[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH RFC] accel: default to an actually available acc
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH RFC] accel: default to an actually available accelerator |
Date: |
Mon, 11 Sep 2017 13:53:09 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
On 11/09/2017 13:51, Cornelia Huck wrote:
> On Mon, 11 Sep 2017 13:48:46 +0200
> Paolo Bonzini <address@hidden> wrote:
>
>> On 06/09/2017 16:35, Peter Maydell wrote:
>>>>> accel = qemu_opt_get(qemu_get_machine_opts(), "accel");
>>>>> if (accel == NULL) {
>>>>> - /* Use the default "accelerator", tcg */
>>>>> - accel = "tcg";
>>>>> + accel = default_accelerator();
>>>> It actually may be easier to just switch the default to
>>>> "tcg:kvm:xen:hax". Haven't tested that, though.
>>> Does it make sense to include Xen in the default list?
>>> I don't know much about Xen but I was under the impression
>>> that it's a special purpose thing that you can only use
>>> as part of a Xen setup, whereas tcg, kvm, hax are all
>>> more-or-less interchangeable ways to run a VM under a
>>> Linux/etc host. Do I have the wrong end of the Xen stick?
>>
>> Yes, that is correct (in fact, -xen-domid is required too).
>
> OK, so we should use "tcg:kvm:hax"?
>
> (Not sure how useful the hax statement is, I'm not familiar with that
> one.)
Yes. When we move KVM to the front, however, HAX and the upcoming HVF
accelerator probably should stay in the back because they are less
tested than TCG (e.g. HAX doesn't support -cpu, HVF will not support
live migration in the first iteration, etc.).
Paolo
Re: [Qemu-devel] [PATCH RFC] accel: default to an actually available accelerator, Richard Henderson, 2017/09/06