From: Robin Murphy <robin.murphy@arm.com>
To: joro@8bytes.org, jgg@ziepe.ca, kevin.tian@intel.com
Cc: will@kernel.org, iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] iommufd/selftest: Fix and cleanup for bus ops
Date: Tue, 28 Nov 2023 10:42:10 +0000 [thread overview]
Message-ID: <cover.1701165201.git.robin.murphy@arm.com> (raw)
Hi all,
The bus ops removal relies on iommu_ops_from_fwnode(NULL) finding the
"global" hardware driver ops on relevant platforms. Unfortunately I
overlooked that this will also match the IOMMUFD mock driver, such that
it can end up claiming to be the IOMMU for real platform etc. devices
which don't have an IOMMU described by a fwspec. This mini-series
addresses that.
I've split it so patch #1 is minimal fix that mitigates the issue and
could be applied independently, then patch #2 then builds on it to take
full advantage of the new machinery and coexist as a normal IOMMU
driver. However they could be squashed if preferred.
Thanks,
Robin.
Robin Murphy (2):
iommufd/selftest: Use a fwnode to distinguish devices
iommufd/selftest: Use normal IOMMU registration
drivers/iommu/iommu-priv.h | 7 -----
drivers/iommu/iommu.c | 46 +++-------------------------
drivers/iommu/iommufd/iommufd_test.h | 2 ++
drivers/iommu/iommufd/selftest.c | 45 +++++++++++++--------------
4 files changed, 27 insertions(+), 73 deletions(-)
--
2.39.2.101.g768bb238c484.dirty
next reply other threads:[~2023-11-28 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 10:42 Robin Murphy [this message]
2023-11-28 10:42 ` [PATCH 1/2] iommufd/selftest: Use a fwnode to distinguish devices Robin Murphy
2023-11-28 14:43 ` Jason Gunthorpe
2023-11-28 16:02 ` Robin Murphy
2023-11-28 16:33 ` Jason Gunthorpe
2023-11-28 17:36 ` Robin Murphy
2023-11-28 19:07 ` Jason Gunthorpe
2023-11-28 10:42 ` [PATCH 2/2] iommufd/selftest: Use normal IOMMU registration Robin Murphy
2023-11-28 14:35 ` Jason Gunthorpe
2023-11-28 14:53 ` Robin Murphy
2023-11-28 14:56 ` Jason Gunthorpe
2023-12-06 5:48 ` kernel test robot
2023-12-06 10:42 ` kernel test robot
2023-12-06 11:35 ` kernel test robot
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=cover.1701165201.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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.