From: "Yang, Sheng" <sheng.yang@intel.com>
To: kvm@vger.kernel.org
Cc: Ben-Ami Yassour <benami@il.ibm.com>,
avi@qumranet.com, amit.shah@qumranet.com, muli@il.ibm.com,
weidong.han@intel.com, "Kay, Allen M" <allen.m.kay@intel.com>
Subject: Re: [PATCH 2/2] KVM: Device assignemnt with VT-d
Date: Wed, 13 Aug 2008 17:38:25 +0800 [thread overview]
Message-ID: <200808131738.25940.sheng.yang@intel.com> (raw)
In-Reply-To: <1218118487-7657-2-git-send-email-benami@il.ibm.com>
On Thursday 07 August 2008 22:14:47 Ben-Ami Yassour wrote:
> Based on a patch by: Kay, Allen M <allen.m.kay@intel.com>
>
> This patch enables pci device assignment based on VT-d support.
> When a device is assigned to the guest, the guest memory is pinned
> and the mapping is updated in the VT-d IOMMU.
>
I am afraid there still some compatible problem...
> Signed-off-by: Kay, Allen M <allen.m.kay@intel.com>
> Signed-off-by: Weidong Han <weidong.han@intel.com>
> Signed-off-by: Ben-Ami Yassour <benami@il.ibm.com>
> ---
> arch/x86/kvm/Makefile | 3 +
> arch/x86/kvm/vtd.c | 203
[snip]
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index a97157c..5cfc21a 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -35,6 +35,7 @@
> #include <linux/module.h>
> #include <linux/mman.h>
> #include <linux/highmem.h>
> +#include <linux/intel-iommu.h>
This broken external kernel modules before 2.6.27... If we wrapped it
with CONFIG_DMAR, it would also broken the commit before the patch
checked in and after DMAR enabled in kernel... Need a version number
judgement?
> diff --git a/include/asm-x86/kvm_host.h
> b/include/asm-x86/kvm_host.h index ef019b5..b141949 100644
> --- a/include/asm-x86/kvm_host.h
> +++ b/include/asm-x86/kvm_host.h
> @@ -354,6 +354,7 @@ struct kvm_arch{
> */
> struct list_head active_mmu_pages;
> struct list_head assigned_dev_head;
> + struct dmar_domain *intel_iommu_domain;
Need wrapped by CONFIG_DMAR?
--
regards
Yang, Sheng
next prev parent reply other threads:[~2008-08-13 9:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 14:14 [PATCH 1/2] VT-d: changes to support KVM Ben-Ami Yassour
2008-08-07 14:14 ` [PATCH 2/2] KVM: Device assignemnt with VT-d Ben-Ami Yassour
2008-08-07 14:19 ` Patch-set description Ben-Ami Yassour
2008-08-13 9:38 ` Yang, Sheng [this message]
2008-08-13 9:46 ` [PATCH 2/2] KVM: Device assignemnt with VT-d Avi Kivity
2008-08-13 10:20 ` Yang, Sheng
2008-08-21 6:43 ` Amit Shah
2008-08-21 11:05 ` Ben-Ami Yassour
2008-08-21 13:46 ` Amit Shah
2008-08-22 7:44 ` Amit Shah
2008-08-22 18:18 ` Avi Kivity
2008-08-23 8:57 ` Amit Shah
2008-08-23 9:28 ` Avi Kivity
2008-08-23 9:43 ` Amit Shah
2008-08-24 10:00 ` Avi Kivity
2008-08-25 5:49 ` Han, Weidong
2008-08-26 7:32 ` Amit Shah
2008-08-26 8:25 ` Avi Kivity
2008-08-13 9:21 ` [PATCH 1/2] VT-d: changes to support KVM Yang, Sheng
2008-08-13 9:21 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-08-21 11:10 VT-d support for device assignment Ben-Ami Yassour
2008-08-21 11:10 ` [PATCH 1/2] VT-d: changes to support KVM Ben-Ami Yassour
2008-08-21 11:10 ` [PATCH 2/2] KVM: Device assignemnt with VT-d Ben-Ami Yassour
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=200808131738.25940.sheng.yang@intel.com \
--to=sheng.yang@intel.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@qumranet.com \
--cc=avi@qumranet.com \
--cc=benami@il.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=muli@il.ibm.com \
--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