From: Paolo Bonzini <pbonzini@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] introduce cpu_physical_memory_map_fast
Date: Fri, 13 May 2011 08:33:13 +0200 [thread overview]
Message-ID: <4DCCD0A9.9050706@redhat.com> (raw)
In-Reply-To: <4DCBFD84.9040702@redhat.com>
On 05/12/2011 05:32 PM, Avi Kivity wrote:
> Out of curiosity, what performance benefit do you see?
Zero. :) Also because the only real change is in patch 4/4 (milkymist)
which I only compile-tested. In all other instances, using
cpu_physical_memory_map_fast is just to make it clear that we don't want
bounce buffers.
However, this is just preparatory work for vmw_pvscsi, which will use
the functions to build its iovecs. qemu_get_ram_ptr would not really be
a satisfactory API for that.
Paolo
prev parent reply other threads:[~2011-05-13 6:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 16:49 [Qemu-devel] [PATCH 0/4] introduce cpu_physical_memory_map_fast Paolo Bonzini
2011-05-03 16:49 ` [Qemu-devel] [PATCH 1/4] exec: extract cpu_physical_memory_map_internal Paolo Bonzini
2011-05-03 16:49 ` [Qemu-devel] [PATCH 2/4] exec: introduce cpu_physical_memory_map_fast and cpu_physical_memory_map_check Paolo Bonzini
2011-05-03 16:49 ` [Qemu-devel] [PATCH 3/4] virtio: use cpu_physical_memory_map_fast Paolo Bonzini
2011-05-03 16:49 ` [Qemu-devel] [PATCH 4/4] milkymist: " Paolo Bonzini
2011-05-04 21:56 ` Michael Walle
2011-05-12 14:51 ` [Qemu-devel] [PATCH 0/4] introduce cpu_physical_memory_map_fast Paolo Bonzini
2011-05-31 9:16 ` Paolo Bonzini
2011-06-06 12:27 ` Paolo Bonzini
2011-06-06 12:56 ` Anthony Liguori
2011-06-06 13:09 ` Paolo Bonzini
2011-06-06 15:44 ` Anthony Liguori
2011-06-06 15:55 ` Paolo Bonzini
2011-05-12 15:32 ` Avi Kivity
2011-05-13 6:33 ` Paolo Bonzini [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=4DCCD0A9.9050706@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi@redhat.com \
--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.