From: Andrea Bolognani <abologna@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>,
Eric Auger <eric.auger@linaro.org>,
Libvirt <libvir-list@redhat.com>,
Andre Przywara <andre.przywara@arm.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [Qemu-devel] [libvirt] ARM KVM GICv3 Support
Date: Mon, 15 Feb 2016 11:08:19 +0100 [thread overview]
Message-ID: <1455530899.4617.69.camel@redhat.com> (raw)
In-Reply-To: <CAMJs5B-QfPeWrB1LFp5qj-N71zD1AGL-MNiJDJfvdqJruAdrQw@mail.gmail.com>
On Tue, 2016-02-02 at 16:58 +0100, Christoffer Dall wrote:
> ok, so that would mean we need to implement a QMP command to tell us
> which gic versions are supported for a given machine. Current
> possible responses are "2", "3" and "2,3"
>
> and we also need to add code to libvirt to try that QMP command, and
> if it doesn't exist, fall back to not specifying gic-version, using
> the old-qemu compatible default of providing a gicv2 to guests, and if
> the QMP command exists, use the newest gic-version.
>
> users can then always override this behavior by directly specifying a
> gic version "host", "2", or "3" in their xml file.
>
> any objections?
Dan voiced his preference for probing the host GIC versions from
libvirt and just passing that to QEMU dealing with any failure later
on, but I think that was mostly to keep things simple and not
because the QMP command approach was wrong?
IOW Dan, if we went ahead with the QMP command approach, would you
oppose it? Peter Xu has posted some RFC QEMU patches yesterday...
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
next prev parent reply other threads:[~2016-02-15 10:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1451993822.16471.1.camel@redhat.com>
[not found] ` <20160105120832.GC28354@cbox>
[not found] ` <1451997467.16471.3.camel@redhat.com>
[not found] ` <20160105134720.GA2393@cbox>
[not found] ` <1452016711.16471.6.camel@redhat.com>
[not found] ` <CAFEAcA_Y6keKPb0Ayjp4yFSdfZXg7rFmxxZ33f=e4R0sV+b8HQ@mail.gmail.com>
[not found] ` <1452018414.16471.8.camel@redhat.com>
[not found] ` <20160106113402.GA13870@cbox>
[not found] ` <1452084567.4759.6.camel@redhat.com>
[not found] ` <CAFEAcA9AGYQiWPDH6fcxMo=jycxtKL8c50JmH1TtS4=Qz53-XQ@mail.gmail.com>
[not found] ` <20160109150155.GA31776@cbox>
[not found] ` <1452613707.4114.9.camel@redhat.com>
2016-01-19 16:46 ` [Qemu-devel] [libvirt] ARM KVM GICv3 Support Andrew Jones
2016-01-19 16:53 ` Peter Maydell
2016-01-19 17:34 ` Laszlo Ersek
2016-01-22 14:44 ` Daniel P. Berrange
2016-02-02 11:49 ` Christoffer Dall
2016-02-02 12:10 ` Daniel P. Berrange
2016-02-02 12:59 ` Andrew Jones
2016-02-02 13:15 ` Peter Maydell
2016-02-02 14:04 ` Andrew Jones
2016-02-02 14:07 ` Peter Maydell
2016-02-02 14:05 ` Christoffer Dall
2016-02-02 14:42 ` Andrew Jones
2016-02-02 15:52 ` Eric Blake
2016-02-02 15:58 ` Christoffer Dall
2016-02-15 10:08 ` Andrea Bolognani [this message]
2016-02-02 15:09 ` Andrea Bolognani
2016-02-02 15:36 ` Pavel Fedin
2016-02-02 15:50 ` Peter Maydell
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=1455530899.4617.69.camel@redhat.com \
--to=abologna@redhat.com \
--cc=andre.przywara@arm.com \
--cc=berrange@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=eblake@redhat.com \
--cc=eric.auger@linaro.org \
--cc=libvir-list@redhat.com \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.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.