>We have to ensure we don't swap KVM guest memory while using hardware
>pass-through, but AFAICT, we do not need to make the memory
>non-reclaimable As long as we reprogram the IOMMU with a new, valid,
>mapping everything should be fine. mlock() really gives us the right
>semantics.
>
>Semant
>> +
>> +#define DEFAULT_DOMAIN_ADDRESS_WIDTH 48
>> +
>> +struct dmar_drhd_unit * dmar_find_matched_drhd_unit(struct pci_dev
>> *dev);
>> +struct dmar_domain * iommu_alloc_domain(struct intel_iommu *iommu);
>> +void iommu_free_domain(struct dmar_domain *domain);
>> +int domain_init(struct dmar_doma
Intel-iommu driver changes for kvm vt-d support. Important changes are
in intel-iommu.c. The rest of the changes are for moving intel-iommu.h
and iova.h from drivers/pci directory to include/linux directory.
Signed-off-by: Allen M Kay <[EMAIL PROTECTED]>
b/drivers/pci/dmar.c |
Kvm-user-mode patch. Still todo: move vt.d to kvm-intel.ko module.
Signed-off-by: Allen M Kay <[EMAIL PROTECTED]>
-
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/ker
Kvm kernel changes.
Signed-off-by: Allen M Kay <[EMAIL PROTECTED]>
--
arch/x86/kvm/Makefile |2
arch/x86/kvm/vtd.c | 183
+
arch/x86/kvm/x86.c |7 +
include/asm-x86/kvm_host.h |3
include/asm-x86/kvm_para.h |
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 inje
