From: Andrew Jones <drjones@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Wei Huang <wei@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Libvirt <libvir-list@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Xu <peterx@redhat.com>,
Andrea Bolognani <abologna@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] ARM: add QMP command to query GIC version
Date: Mon, 15 Feb 2016 21:18:15 +0100 [thread overview]
Message-ID: <20160215201815.yheakyujt4axevse@hawk.localdomain> (raw)
In-Reply-To: <87d1rxhid5.fsf@blackfin.pond.sub.org>
On Mon, Feb 15, 2016 at 08:40:54PM +0100, Markus Armbruster wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > On 15 February 2016 at 15:08, Markus Armbruster <armbru@redhat.com> wrote:
> >> Peter Xu <peterx@redhat.com> writes:
> >>> On Mon, Feb 15, 2016 at 10:52:01AM +0100, Markus Armbruster wrote:
> >>>> Peter Xu <peterx@redhat.com> writes:
> >>>> Adding ad hoc queries as we go won't scale. Is there really no generic
> >>>> way to get this information, e.g. with qom-get?
> >>>
> >>> Haven't used "qom-get" before, but it seems to fetch one property
> >>> for a specific object. If so, will it be strange to hide some
> >>> capability bits into every GIC objects (though there is possibly
> >>> one object)?
> >>
> >> Pardon my ignorance... what are these "GIC objects"?
> >>
> >> What exactly is the "GIC type", and how would the result of
> >> query-gic-capability be used?
> >
> > The GIC type (for our purposes) is the revision of the interrupt
> > controller supported by the host, which comes in two versions
> > (v2 and v3). These are not compatible, unless your host has
> > the v3-with-v2-compat flavour. If a host is v3-only, it is not
> > possible for it to give the guest a v2 virtual interrupt
> > controller; if v2, it can't give the guest a v3 virtual interrupt
> > controller. (If you ask QEMU to do this via command line options
> > we will report an error at startup.)
>
> How would the command line look like?
>
Here is what is available today
# select gicv2 (this work with and without KVM)
qemu-system-aarch64 -M virt # v2 is the default
qemu-system-aarch64 -M virt,gic-version=2 ...
# select gicv3 (only works with KVM)
qemu-system-aarch64 -M virt,gic-version=3 ...
# select whatever the host has
qemu-system-aarch64 -M virt,gic-version=host ...
Thanks,
drew
next prev parent reply other threads:[~2016-02-15 20:18 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 [this message]
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
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=20160215201815.yheakyujt4axevse@hawk.localdomain \
--to=drjones@redhat.com \
--cc=abologna@redhat.com \
--cc=armbru@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).