qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Bolognani <abologna@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: wei@redhat.com, peter.maydell@linaro.org, drjones@redhat.com,
	armbru@redhat.com, mdroth@linux.vnet.ibm.com,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/3] arm: implement query-gic-capability
Date: Fri, 04 Mar 2016 09:43:24 +0100	[thread overview]
Message-ID: <1457081004.4468.4.camel@redhat.com> (raw)
In-Reply-To: <20160304025255.GF30973@pxdev.xzpeter.org>

On Fri, 2016-03-04 at 10:52 +0800, Peter Xu wrote:
> > Sorry for not catching this earlier, but I'm afraid this is not
> > going to work -- libvirt doesn't pass either -enable-kvm or the
> > machine option accel=kvm when probing for capabilities, which
> > means that, with the current implementation, it will only get
> > information about emulated GIC.
> > 
> > Is there a way to make probing work without requiring KVM to
> > be enabled?
> Ah.. If so, this is a good point...
> 
> I can do this, but I just feel it a bit hacky if I do ioctl()s
> directly in one QMP command handle:
> 
> qmp_query_gic_capability()
> {
>     kvm = open("/dev/kvm");
>     vm = ioctl(KVM_CREATE_VM);
> 
>     ...test create devices using KVM_CREATE_DEVICE ioctls...
> 
>     close(vm);
>     close(kvm);
> }
> 
> Rather than leveraging current KVMState stuffs (of course, I can
> make things a little bit prettier than above...).
> 
> Another way to do is to generalize kvm_init() maybe? That's some
> work too.
> 
> Andrea, do you know how much effort we need to add this support for
> libvirt, say, we can specify "accel=" or "-enable-kvm" as extra
> parameter when probing?

I'm afraid this is not going to be possible for the same reason
we have to use '-M none' when probing: at that point in time, we
simply have no idea what the guests will look like. Actually,
it's the other way around, in that the result of probing (host
and domain capabilities) will influence the guest configuration
created by the user / management tool.

And we definitely can't use 'accel=kvm' unconditionally, because
then we won't be able to probe eg. the qemu-system-aarch64 binary
installed on a x86_64 host.

Cheers.

-- 
Andrea Bolognani
Software Engineer - Virtualization Team

  reply	other threads:[~2016-03-04  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03  8:21 [Qemu-devel] [PATCH v2 0/3] ARM: add query-gic-capability SMP command Peter Xu
2016-03-03  8:21 ` [Qemu-devel] [PATCH v2 1/3] arm: qmp: add GICCapability struct Peter Xu
2016-03-03  8:21 ` [Qemu-devel] [PATCH v2 2/3] arm: qmp: add query-gic-capability interface Peter Xu
2016-03-03 11:55   ` Andrew Jones
2016-03-04  2:22     ` Peter Xu
2016-03-03  8:21 ` [Qemu-devel] [PATCH v2 3/3] arm: implement query-gic-capability Peter Xu
2016-03-03 12:19   ` Andrea Bolognani
2016-03-04  2:52     ` Peter Xu
2016-03-04  8:43       ` Andrea Bolognani [this message]
2016-03-07  4:27         ` Peter Xu

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=1457081004.4468.4.camel@redhat.com \
    --to=abologna@redhat.com \
    --cc=armbru@redhat.com \
    --cc=drjones@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wei@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).