From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org
Subject: qemu/hw/device-assignment: questions about msix_table_page
Date: Mon, 27 Apr 2009 16:13:05 +0300 [thread overview]
Message-ID: <20090427131305.GA2272@redhat.com> (raw)
Sheng, Marcelo,
I've been reading code in qemu/hw/device-assignment.c, and
I have a couple of questions about msi-x implementation:
1. What is the reason that msix_table_page is allocated
with mmap and not with e.g. malloc?
2. msix_table_page has the guest view of the msix table for the device.
However, even this memory isn't mapped into guest directly, instead
msix_mmio_read/msix_mmio_write perform the write in qemu.
Won't it be possible to map this page directly into
guest memory, reducing the overhead for table writes?
Could you shed light on this for me please?
Thanks,
( ------)
( Resending with a sane subject/reply-to address. )
( Sorry about multiple copies.)
--
MST
next reply other threads:[~2009-04-27 13:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 13:13 Michael S. Tsirkin [this message]
[not found] <20090427104117.GB29082@redhat.com>
2009-04-27 13:16 ` Sheng Yang
2009-04-27 13:51 ` qemu/hw/device-assignment: questions about msix_table_page Michael S. Tsirkin
2009-04-27 14:03 ` Sheng Yang
2009-04-27 14:15 ` Michael S. Tsirkin
2009-04-27 14:30 ` Sheng Yang
2009-04-27 14:35 ` Michael S. Tsirkin
2009-05-05 9:51 ` Michael S. Tsirkin
2009-05-05 10:19 ` Marcelo Tosatti
2009-05-05 10:34 ` Michael S. Tsirkin
2009-05-05 10:49 ` Marcelo Tosatti
2009-05-05 11:45 ` Michael S. Tsirkin
2009-05-05 11:51 ` Marcelo Tosatti
2009-05-05 12:46 ` Michael S. Tsirkin
2009-05-06 2:35 ` Sheng Yang
2009-05-06 7:31 ` Michael S. Tsirkin
2009-05-06 8:17 ` Sheng Yang
2009-04-28 9:31 ` 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=20090427131305.GA2272@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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).