From: Alon Levy <alevy@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: kraxel@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] hmp/qxl: info spice: add qxl info
Date: Mon, 28 May 2012 16:36:16 +0300 [thread overview]
Message-ID: <20120528133616.GK8353@garlic> (raw)
In-Reply-To: <20120528101328.4f936301@doriath.home>
On Mon, May 28, 2012 at 10:13:28AM -0300, Luiz Capitulino wrote:
> On Mon, 28 May 2012 12:08:13 +0300
> Alon Levy <alevy@redhat.com> 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 <alevy@redhat.com> 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"?
prev parent reply other threads:[~2012-05-28 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 15:09 [Qemu-devel] [PATCH] hmp/qxl: info spice: add qxl info Alon Levy
2012-05-24 15:19 ` Alon Levy
2012-05-24 16:22 ` [Qemu-devel] [PATCH v2] " Alon Levy
2012-05-25 14:43 ` Luiz Capitulino
2012-05-28 9:08 ` Alon Levy
2012-05-28 13:13 ` Luiz Capitulino
2012-05-28 13:36 ` Alon Levy [this message]
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=20120528133616.GK8353@garlic \
--to=alevy@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).