From: Lu Baolu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Nicolin Chen <nicolinc@nvidia.com>
Cc: iommu@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH v3 0/2] Prevent RESV_DIRECT devices from user assignment
Date: Mon, 24 Jul 2023 14:03:50 +0800 [thread overview]
Message-ID: <20230724060352.113458-1-baolu.lu@linux.intel.com> (raw)
These are follow-up patches on this discussion:
https://lore.kernel.org/linux-iommu/BN9PR11MB5276E84229B5BD952D78E9598C639@BN9PR11MB5276.namprd11.prod.outlook.com
I just summarized the ideas and code into a real patch series. Please
help to review and merge.
Change log:
v3:
- Rename "requires_direct" to "require_direct".
- Refine some comments.
- Rebase on the top of iommu next branch.
v2: https://lore.kernel.org/linux-iommu/20230713043248.41315-1-baolu.lu@linux.intel.com/
- Move "pg_size == 0" check out of the loop.
- Rebase on the top of v6.5-rc1.
v1: https://lore.kernel.org/linux-iommu/20230607035145.343698-1-baolu.lu@linux.intel.com/
Lu Baolu (2):
iommu: Prevent RESV_DIRECT devices from blocking domains
iommu/vt-d: Remove rmrr check in domain attaching device path
include/linux/iommu.h | 2 ++
drivers/iommu/intel/iommu.c | 58 -------------------------------------
drivers/iommu/iommu.c | 37 ++++++++++++++++-------
3 files changed, 29 insertions(+), 68 deletions(-)
--
2.34.1
next reply other threads:[~2023-07-24 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 6:03 Lu Baolu [this message]
2023-07-24 6:03 ` [PATCH v3 1/2] iommu: Prevent RESV_DIRECT devices from blocking domains Lu Baolu
2023-08-07 12:30 ` Joerg Roedel
2023-07-24 6:03 ` [PATCH v3 2/2] iommu/vt-d: Remove rmrr check in domain attaching device path Lu Baolu
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=20230724060352.113458-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--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.