From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: Chris Wright <chrisw@redhat.com>,
kvm-devel@lists.sourceforge.net, "Kay,
Allen M" <allen.m.kay@intel.com>,
Ben-Ami Yassour1 <benami@il.ibm.com>
Subject: Re: [RFC] [VTD][patch 2/3] vt-d support for pci passthrough: kvm-vtd-user.patch
Date: Tue, 06 May 2008 19:39:50 -0500 [thread overview]
Message-ID: <4820FA56.8000200@codemonkey.ws> (raw)
In-Reply-To: <482034C0.90808@qumranet.com>
Avi Kivity wrote:
> Kay, Allen M wrote:
>
>> Still todo: move vt.d to kvm-intel.ko module.
>>
>>
>
> Not sure it's the right thing to do. If we get the iommus abstracted
> properly, we can rename vtd.c to dma.c and move it to virt/kvm/.
>
> The code is certainly a lot more about managing memory than anything vmx
> specific. It's hardly x86 specific, even.
>
Really, an external interface to KVM that allowed someone to query the
GPA => PA mapping would suffice. It should not fault in pages that
aren't present and we should provide notifications for when the mapping
changes for a given reason. Userspace can enforce the requirement that
memory remains present via mlock(). This allows us to implement a PV
API for DMA registration without the IOMMU code having any particular
knowledge of it.
Regards,
Anthony Liguori
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-05-07 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 21:37 [RFC] [VTD][patch 2/3] vt-d support for pci passthrough: kvm-vtd-user.patch Kay, Allen M
2008-05-06 10:36 ` Avi Kivity
2008-05-07 0:39 ` Anthony Liguori [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=4820FA56.8000200@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=allen.m.kay@intel.com \
--cc=avi@qumranet.com \
--cc=benami@il.ibm.com \
--cc=chrisw@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
/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.