qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cam Macdonell <cam@cs.ualberta.ca>
To: Frank Berreth <frankber@google.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: How to map PCI memory into the VM without trapping
Date: Thu, 6 May 2010 10:52:16 -0600	[thread overview]
Message-ID: <i2j8286e4ee1005060952zf12dc1ffhed501a919692d4e4@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil62opmjq2GWe5euf9wBxWYsGjATYhSlI4tDynj@mail.gmail.com>

On Wed, May 5, 2010 at 5:20 PM, Frank Berreth <frankber@google.com> wrote:
> Hi there,
> this is just an update if you are interested in the outcome. I turns out
> that my initial assumption that there would be page faults/trapping on the
> memory pages was false. The reason the throughput is so low is because the
> memory was mapped non-cached. The VGA driver and the ivshmem driver use
> pci_ioremap_bar which will *always* map the PCI bar non-cached (even the
> resourceX_wc).
> Changing the driver(s) to use ioremap_cache or ioremap_wc speeds up things
> quite a bit. I don't know if VGA framebuffer was always mapped this way --
> it appears on a real system that usually graphics memory is mapped WC.
> Mapping it UC would cause quite a performance degradation. This could be the
> reason for the reported VGA performance drop in another email thread. IMHO,
> since QEMU emulates VGA, this could be mapped WB.
> Thanks,
> Frank.
>

Hi Frank,

Thanks for the note.  I'll make the change to cached and see if that
helps with some of the tests I'm running.

Cheers,
Cam

      reply	other threads:[~2010-05-06 16:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 21:07 [Qemu-devel] How to map PCI memory into the VM without trapping Frank Berreth
2010-05-05 23:20 ` [Qemu-devel] " Frank Berreth
2010-05-06 16:52   ` Cam Macdonell [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=i2j8286e4ee1005060952zf12dc1ffhed501a919692d4e4@mail.gmail.com \
    --to=cam@cs.ualberta.ca \
    --cc=frankber@google.com \
    --cc=kvm@vger.kernel.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).