[RFC] [VTD][patch 2/3] vt-d support for pci passthrough: kvm-vtd-user.patch

[RFC] [VTD][patch 2/3] vt-d support for pci passthrough: kvm-vtd-user.patch

[Kay, Allen M]

Kvm-user-mode patch.  Still todo: move vt.d to kvm-intel.ko module.

Signed-off-by: Allen M Kay <allen.m.kay@intel.com>

-----

 Kbuild |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-----

diff --git a/kernel/Kbuild b/kernel/Kbuild
index e3e97ab..7455605 100644
--- a/kernel/Kbuild
+++ b/kernel/Kbuild
@@ -1,7 +1,7 @@
 EXTRA_CFLAGS := -I$(src)/include -include
$(src)/external-module-compat.h
 obj-m := kvm.o kvm-intel.o kvm-amd.o
 kvm-objs := kvm_main.o x86.o mmu.o x86_emulate.o anon_inodes.o irq.o
i8259.o \
-	 lapic.o ioapic.o preempt.o i8254.o
+	 lapic.o ioapic.o preempt.o i8254.o vtd.o
 ifeq ($(CONFIG_KVM_TRACE),y)
 kvm-objs += kvm_trace.o
 endif

-------------------------------------------------------------------------
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

Re: [RFC] [VTD][patch 2/3] vt-d support for pci passthrough: kvm-vtd-user.patch

[Avi Kivity]

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.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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

Re: [RFC] [VTD][patch 2/3] vt-d support for pci passthrough: kvm-vtd-user.patch

[Anthony Liguori]

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