[RFC] [VTD][patch 0/3] vt-d support for pci passthrough

[RFC] [VTD][patch 0/3] vt-d support for pci passthrough

[Kay, Allen M]

Following three patches contains vt-d support for pci passthrough.  It
contains diff's base on Amit's 4/22 passthrough tree.

The hardware environment used for this work is an Intel Weybridge system
(Q35).  The passthrough device is an E1000 NIC. I'm still using irqhook
mechanism for interrupt injection as I had problem with irqchip
machanism.  Following is the command line I used  to start the guest.

/usr/local/bin/qemu-system-x86_64 -boot c -hda /etc/xen/fc5_32.img -m
256 -net none -pcidevice e1000/01:00.0-16 -no-kvm-irqchip

Remaining tasks include:

1) Generated vtd.o with kvm-intel.ko instead of kvm.ko.
2) Make iommu hooks in generic code to be non-Intel specific

Let me know of your feedbacks.  Thanks.

Allen

-------------------------------------------------------------------------
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 0/3] vt-d support for pci passthrough

[Amit Shah]

On Tuesday 06 May 2008 03:05:30 Kay, Allen M wrote:
> Following three patches contains vt-d support for pci passthrough.  It
> contains diff's base on Amit's 4/22 passthrough tree.
>
> The hardware environment used for this work is an Intel Weybridge system
> (Q35).  The passthrough device is an E1000 NIC. I'm still using irqhook
> mechanism for interrupt injection as I had problem with irqchip
> machanism.  Following is the command line I used  to start the guest.

Can you tell me what the problem with in-kernel irqchip is? Last time you 
mentioned there was a warning that came up when the guest exited. That 
shouldn't have stopped it from working, though

> /usr/local/bin/qemu-system-x86_64 -boot c -hda /etc/xen/fc5_32.img -m
> 256 -net none -pcidevice e1000/01:00.0-16 -no-kvm-irqchip
>
> Remaining tasks include:
>
> 1) Generated vtd.o with kvm-intel.ko instead of kvm.ko.
> 2) Make iommu hooks in generic code to be non-Intel specific

This is a good idea but will need collaboration with a lot of vendors.

> Let me know of your feedbacks.  Thanks.
>
> Allen

Amit

-------------------------------------------------------------------------
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 0/3] vt-d support for pci passthrough

[Avi Kivity]

Kay, Allen M wrote:
> Following three patches contains vt-d support for pci passthrough.  It
> contains diff's base on Amit's 4/22 passthrough tree.
>
> The hardware environment used for this work is an Intel Weybridge system
> (Q35).  The passthrough device is an E1000 NIC. I'm still using irqhook
> mechanism for interrupt injection as I had problem with irqchip
> machanism.  Following is the command line I used  to start the guest.
>
> /usr/local/bin/qemu-system-x86_64 -boot c -hda /etc/xen/fc5_32.img -m
> 256 -net none -pcidevice e1000/01:00.0-16 -no-kvm-irqchip
>
> Remaining tasks include:
>
> 1) Generated vtd.o with kvm-intel.ko instead of kvm.ko.
> 2) Make iommu hooks in generic code to be non-Intel specific
>   

Eventually we will want to make it even non-x86 specific; ia64 will 
probably be able to share, and maybe ppc someday.

That needn't be done at once, though.

Your mail client mangles the patches, please attach or use git send-email.

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