From: Jason Gunthorpe <jgg@nvidia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: iommu@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Kevin Tian <kevin.tian@intel.com>
Subject: [GIT PULL] Please pull IOMMUFD subsystem changes #2
Date: Wed, 27 Nov 2024 11:57:12 -0400 [thread overview]
Message-ID: <20241127155712.GA1470954@nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2314 bytes --]
Hi Linus,
As I mentioned beore this is the two patches that needed both iommufd
and iommu tree merged together. You have merged both so this is the
remainder.
It has been in linux-next since before you pulled from Joerg. I left
it based with my merge of Joerg's tree to iommufd rather than rebasing
it to your merge of Joerg's tree.
Due to the many different driver trees in iommu it is helpful if
global changes like this make -rc1.
Thanks,
Jason
The following changes since commit 42f0cbb2a253bcd7d4f20e80462014622f19d88e:
Merge branches 'intel/vt-d', 'amd/amd-vi' and 'iommufd/arm-smmuv3-nested' into next (2024-11-15 09:27:43 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git tags/for-linus-iommufd
for you to fetch changes up to d53764723ecd639a0cc0c5ad24146847fc09f78d:
iommu: Rename ops->domain_alloc_user() to domain_alloc_paging_flags() (2024-11-22 14:43:45 -0400)
----------------------------------------------------------------
iommufd 6.13 merge window pull #2
Change the driver callback op domain_alloc_user() into two ops
domain_alloc_paging_flags() and domain_alloc_nesting() that better
describe what the ops are expected to do. There will be per-driver cleanup
based on this going into the next cycle via the driver trees.
----------------------------------------------------------------
Jason Gunthorpe (3):
Merge tag 'iommu-updates-v6.13' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/iommu/linux into iommufd.git
iommu: Add ops->domain_alloc_nested()
iommu: Rename ops->domain_alloc_user() to domain_alloc_paging_flags()
drivers/iommu/amd/iommu.c | 9 ++++-----
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 9 ++++-----
drivers/iommu/intel/iommu.c | 15 ++++-----------
drivers/iommu/intel/iommu.h | 6 ++++--
drivers/iommu/intel/nested.c | 11 +++++++++--
drivers/iommu/iommu.c | 4 ++--
drivers/iommu/iommufd/hw_pagetable.c | 16 ++++++++--------
drivers/iommu/iommufd/selftest.c | 15 ++++++---------
include/linux/iommu.h | 27 ++++++++++++++++-----------
9 files changed, 57 insertions(+), 55 deletions(-)
(diffstat from tag for-linus-iommufd-merged)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-11-27 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 15:57 Jason Gunthorpe [this message]
2024-11-27 22:58 ` [GIT PULL] Please pull IOMMUFD subsystem changes #2 pr-tracker-bot
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=20241127155712.GA1470954@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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