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
Date: Thu, 22 Feb 2024 09:23:04 -0400 [thread overview]
Message-ID: <20240222132304.GA3882153@nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
Hi Linus,
Some small fixes and updates for the selftest. I'm aware of some
syzkaller issues that hopefully will get fixes into another PR before
the merge window.
The following changes since commit 54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478:
Linux 6.8-rc3 (2024-02-04 12:20:36 +0000)
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 510325e5ac5f45c1180189d3bfc108c54bf64544:
selftests/iommu: fix the config fragment (2024-02-22 09:02:05 -0400)
----------------------------------------------------------------
iommufd for 6.8 rc
- Fix dirty tracking bitmap collection when using reporting bitmaps that
are not neatly aligned to u64's or match the IO page table radix tree
layout.
- Add self tests to cover the cases that were found to be broken.
- Add missing enforcement of invalidation type in the uapi.
- Fix selftest config generation
----------------------------------------------------------------
Jason Gunthorpe (1):
iommufd: Reject non-zero data_type if no data_len is provided
Joao Martins (9):
iommufd/iova_bitmap: Bounds check mapped::pages access
iommufd/iova_bitmap: Switch iova_bitmap::bitmap to an u8 array
iommufd/selftest: Test u64 unaligned bitmaps
iommufd/iova_bitmap: Handle recording beyond the mapped pages
iommufd/selftest: Refactor dirty bitmap tests
iommufd/selftest: Refactor mock_domain_read_and_clear_dirty()
iommufd/selftest: Hugepage mock domain support
iommufd/selftest: Add mock IO hugepages tests
iommufd/iova_bitmap: Consider page offset for the pages to be pinned
Muhammad Usama Anjum (1):
selftests/iommu: fix the config fragment
drivers/iommu/iommufd/hw_pagetable.c | 3 +-
drivers/iommu/iommufd/iommufd_test.h | 1 +
drivers/iommu/iommufd/iova_bitmap.c | 68 +++++++++++++++++++----
drivers/iommu/iommufd/selftest.c | 79 ++++++++++++++++++++-------
tools/testing/selftests/iommu/config | 5 +-
tools/testing/selftests/iommu/iommufd.c | 78 +++++++++++++++++++++-----
tools/testing/selftests/iommu/iommufd_utils.h | 39 ++++++++-----
7 files changed, 210 insertions(+), 63 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-02-22 13:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 13:23 Jason Gunthorpe [this message]
2024-02-22 20:03 ` [GIT PULL] Please pull IOMMUFD subsystem changes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 17:29 Jason Gunthorpe
2024-04-19 21:07 ` pr-tracker-bot
2024-03-02 0:08 Jason Gunthorpe
2024-03-02 1:31 ` pr-tracker-bot
2024-01-12 17:49 Jason Gunthorpe
2024-01-18 23:35 ` pr-tracker-bot
2023-12-04 19:35 Jason Gunthorpe
2023-12-04 21:59 ` pr-tracker-bot
2023-10-31 13:14 Jason Gunthorpe
2023-11-02 2:51 ` pr-tracker-bot
2023-08-30 23:40 Jason Gunthorpe
2023-08-31 3:50 ` pr-tracker-bot
2023-08-31 3:59 ` Linus Torvalds
2023-08-31 16:43 ` Jason Gunthorpe
2023-07-28 13:48 Jason Gunthorpe
2023-07-28 18:39 ` pr-tracker-bot
2023-06-28 14:04 Jason Gunthorpe
2023-06-30 4:16 ` pr-tracker-bot
2023-04-25 14:46 Jason Gunthorpe
2023-04-27 17:15 ` pr-tracker-bot
2023-04-06 13:34 Jason Gunthorpe
2023-04-06 18:46 ` pr-tracker-bot
2023-02-21 15:39 Jason Gunthorpe
2023-02-24 22:50 ` Linus Torvalds
2023-02-25 0:02 ` Jason Gunthorpe
2023-02-25 0:50 ` Linus Torvalds
2023-02-24 23:27 ` pr-tracker-bot
2022-12-12 18:30 Jason Gunthorpe
2022-12-14 18:04 ` 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=20240222132304.GA3882153@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;
as well as URLs for NNTP newsgroup(s).