All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Andrew Jones <drjones@redhat.com>
Cc: Wei Huang <wei@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>,
	Andrea Bolognani <abologna@redhat.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Cole Robinson <crobinso@redhat.com>,
	Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] [libvirt] ARM KVM GICv3 Support
Date: Tue, 19 Jan 2016 18:34:50 +0100	[thread overview]
Message-ID: <569E73BA.9070603@redhat.com> (raw)
In-Reply-To: <CAFEAcA9htRS3MLvVOBmSaw2=gvHg-ZLR1RH64SP47HDGRtJMqQ@mail.gmail.com>

On 01/19/16 17:53, Peter Maydell wrote:
> On 19 January 2016 at 16:46, Andrew Jones <drjones@redhat.com> wrote:
>> On Tue, Jan 12, 2016 at 04:48:27PM +0100, Andrea Bolognani wrote:
>>> Would providing a QMP command that returns the list of GIC versions
>>> available on the current host for the current machine type be
>>> acceptable from QEMU's point of view?
>>>
>>
>> Adding qemu-devel. Peter any opinion on this? If it sounds like a
>> reasonable idea then either I or Wei can look into sending the
>> patches.
> 
> I don't have a strong opinion, really. We should do whatever
> works for libvirt and fits with whatever we do currently
> (eg whatever we do at the moment for telling libvirt
> "yes this QEMU supports KVM", if we're not using some ancient
> silly way to do that).

Would this kind of info fit the capabilities list that libvirtd fetches
from QEMU at startup (as far as I recall)?

Thanks
Laszlo

  reply	other threads:[~2016-01-19 17:34 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 [this message]
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
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=569E73BA.9070603@redhat.com \
    --to=lersek@redhat.com \
    --cc=abologna@redhat.com \
    --cc=andre.przywara@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=crobinso@redhat.com \
    --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 \
    --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 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.