From: Peter Xu <peterx@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>
Cc: peter.maydell@linaro.org, drjones@redhat.com, armbru@redhat.com,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, eblake@redhat.com
Subject: Re: [Qemu-arm] [PATCH v2 3/3] arm: implement query-gic-capability
Date: Fri, 4 Mar 2016 10:52:55 +0800 [thread overview]
Message-ID: <20160304025255.GF30973@pxdev.xzpeter.org> (raw)
In-Reply-To: <1457007587.4468.2.camel@redhat.com>
On Thu, Mar 03, 2016 at 01:19:47PM +0100, Andrea Bolognani wrote:
> On Thu, 2016-03-03 at 16:21 +0800, Peter Xu wrote:
> > For emulated ARM VM, only gicv2 is supported. We need to add gicv3
> in
> > when emulated gicv3 ready. For KVM accelerated ARM VM, we detect the
> > capability bits using ioctls.
> >
> > if we want to
> know GIC kernel capabilities, we need to make sure we have
> > enabled KVM when querying (like, with "-enable-kvm").
> >
> >
> Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > target-arm/machine.c | 48
> +++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 47 insertions(+), 1 deletion(-)
>
> 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?
Or, does anyone on the list has suggestion on how to better do this?
Thanks.
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Xu <peterx@redhat.com>
To: Andrea Bolognani <abologna@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, 4 Mar 2016 10:52:55 +0800 [thread overview]
Message-ID: <20160304025255.GF30973@pxdev.xzpeter.org> (raw)
In-Reply-To: <1457007587.4468.2.camel@redhat.com>
On Thu, Mar 03, 2016 at 01:19:47PM +0100, Andrea Bolognani wrote:
> On Thu, 2016-03-03 at 16:21 +0800, Peter Xu wrote:
> > For emulated ARM VM, only gicv2 is supported. We need to add gicv3
> in
> > when emulated gicv3 ready. For KVM accelerated ARM VM, we detect the
> > capability bits using ioctls.
> >
> > if we want to
> know GIC kernel capabilities, we need to make sure we have
> > enabled KVM when querying (like, with "-enable-kvm").
> >
> >
> Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > target-arm/machine.c | 48
> +++++++++++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 47 insertions(+), 1 deletion(-)
>
> 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?
Or, does anyone on the list has suggestion on how to better do this?
Thanks.
Peter
next prev parent reply other threads:[~2016-03-04 2:53 UTC|newest]
Thread overview: 14+ 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 ` [Qemu-arm] " Andrew Jones
2016-03-03 11:55 ` Andrew Jones
2016-03-04 2:22 ` [Qemu-arm] " Peter Xu
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 [this message]
2016-03-04 2:52 ` Peter Xu
2016-03-04 8:43 ` Andrea Bolognani
2016-03-07 4:27 ` [Qemu-arm] " Peter Xu
2016-03-07 4:27 ` [Qemu-devel] " 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=20160304025255.GF30973@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=eblake@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.