From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40885) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLaBG-0002Yt-5F for qemu-devel@nongnu.org; Tue, 19 Jan 2016 12:34:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLaBD-0008Ai-EG for qemu-devel@nongnu.org; Tue, 19 Jan 2016 12:34:58 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54112) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLaBD-0008Ae-8W for qemu-devel@nongnu.org; Tue, 19 Jan 2016 12:34:55 -0500 References: <1451997467.16471.3.camel@redhat.com> <20160105134720.GA2393@cbox> <1452016711.16471.6.camel@redhat.com> <1452018414.16471.8.camel@redhat.com> <20160106113402.GA13870@cbox> <1452084567.4759.6.camel@redhat.com> <20160109150155.GA31776@cbox> <1452613707.4114.9.camel@redhat.com> <20160119164620.GA26962@hawk.localdomain> From: Laszlo Ersek Message-ID: <569E73BA.9070603@redhat.com> Date: Tue, 19 Jan 2016 18:34:50 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [libvirt] ARM KVM GICv3 Support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Andrew Jones Cc: Wei Huang , Eric Auger , Libvirt , Andre Przywara , QEMU Developers , Andrea Bolognani , Marc Zyngier , Cole Robinson , Christoffer Dall On 01/19/16 17:53, Peter Maydell wrote: > On 19 January 2016 at 16:46, Andrew Jones 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