From: "Zhao, Yu" <yu.zhao@intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/6] ATS capability support for Intel IOMMU
Date: Fri, 20 Mar 2009 10:47:17 +0800 [thread overview]
Message-ID: <49C303B5.5040707@intel.com> (raw)
In-Reply-To: <20090319193043.583ad601@hobbes.lan>
Jesse Barnes wrote:
> On Thu, 12 Feb 2009 20:50:32 +0800
> Yu Zhao <yu.zhao@intel.com> wrote:
>
>> This patch series implements Address Translation Service support for
>> the Intel IOMMU. ATS makes the PCI Endpoint be able to request the
>> DMA address translation from the IOMMU and cache the translation in
>> the Endpoint, thus alleviate IOMMU pressure and improve the hardware
>> performance in the I/O virtualization environment.
>>
>>
>> Changelog: v2 -> v3
>> 1, throw error message if VT-d hardware detects invalid descriptor
>> on Queued Invalidation interface (David Woodhouse)
>> 2, avoid using pci_find_ext_capability every time when reading ATS
>> Invalidate Queue Depth (Matthew Wilcox)
>> Changelog: v1 -> v2
>> added 'static' prefix to a local LIST_HEAD (Andrew Morton)
>>
>>
>> Yu Zhao (6):
>> PCI: support the ATS capability
>> VT-d: parse ATSR in DMA Remapping Reporting Structure
>> VT-d: add queue invalidation fault status support
>> VT-d: add device IOTLB invalidation support
>> VT-d: cleanup iommu_flush_iotlb_psi and flush_unmaps
>> VT-d: support the device IOTLB
>
> Um nevermind, this should go through the IOMMU tree (David?).
If it's possible, I'd like it go through the PCI tree because the ATS
depends on the SR-IOV. This dependency is not reflected in this v3
series since the SR-IOV is not in-tree and I don't want to break the
build after people apply the ATS on their tree.
So Dave, can I get an ack from you and let Jesse pull the IOMMU change
to his tree? Or let this ATS go to 2.6.31?
Thanks,
Yu
next prev parent reply other threads:[~2009-03-20 2:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 12:50 [PATCH v3 0/6] ATS capability support for Intel IOMMU Yu Zhao
2009-02-12 12:50 ` [PATCH v3 1/6] PCI: support the ATS capability Yu Zhao
2009-02-12 12:50 ` [PATCH v3 2/6] VT-d: parse ATSR in DMA Remapping Reporting Structure Yu Zhao
2009-02-12 12:50 ` [PATCH v3 3/6] VT-d: add queue invalidation fault status support Yu Zhao
2009-02-12 12:50 ` [PATCH v3 4/6] VT-d: add device IOTLB invalidation support Yu Zhao
2009-02-12 12:50 ` [PATCH v3 5/6] VT-d: cleanup iommu_flush_iotlb_psi and flush_unmaps Yu Zhao
2009-02-12 12:50 ` [PATCH v3 6/6] VT-d: support the device IOTLB Yu Zhao
2009-02-14 23:20 ` Grant Grundler
2009-02-26 3:21 ` Yu Zhao
2009-02-13 3:44 ` [PATCH v3 0/6] ATS capability support for Intel IOMMU Matthew Wilcox
2009-02-13 5:27 ` Zhao, Yu
2009-02-14 22:59 ` Grant Grundler
2009-02-26 2:50 ` Yu Zhao
2009-02-26 3:46 ` Greg KH
2009-02-27 7:19 ` Grant Grundler
2009-03-20 2:30 ` Jesse Barnes
2009-03-20 2:30 ` Jesse Barnes
2009-03-20 2:47 ` Zhao, Yu [this message]
2009-03-20 11:15 ` David Woodhouse
2009-03-23 5:22 ` Yu Zhao
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=49C303B5.5040707@intel.com \
--to=yu.zhao@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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