qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Laurent Vivier <Laurent.Vivier@bull.net>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [RFC] Coalesced MMIO support
Date: Fri, 05 Dec 2008 20:46:50 +0200	[thread overview]
Message-ID: <4939771A.1010602@redhat.com> (raw)
In-Reply-To: <49384758.9090900@us.ibm.com>

Anthony Liguori wrote:
> The images I need to test this against are not on this computer, so I 
> can't commit until tomorrow when I have access to them again.  So I 
> figured that was a good reason to post first as an RFC.
>
> MMIO exits are more expensive in KVM or Xen than in QEMU because they 
> involve, at least, privilege transitions.  However, MMIO write 
> operations can be effectively batched if those writes do not have side 
> effects.
>
> Good examples of this include VGA pixel operations when in a planar 
> mode.  As it turns out, we can get a nice boost in other areas too.  
> Laurent mentioned a 9.7% performance boost in iperf with the coalesced 
> MMIO changes for the e1000 when he originally posted this work for KVM.
>

The cirrus blitter could also use this.  None of the registers except 
start/status have any effect except for queuing a bit of data.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

      reply	other threads:[~2008-12-05 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 21:10 [Qemu-devel] [RFC] Coalesced MMIO support Anthony Liguori
2008-12-05 18:46 ` Avi Kivity [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=4939771A.1010602@redhat.com \
    --to=avi@redhat.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Laurent.Vivier@bull.net \
    --cc=kvm-devel@lists.sourceforge.net \
    --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).