From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@infradead.org>,
Kevin Tian <kevin.tian@intel.com>, Will Deacon <will@kernel.org>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] iommu: Extend changing default domain to normal group
Date: Wed, 22 Mar 2023 15:45:40 +0100 [thread overview]
Message-ID: <ZBsUlHuZ4kLfSGXI@8bytes.org> (raw)
In-Reply-To: <20230322064956.263419-1-baolu.lu@linux.intel.com>
On Wed, Mar 22, 2023 at 02:49:50PM +0800, Lu Baolu wrote:
> Lu Baolu (6):
> iommu/ipmmu-vmsa: Call arm_iommu_release_mapping() in release path
> iommu: Split iommu_group_remove_device() into helpers
> iommu: Same critical region for device release and removal
> iommu: Move lock from iommu_change_dev_def_domain() to its caller
> iommu: Replace device_lock() with group->mutex
> iommu: Cleanup iommu_change_dev_def_domain()
>
> drivers/iommu/iommu.c | 273 ++++++++----------
> drivers/iommu/ipmmu-vmsa.c | 14 +-
> .../ABI/testing/sysfs-kernel-iommu_groups | 1 -
> 3 files changed, 130 insertions(+), 158 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2023-03-22 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 6:49 [PATCH v4 0/6] iommu: Extend changing default domain to normal group Lu Baolu
2023-03-22 6:49 ` [PATCH v4 1/6] iommu/ipmmu-vmsa: Call arm_iommu_release_mapping() in release path Lu Baolu
2023-03-22 6:49 ` [PATCH v4 2/6] iommu: Split iommu_group_remove_device() into helpers Lu Baolu
2023-03-22 6:49 ` [PATCH v4 3/6] iommu: Same critical region for device release and removal Lu Baolu
2023-03-22 6:49 ` [PATCH v4 4/6] iommu: Move lock from iommu_change_dev_def_domain() to its caller Lu Baolu
2023-03-22 6:49 ` [PATCH v4 5/6] iommu: Replace device_lock() with group->mutex Lu Baolu
2023-03-22 6:49 ` [PATCH v4 6/6] iommu: Cleanup iommu_change_dev_def_domain() Lu Baolu
2023-03-22 14:45 ` Joerg Roedel [this message]
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=ZBsUlHuZ4kLfSGXI@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.