From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:58278) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SZ07a-0001L0-Se for qemu-devel@nongnu.org; Mon, 28 May 2012 09:36:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SZ07Z-0006Bp-6c for qemu-devel@nongnu.org; Mon, 28 May 2012 09:36:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38696) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SZ07Y-0006Bg-V5 for qemu-devel@nongnu.org; Mon, 28 May 2012 09:36:29 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4SDaRCt029264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 28 May 2012 09:36:27 -0400 Date: Mon, 28 May 2012 16:36:16 +0300 From: Alon Levy Message-ID: <20120528133616.GK8353@garlic> References: <20120524151905.GQ6105@garlic.tlv.redhat.com> <1337876572-2051-1-git-send-email-alevy@redhat.com> <20120525114311.1c1acf03@doriath.home> <20120528090813.GE8353@garlic> <20120528101328.4f936301@doriath.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120528101328.4f936301@doriath.home> Subject: Re: [Qemu-devel] [PATCH v2] hmp/qxl: info spice: add qxl info List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: kraxel@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com On Mon, May 28, 2012 at 10:13:28AM -0300, Luiz Capitulino wrote: > On Mon, 28 May 2012 12:08:13 +0300 > Alon Levy wrote: > > > On Fri, May 25, 2012 at 11:43:11AM -0300, Luiz Capitulino wrote: > > > On Thu, 24 May 2012 19:22:52 +0300 > > > Alon Levy wrote: > > > > > > > For all devices print id, mode and guest_bug status. > > > > > > Is qxl really tied to spice? In the meaning that it's impossible to use it > > > without spice? Wouldn't it be better to have 'info display' instead? > > > > Would a patch implementing 'info display' require me to implement it for > > all displays? > > Would be nice, even if we start with very basic information. How would that work? I have QXLInfo that only makes sense when the information is about a qxl device. Can't have opaque data in a QMP response, so would this be a "info display qxl" "info display cirrus" etc. or "info qxl"?