From: Eduardo Habkost <ehabkost@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Thomas Huth" <thuth@redhat.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
qemu-devel@nongnu.org, "Emilio G . Cota" <cota@braap.org>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [RFC PATCH] vl: only display available accelerators
Date: Wed, 8 Nov 2017 15:25:47 -0200 [thread overview]
Message-ID: <20171108172547.GP3111@localhost.localdomain> (raw)
In-Reply-To: <20171108170629.GD12670@redhat.com>
On Wed, Nov 08, 2017 at 05:06:29PM +0000, Daniel P. Berrange wrote:
> On Wed, Nov 08, 2017 at 02:59:05PM -0200, Eduardo Habkost wrote:
> > On Wed, Nov 08, 2017 at 01:21:33PM -0300, Philippe Mathieu-Daudé wrote:
> > > On 11/08/2017 10:28 AM, Daniel P. Berrange wrote:
> > > > On Mon, Oct 30, 2017 at 09:20:29AM +0100, Eduardo Habkost wrote:
> > > >> On Mon, Oct 30, 2017 at 01:00:56AM -0300, Philippe Mathieu-Daudé wrote:
> > > >>> examples configuring with '--enable-kvm --disable-tcg'
> > > >>>
> > > >>> - before
> > > >>>
> > > >>> $ qemu-system-x86_64 -accel help
> > > >>> Possible accelerators: kvm, xen, hax, tcg
> > > >>>
> > > >>> $ qemu-system-x86_64 -accel tcg
> > > >>> qemu-system-x86_64: -machine accel=tcg: No accelerator found
> > > >>>
> > > >>> # qemu-system-x86_64 -accel hax
> > > >>> qemu-system-x86_64: -machine accel=hax: No accelerator found
> > > >>>
> > > >>> # qemu-system-x86_64 -accel xen
> > > >>> xencall: error: Could not obtain handle on privileged command interface: No such file or directory
> > > >>> xen be core: xen be core: can't open xen interface
> > > >>> can't open xen interface
> > > >>> qemu-system-x86_64: failed to initialize Xen: Operation not permitted
> > > >>>
> > > >>> - after
> > > >>>
> > > >>> $ qemu-system-x86_64 -accel help
> > > >>> Possible accelerators: kvm
> > > >>>
> > > >>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> > > >>> ---
> > > >>> RFC because:
> > > >>> - I don't think this is the nicest way, too much #ifdef'fery in main()
> > > >>
> > > >> I suggest using object_class_get_list(TYPE_ACCEL, false).
> > > >
> > > > And check the result of the available() method on the returned classes
> > > > too, to filter the results.
> > >
> > > Good idea! I'll use that.
> >
> > It looks like QTest is the only accelerator that implements
> > ->available(), and its return value is a build-time constant that
> > depends only on CONFIG_POSIX.
> >
> > I wonder why we don't simply avoid compiling the qtest class if
> > CONFIG_POSIX is unset, making the ->available() method
> > unnecessary.
>
> Yeah that does seem simpler, though I'm surprised that Xen does not
> implement the available method. Xen is an accel I'd expect to see
> compiled into an x86 build, but is only available if the host is
> actually booted under a Xen hypervisor. Likewise shouldn't kvm
> only report itself as available if the /dev/kvm actually exists.
> But maybe that's not the kind of semantics code using available()
> expects ?
Currently the only caller of ->available() calls ->init_machine()
immediately afterwards, so for the current code it doesn't matter
if the check is inside ->available() or ->init_machine().
That said, I'm not sure we should look for /dev/kvm or check for
the Xen hypervisor when handling "-accel help". I expect help
text to tell the user what the QEMU binary supports, not what the
current host supports.
--
Eduardo
next prev parent reply other threads:[~2017-11-08 17:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 4:00 [Qemu-devel] [RFC PATCH] vl: only display available accelerators Philippe Mathieu-Daudé
2017-10-30 4:13 ` no-reply
2017-10-30 8:20 ` Eduardo Habkost
2017-10-30 15:01 ` Philippe Mathieu-Daudé
2017-10-30 15:34 ` Peter Maydell
2017-11-08 13:28 ` Daniel P. Berrange
2017-11-08 16:21 ` Philippe Mathieu-Daudé
2017-11-08 16:59 ` Eduardo Habkost
2017-11-08 17:06 ` Daniel P. Berrange
2017-11-08 17:25 ` Eduardo Habkost [this message]
2017-11-08 17:28 ` Daniel P. Berrange
2017-11-08 18:03 ` Philippe Mathieu-Daudé
2017-11-08 18:35 ` Eduardo Habkost
2017-11-08 19:41 ` Philippe Mathieu-Daudé
-- strict thread matches above, loose matches on Subject: below --
2017-10-30 18:14 Philippe Mathieu-Daudé
2017-10-30 18:18 ` Philippe Mathieu-Daudé
2017-11-03 0:35 ` Eduardo Habkost
2017-11-08 16:20 ` Philippe Mathieu-Daudé
2017-11-08 16:56 ` Eduardo Habkost
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=20171108172547.GP3111@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sstabellini@kernel.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).