From: Avi Kivity <avi@qumranet.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: Chris Wright <chrisw@redhat.com>,
kvm-devel@lists.sourceforge.net,
Ben-Ami Yassour1 <benami@il.ibm.com>
Subject: Re: [RFC] [VTD][patch 0/3] vt-d support for pci passthrough
Date: Tue, 06 May 2008 13:27:54 +0300 [thread overview]
Message-ID: <482032AA.7040404@qumranet.com> (raw)
In-Reply-To: <1FE6DD409037234FAB833C420AA843EC01438CB1@orsmsx424.amr.corp.intel.com>
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
prev parent reply other threads:[~2008-05-06 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 21:35 [RFC] [VTD][patch 0/3] vt-d support for pci passthrough Kay, Allen M
2008-05-06 7:39 ` Amit Shah
2008-05-06 10:27 ` Avi Kivity [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=482032AA.7040404@qumranet.com \
--to=avi@qumranet.com \
--cc=allen.m.kay@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox