From: Avi Kivity <avi@qumranet.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: kvm@vger.kernel.org, Amit Shah <amit.shah@qumranet.com>,
Muli Ben-Yehuda <MULI@il.ibm.com>,
Ben-Ami Yassour <benami@il.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Chris Wright <chrisw@redhat.com>,
"Han, Weidong" <weidong.han@intel.com>
Subject: Re: [PATCH 0/4][VTD] kvm vt-d support kernel changes
Date: Fri, 20 Jun 2008 21:00:34 +0300 [thread overview]
Message-ID: <485BF042.2070400@qumranet.com> (raw)
In-Reply-To: <1FE6DD409037234FAB833C420AA843EC018831C6@orsmsx424.amr.corp.intel.com>
Kay, Allen M wrote:
> Following four patches contains changes for enabling VT-d PCI
> passthrough. The patches are located at:
>
> git.kernel.org/pub/scm/linux/kernel/git/amit/kvm.git vtd
>
>
Please attach patches as text/plain or inline them. It's very annoying
to review application/octet-stream patches.
> I have incorporated most of the feedbacks from the last RFC submission.
> It was tested with passthrough an E1000 NIC to a linux guest using
> irqhook interrupt injection mechanism.
>
> 1) intel_iommu_move.patch: move intel-iommu.h/iova.h to include/linux.
> 2) intel_iommu_mods.patch: kvm modifications to intel-iommu.c.
>
What's the upstream path for these (who's the subsystem maintainer)?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-06-20 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 0:39 [PATCH 0/4][VTD] kvm vt-d support kernel changes Kay, Allen M
2008-06-10 12:53 ` Muli Ben-Yehuda
2008-06-10 19:45 ` Kay, Allen M
2008-06-12 12:08 ` Muli Ben-Yehuda
2008-06-20 18:00 ` Avi Kivity [this message]
2008-06-21 3:33 ` Han, Weidong
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=485BF042.2070400@qumranet.com \
--to=avi@qumranet.com \
--cc=MULI@il.ibm.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=benami@il.ibm.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=weidong.han@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