From: Greg KH <gregkh@suse.de>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Ingo Molnar <mingo@redhat.com>, Avi Kivity <avi@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Alexander Graf <agraf@suse.de>,
Han Weidong <weidong.han@intel.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH 0/12] Factor VT-d KVM functions into a generic API (with multiple device assignment support)
Date: Tue, 2 Dec 2008 19:44:05 -0800 [thread overview]
Message-ID: <20081203034405.GA23835@suse.de> (raw)
In-Reply-To: <1228222883-17207-1-git-send-email-joerg.roedel@amd.com>
On Tue, Dec 02, 2008 at 02:01:11PM +0100, Joerg Roedel wrote:
> 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 is the second version of the patchset. The most important change to
> the previous version is that this patchset was rebased to the improved
> API from Han Weidong which supports multiple devices per IOMMU domain.
>
> For completeness, this series also includes the patches from Han with
> some cleanups. So this patchset can be applied on current avi/master
> tree.
Have you tried porting any of the current iommu controllers to this new
framework to see if it works properly for them?
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-03 6:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 13:01 [PATCH 0/12] Factor VT-d KVM functions into a generic API (with multiple device assignment support) Joerg Roedel
2008-12-02 13:01 ` [PATCH 01/12] VT-d: Support multiple device assignment for KVM Joerg Roedel
2008-12-02 13:01 ` [PATCH 02/12] KVM: change to use new APIs for kvm vtd Joerg Roedel
2008-12-02 13:01 ` [PATCH 03/12] KVM: rename vtd.c to iommu.c Joerg Roedel
2008-12-02 13:01 ` [PATCH 04/12] introcude linux/iommu.h for an iommu api Joerg Roedel
2008-12-02 13:01 ` [PATCH 05/12] add frontend implementation for the IOMMU API Joerg Roedel
2008-12-02 13:01 ` [PATCH 06/12] select IOMMU_API when DMAR and/or AMD_IOMMU is selected Joerg Roedel
2008-12-02 13:01 ` [PATCH 07/12] KVM: change KVM iommu.c to use IOMMU API Joerg Roedel
2008-12-02 13:01 ` [PATCH 08/12] VT-d: adapt domain init and destroy functions for " Joerg Roedel
2008-12-02 13:01 ` [PATCH 09/12] VT-d: adapt device attach and detach " Joerg Roedel
2008-12-02 13:01 ` [PATCH 10/12] VT-d: adapt domain map and unmap " Joerg Roedel
2008-12-02 13:01 ` [PATCH 11/12] VT-d: adapt domain iova_to_phys function " Joerg Roedel
2008-12-02 13:01 ` [PATCH 12/12] VT-d: register functions for the " Joerg Roedel
2008-12-03 3:44 ` Greg KH [this message]
2008-12-03 7:50 ` [PATCH 0/12] Factor VT-d KVM functions into a generic API (with multiple device assignment support) Joerg Roedel
2008-12-03 7:53 ` Greg KH
2008-12-03 9:03 ` Joerg Roedel
2008-12-04 10:47 ` Muli Ben-Yehuda
2008-12-03 10:17 ` 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=20081203034405.GA23835@suse.de \
--to=gregkh@suse.de \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--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