From: Andrea Bolognani <abologna@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Wei Huang <wei@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>,
Libvirt <libvir-list@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Xu <peterx@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [libvirt] [RFC PATCH 0/2] ARM: add QMP command to query GIC version
Date: Tue, 16 Feb 2016 13:27:55 +0100 [thread overview]
Message-ID: <1455625675.4617.90.camel@redhat.com> (raw)
In-Reply-To: <20160216121532.GC11370@redhat.com>
On Tue, 2016-02-16 at 12:15 +0000, Daniel P. Berrange wrote:
> On Tue, Feb 16, 2016 at 01:05:45PM +0100, Andrea Bolognani wrote:
> > On Tue, 2016-02-16 at 10:15 +0000, Daniel P. Berrange wrote:
> > > > Back to GIV. Recognized values of gic-version are fixed at compile
> > > > time: 2, 3, host. Once again, QOM does things in code rather than data:
> > > > the set of values is defined in the setter function
> > > > virt_set_gic_version().
> > > >
> > > > Some values are accepted only together with other configuration: 3
> > > > requires accel=kvm (for now), host requires -cpu host. Static
> > > > introspection can't show such constraints.
> > > >
> > > > Would the proposed query-gic-capability show them? How?
> > >
> > > Also bear in mind that libvirt probes capabilities using '-m none' so
> > > you're not going to have any 'virt' machine type instantiated when
> > > probing is done.
> >
> > The idea is to add this information to domain capabilities, which
> > already have virtualization type, architecture and machine type as
> > inputs.
>
> Regardless of the way it is exposed in libvirt API, when libvirt probes
> for capabilities it will *always* use '-m none'.
Domain capabilities are currently derived almost entirely from data
taken from virQEMUCaps, but is there anything stopping us from
calling QEMU with the appropriate machine type from
qemuConnectGetDomainCapabilities() to query for machine type
dependent domain capabilities such as supported values for the
gic-version property?
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
next prev parent reply other threads:[~2016-02-16 12:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 5:41 [Qemu-devel] [RFC PATCH 0/2] ARM: add QMP command to query GIC version Peter Xu
2016-02-14 5:41 ` [Qemu-devel] [RFC PATCH 1/2] arm: gic: add GICType Peter Xu
2016-02-14 5:41 ` [Qemu-devel] [RFC PATCH 2/2] arm: gic: add "query-gic-capability" interface Peter Xu
2016-02-15 6:54 ` [Qemu-devel] [RFC PATCH 0/2] ARM: add QMP command to query GIC version Wei Huang
2016-02-15 7:34 ` Peter Xu
2016-02-15 7:49 ` Fam Zheng
2016-02-15 9:35 ` [Qemu-devel] [libvirt] " Martin Kletzander
2016-02-15 9:41 ` Peter Maydell
2016-02-15 12:16 ` Andrew Jones
2016-02-15 12:27 ` Pavel Fedin
2016-02-15 10:09 ` Peter Xu
2016-02-15 9:52 ` [Qemu-devel] " Markus Armbruster
2016-02-15 10:34 ` Peter Xu
2016-02-15 15:08 ` Markus Armbruster
2016-02-15 15:21 ` Peter Maydell
2016-02-15 19:40 ` Markus Armbruster
2016-02-15 20:18 ` Andrew Jones
2016-02-15 20:32 ` Peter Maydell
2016-02-16 10:10 ` Markus Armbruster
2016-02-16 10:15 ` Daniel P. Berrange
2016-02-16 12:05 ` [Qemu-devel] [libvirt] " Andrea Bolognani
2016-02-16 12:09 ` Peter Maydell
2016-02-16 12:20 ` Andrea Bolognani
2016-02-16 12:15 ` Daniel P. Berrange
2016-02-16 12:27 ` Andrea Bolognani [this message]
2016-02-16 12:38 ` Daniel P. Berrange
2016-02-16 13:14 ` Andrea Bolognani
2016-02-15 15:22 ` [Qemu-devel] " Daniel P. Berrange
2016-02-18 4:40 ` Peter Xu
2016-02-18 16:52 ` Andrew Jones
2016-02-18 17:10 ` Andrea Bolognani
2016-02-19 1:55 ` Peter Xu
2016-02-19 12:33 ` Andrea Bolognani
2016-02-22 1:35 ` Peter Xu
2016-02-29 16:30 ` Andrea Bolognani
2016-03-01 2:19 ` 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=1455625675.4617.90.camel@redhat.com \
--to=abologna@redhat.com \
--cc=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--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).