From: Eric Blake <eblake@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>,
Andrew Jones <drjones@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eric Auger <eric.auger@linaro.org>,
Libvirt <libvir-list@redhat.com>,
Andre Przywara <andre.przywara@arm.com>,
qemu-devel@nongnu.org, Andrea Bolognani <abologna@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [Qemu-devel] [libvirt] ARM KVM GICv3 Support
Date: Tue, 2 Feb 2016 08:52:12 -0700 [thread overview]
Message-ID: <56B0D0AC.3010003@redhat.com> (raw)
In-Reply-To: <20160202140528.GC6190@cbox>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On 02/02/2016 07:05 AM, Christoffer Dall wrote:
>>
>> I'm not familiar enough with libvirt, nor the use of QMP, to really argue
>> one way or another, but I find it a bit strange that we'd prefer libvirt
>> to query two entities over one. And, why should the libvirt installed on
>> a particular host prefer gicv3 as the default, just because KVM supports
>> it, even when QEMU does not?
>
> I think the assumption here is that if you install a recent libvirt you
> also install a recent QEMU. You always have the risk of things not
> working if you have too old a QEMU, right?
Libvirt exists for providing back-compat glue. The following
combinations are supported:
old libvirt, old qemu
new libvirt, old qemu
new libvirt, new qemu
and it is only this combination that might require a libvirt upgrade to
work correctly:
old libvirt, new qemu
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-02-02 15:52 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 [this message]
2016-02-02 15:58 ` Christoffer Dall
2016-02-15 10:08 ` Andrea Bolognani
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=56B0D0AC.3010003@redhat.com \
--to=eblake@redhat.com \
--cc=abologna@redhat.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@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.