qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] memory: Fix old portio word accesses
Date: Mon, 19 Sep 2011 16:58:22 +0300	[thread overview]
Message-ID: <4E774A7E.60002@redhat.com> (raw)
In-Reply-To: <4E7749C6.3090305@redhat.com>

On 09/19/2011 04:55 PM, Gerd Hoffmann wrote:
>
> If the register access is trivial then you don't need to call into the 
> driver at all ...
>
> You can have a look at hw/intel-hda.c which actually implements 
> something like this, with some commonly needed features:
>
>   * The "offset" field already mentioned by avi is there, so trivial
>     reads/writes can be handled by the core.
>   * A "wmask" field to specify which bits are guest writable.
>   * A "wclear" field to specify which bits have write-one-to-clear
>     semantics.
>   * A "reset" field which specified the value this field has after
>     device reset.  Also serves as value for read-only registers.
>   * read/write handlers of course.  The write handler is called after
>     the core applied sanity checks and calculated the new register
>     value (using wmask+wclear).
>   * A "name" field (for debug logging).
>
> It's pretty nice, alot more readable that a big switch, forces you to 
> think which bits the guest can set (not specifying a wmask gives you a 
> read-only register ;).
>
> Also no bloat.  With this moving to memory core the all the handlers 
> will gain a line with a container_of(), but that isn't too bad too IMHO.

It's also more secure.  Move as much as possible into the core, and 
review (and fuzz) that like hell.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-09-19 13:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 12:44 [Qemu-devel] [PATCH 1/2] memory: Fix old portio word accesses Jan Kiszka
2011-09-18 12:51 ` [Qemu-devel] [PATCH v2 " Jan Kiszka
2011-09-18 15:37   ` Avi Kivity
2011-09-18 15:43     ` Jan Kiszka
2011-09-18 15:45       ` Avi Kivity
2011-09-18 16:28         ` Jan Kiszka
2011-09-18 16:49           ` Avi Kivity
2011-09-18 19:07             ` Jan Kiszka
2011-09-19 12:19               ` Avi Kivity
2011-09-19 12:32                 ` Jan Kiszka
2011-09-19 12:42                   ` Avi Kivity
2011-09-19 12:55                     ` Jan Kiszka
2011-09-19 13:09                       ` Avi Kivity
2011-09-19 13:55                       ` Gerd Hoffmann
2011-09-19 13:58                         ` Avi Kivity [this message]
2011-09-26 13:30   ` Avi Kivity
2011-09-18 14:44 ` [Qemu-devel] [PATCH " Richard Henderson

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=4E774A7E.60002@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).