From: Joerg Roedel <joerg.roedel@amd.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org
Cc: avi@redhat.com, weidong.han@intel.com, mingo@redhat.com,
dwmw2@infradead.org, amit.shah@redhat.com
Subject: [PATCH 0/9] Factor VT-d KVM functions into a generic API
Date: Thu, 27 Nov 2008 16:40:45 +0100 [thread overview]
Message-ID: <1227800454-9555-1-git-send-email-joerg.roedel@amd.com> (raw)
Hi,
this patch series makes the current KVM device passthrough code generic
enough so that other IOMMU implementation can also plug into this code.
It works by factoring the functions Vt-d code exports to KVM into a
generic interface which allows different backends.
This a basic implementation of a generic interface. It can and should be
improved later to support more types of hardware IOMMUs then VT-d and
AMD IOMMU.
Since I have no VT-d hardware available these patches are only compile
tested for now.
Please review, comment and test these patches.
Thanks,
Joerg
diffstat:
arch/ia64/Kconfig | 3 +
arch/ia64/kvm/Makefile | 2 +-
arch/x86/Kconfig | 3 +
arch/x86/include/asm/kvm_host.h | 3 +-
arch/x86/kvm/Makefile | 2 +-
drivers/base/Makefile | 1 +
drivers/base/iommu.c | 94 +++++++++++++++++++
drivers/pci/intel-iommu.c | 91 ++++++++++++++++++
include/linux/iommu.h | 100 ++++++++++++++++++++
virt/kvm/iommu.c | 193 +++++++++++++++++++++++++++++++++++++++
virt/kvm/vtd.c | 191 --------------------------------------
next reply other threads:[~2008-11-27 15:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 15:40 Joerg Roedel [this message]
2008-11-27 15:40 ` [PATCH 1/9] KVM: rename vtd.c to iommu.c Joerg Roedel
2008-11-27 16:32 ` Avi Kivity
2008-11-27 17:05 ` Joerg Roedel
2008-11-30 10:12 ` Avi Kivity
2008-11-27 15:40 ` [PATCH 2/9] introcude linux/iommu.h for an iommu api Joerg Roedel
2008-11-28 2:50 ` Han, Weidong
2008-11-27 15:40 ` [PATCH 3/9] add frontend implementation for the IOMMU API Joerg Roedel
2008-11-28 2:50 ` Han, Weidong
2008-12-01 18:16 ` 'Joerg Roedel'
2008-11-28 9:40 ` FUJITA Tomonori
2008-11-28 11:31 ` Joerg Roedel
2008-12-01 8:38 ` FUJITA Tomonori
2008-12-01 12:00 ` Joerg Roedel
2008-12-01 13:02 ` Muli Ben-Yehuda
2008-12-01 14:07 ` Joerg Roedel
2008-12-01 14:18 ` FUJITA Tomonori
2008-12-01 14:27 ` Joerg Roedel
2008-12-01 14:33 ` Avi Kivity
2008-12-01 15:46 ` Joerg Roedel
2008-12-01 15:58 ` FUJITA Tomonori
2008-12-01 16:59 ` Joerg Roedel
2008-12-01 17:27 ` Joerg Roedel
2008-11-27 15:40 ` [PATCH 4/9] select IOMMU_API when DMAR and/or AMD_IOMMU is selected Joerg Roedel
2008-11-27 15:40 ` [PATCH 5/9] VT-d: add domain init and destroy functions for IOMMU API Joerg Roedel
2008-11-27 15:40 ` [PATCH 6/9] VT-d: add device attach and detach " Joerg Roedel
2008-11-27 15:40 ` [PATCH 7/9] VT-d: add domain map and iova_to_phys " Joerg Roedel
2008-11-27 15:40 ` [PATCH 8/9] VT-d: register functions for the " Joerg Roedel
2008-11-28 2:50 ` Han, Weidong
2008-11-27 15:40 ` [PATCH 9/9] KVM: change KVM iommu.c to use " Joerg Roedel
2008-11-27 15:43 ` [osrc-patches] [PATCH 0/9] Factor VT-d KVM functions into a generic API Joerg Roedel
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=1227800454-9555-1-git-send-email-joerg.roedel@amd.com \
--to=joerg.roedel@amd.com \
--cc=amit.shah@redhat.com \
--cc=avi@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®