All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: John Williams <john.williams@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	John Williams <jwilliams@xilinx.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Peter Crosthwaite <pcrost@xilinx.com>
Subject: Re: [Qemu-devel] [RFC] Memory API and fine grained Memory Regions
Date: Mon, 29 Oct 2012 18:34:37 +0200	[thread overview]
Message-ID: <508EB01D.5010608@redhat.com> (raw)
In-Reply-To: <ac93a283-e426-462e-8057-8428492ece78@VA3EHSMHS018.ehs.local>

On 10/29/2012 01:37 AM, John Williams wrote:

>> IMO, an mr per reg would just add a massive overhead for no win.
> 
> I tend to agree with Edgar here - QEMU has a careful line to walk between being an emulator and an RTL simulator.
> 
> Any WAG on the runtime overhead of a mem region per register vs a switch-based decodes in read/write handlers?
> 

Actually a region-per-register can be faster, since the subpage logic
will dispatch the access directly to the handler, instead of going first
to the device handler, then following the switch.

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

  reply	other threads:[~2012-10-29 16:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26  7:03 [Qemu-devel] [RFC] Memory API and fine grained Memory Regions Peter Crosthwaite
2012-10-26  7:31 ` Gerd Hoffmann
2012-10-27  4:12 ` Edgar E. Iglesias
2012-10-28 23:37   ` John Williams
2012-10-29 16:34     ` Avi Kivity [this message]
2012-10-30  8:35       ` Edgar E. Iglesias
2012-10-29 16:36   ` Avi Kivity

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=508EB01D.5010608@redhat.com \
    --to=avi@redhat.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.williams@xilinx.com \
    --cc=jwilliams@xilinx.com \
    --cc=pcrost@xilinx.com \
    --cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.