From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Cornelia Huck <cohuck@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] accel: default to an actually available accelerator
Date: Mon, 11 Sep 2017 13:48:46 +0200 [thread overview]
Message-ID: <afe815b5-d5a6-8b22-b30f-50f52dbe540e@redhat.com> (raw)
In-Reply-To: <CAFEAcA9oOmX1u2zYHJ28AYFDUXVUs=8i04fC05TsxopbvxPmBQ@mail.gmail.com>
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).
Paolo
next prev parent reply other threads:[~2017-09-11 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 9:49 [Qemu-devel] [PATCH RFC] accel: default to an actually available accelerator Cornelia Huck
2017-09-06 11:29 ` Cornelia Huck
2017-09-06 14:35 ` Peter Maydell
2017-09-06 15:54 ` Cornelia Huck
2017-09-11 11:48 ` Paolo Bonzini [this message]
2017-09-11 11:51 ` Cornelia Huck
2017-09-11 11:53 ` Paolo Bonzini
2017-09-07 8:11 ` Kevin Wolf
2017-09-07 8:14 ` Thomas Huth
2017-09-07 8:25 ` Cornelia Huck
2017-09-07 8:45 ` Kevin Wolf
2017-09-11 11:51 ` Paolo Bonzini
2017-09-22 18:15 ` Eduardo Habkost
2017-09-06 14:04 ` Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=afe815b5-d5a6-8b22-b30f-50f52dbe540e@redhat.com \
--to=pbonzini@redhat.com \
--cc=cohuck@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).