qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: John Baboval <baboval@spineless.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Multi-head support RFC
Date: Wed, 20 Nov 2013 08:39:35 +0100	[thread overview]
Message-ID: <1384933175.2005.15.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <528B72E8.6070307@spineless.org>

> >     graphic_console_init(..., &state->heads[i]);
> >
> > so you can figure the head in the callbacks.
> 
> What I had prototyped (I got impatient) was to add a helper: 
> qemu_console_hw_opaque() to console.c so the HwOps could query the 
> opaque pointer. I don't like it because it requires an additional 
> function call at the top of frequently called operations... However I'm 
> not a huge fan of the head state array either, since it will require 
> either pointer duplication, or pointer acrobatics, or the same helper 
> function to get the card state.

Yes, easiest way to get the device state struct from the head state
struct is a pointer in each the head state (this is what you mean with
pointer duplication, right?).

I still think it is the best way.  You get a direct pointer to your head
state.  Device state is only one pointer dereference away.

Anything else requires extra effort to lookup the head state from
whatever information (QemuConsole, index, ...) we pass to the hwops
function.

cheers,
  Gerd

      reply	other threads:[~2013-11-20  7:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 20:42 [Qemu-devel] Multi-head support RFC John Baboval
2013-11-06  1:46 ` Dave Airlie
2013-11-06 10:57   ` Gerd Hoffmann
2013-11-06 23:44     ` Dave Airlie
2013-11-07 13:00       ` Gerd Hoffmann
2013-11-08 15:20       ` John Baboval
2013-11-06 15:48   ` John Baboval
2013-11-06 10:55 ` Gerd Hoffmann
2013-11-06 15:39   ` John Baboval
2013-11-07 13:46     ` Gerd Hoffmann
2013-11-07 15:54       ` John Baboval
2013-11-15 20:14         ` John Baboval
2013-11-19  6:57           ` Gerd Hoffmann
2013-11-19 14:17             ` John Baboval
2013-11-20  7:39               ` Gerd Hoffmann [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=1384933175.2005.15.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=baboval@spineless.org \
    --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).