qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH 1 of 2] [UPDATE] DisplayState interface change
Date: Thu, 20 Nov 2008 12:58:39 -0600	[thread overview]
Message-ID: <4925B35F.20701@codemonkey.ws> (raw)
In-Reply-To: <49259735.8080807@eu.citrix.com>

Hi Stefano,

Stefano Stabellini wrote:
> Hi all,
> this patch changes the DisplayState interface adding support for
> multiple frontends at the same time (sdl and vnc) and implements most
> of the benefit of the shared_buf patch without the added complexity.
>
> Currently DisplayState is managed by sdl (or vnc) and sdl (or vnc) is
> also responsible for allocating the data and setting the depth.
> Vga.c (or another backend) will do any necessary conversion.
>
> The idea is to change it so that is vga.c (or another backend) that
> fully manages the DisplayState interface allocating data and setting the
> depth (either 16 or 32 bit, if the guest uses a different resolution or
> is in text mode, vga.c (or another backend) is in charge of
> doing the conversion seamlessly).
>
> The other idea is that DisplayState supports *multiple* frontends
> like sdl and vnc; each of them can register some callbacks to be called
> when a display event occurs.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>   

There are really two parts to this patch.  One part is a completely 
mechanical conversion of things like ds->linesize to 
ds->surface->linesize.  The second is the guys of the API change.

If you introduce accessors to access things like linesize from 
DisplayState, so something like:

int ds_get_linesize(DisplayState *ds) {
     return ds->linesize;
}

You can do the mechanical conversion in a single patch.  That patch will 
then be a breeze to review.  Then in your next patch, you can just 
convert these accessors to use the new ds->surface->linesize.

That should make this all considerably easier to thoroughly review.  
It's just too big right now to review properly.

Regards,

Anthony Liguori

  parent reply	other threads:[~2008-11-20 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 16:58 [Qemu-devel] [PATCH 1 of 2] [UPDATE] DisplayState interface change Stefano Stabellini
     [not found] ` <200811201737.00254.paul@codesourcery.com>
2008-11-20 17:48   ` Stefano Stabellini
     [not found]     ` <200811201823.22742.paul@codesourcery.com>
2008-11-20 18:36       ` Stefano Stabellini
     [not found]         ` <200811201839.24213.paul@codesourcery.com>
2008-11-20 19:02           ` Stefano Stabellini
     [not found]     ` <200811211040.44235.paul@codesourcery.com>
2008-11-21 11:31       ` Stefano Stabellini
2008-11-20 18:58 ` Anthony Liguori [this message]
     [not found]   ` <200811202246.18906.paul@codesourcery.com>
2008-11-20 23:06     ` Anthony Liguori
2008-11-20 23:07     ` Anthony Liguori
2008-11-20 23:16     ` Anthony Liguori

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=4925B35F.20701@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.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 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).