From: Joerg Roedel <joerg.roedel@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <dwmw2@infradead.org>, <iommu@lists.linux-foundation.org>,
<bhelgaas@google.com>, <benh@kernel.crashing.org>,
<aik@ozlabs.ru>, <david@gibson.dropbear.id.au>,
<konrad.wilk@oracle.com>, <linux-kernel@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<ddutile@redhat.com>, <liuj97@gmail.com>
Subject: Re: [PATCH v2 0/7] IOMMU: Groups support
Date: Wed, 6 Jun 2012 13:05:14 +0200 [thread overview]
Message-ID: <20120606110514.GG757@amd.com> (raw)
In-Reply-To: <20120530201424.31527.33142.stgit@bling.home>
On Wed, May 30, 2012 at 02:18:29PM -0600, Alex Williamson wrote:
> v2:
> - Trickle down changes from pci_get_dma_source() to better handle
> PCI device reference counting in IOMMU driver patches
Okay, I looked again over the code and looks good for merging to me. The
IOMMU Groups code depends on changes in the PCI code. We need to work
out how to merge this.
Bjorn,
I need the PCI changes before I can merge the IOMMU Groups code. There
are two ways that would work for me:
a) You Ack the PCI patch-set from Alex and I put it into my tree
and merge the IOMMU Group code on-top, or
b) You merge the PCI related patch-set into a seperate branch
which you can merge into your next-branch and which I can
pull in to merge IOMMU Groups on-top.
Please let me know what works best for you.
What I would also appreciate are a few more Acks from other IOMMU
maintainers (David W.?) and from the Power side.
Thanks,
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2012-06-06 11:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 20:18 [PATCH v2 0/7] IOMMU: Groups support Alex Williamson
2012-05-30 20:18 ` [PATCH v2 1/7] driver core: Add iommu_group tracking to struct device Alex Williamson
2012-06-20 5:45 ` Benjamin Herrenschmidt
2012-05-30 20:18 ` [PATCH v2 2/7] iommu: IOMMU Groups Alex Williamson
2012-06-20 10:01 ` Benjamin Herrenschmidt
2012-06-20 16:48 ` Alex Williamson
2012-06-21 0:07 ` Benjamin Herrenschmidt
2012-05-30 20:19 ` [PATCH v2 3/7] amd_iommu: Support IOMMU groups Alex Williamson
2012-05-30 20:19 ` [PATCH v2 4/7] intel-iommu: " Alex Williamson
2012-05-30 20:19 ` [PATCH v2 5/7] amd_iommu: Make use of DMA quirks and ACS checks in " Alex Williamson
2012-05-30 20:19 ` [PATCH v2 6/7] intel-iommu: " Alex Williamson
2012-05-31 19:47 ` Don Dutile
2012-05-31 20:41 ` Alex Williamson
2012-05-30 20:19 ` [PATCH v2 7/7] iommu: Remove group_mf Alex Williamson
2012-06-06 11:05 ` Joerg Roedel [this message]
2012-06-11 15:37 ` [PATCH v2 0/7] IOMMU: Groups support Alex Williamson
2012-06-12 2:55 ` Bjorn Helgaas
2012-06-18 17:31 ` Alex Williamson
2012-06-19 9:49 ` Joerg Roedel
2012-06-19 10:40 ` Benjamin Herrenschmidt
2012-06-25 11:29 ` 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=20120606110514.GG757@amd.com \
--to=joerg.roedel@amd.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=david@gibson.dropbear.id.au \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.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;
as well as URLs for NNTP newsgroup(s).