From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: quic_saipraka@quicinc.com, konrad.dybcio@somainline.org,
bjorn.andersson@linaro.org, linux-tegra@vger.kernel.org,
thierry.reding@gmail.com, will@kernel.org, zhang.lyra@gmail.com,
joro@8bytes.org, jon@solid-run.com, jonathanh@nvidia.com,
iommu@lists.linux.dev, agross@kernel.org,
linux-arm-kernel@lists.infradead.org, jgg@nvidia.com,
yangyingliang@huawei.com, orsonzhai@gmail.com,
kevin.tian@intel.com, linux-arm-msm@vger.kernel.org,
robin.murphy@arm.com, christophe.jaillet@wanadoo.fr,
baolin.wang@linux.alibaba.com, thunder.leizhen@huawei.com,
matthias.bgg@gmail.com, tglx@linutronix.de,
virtualization@lists.linux-foundation.org, yong.wu@mediatek.com,
dwmw2@infradead.org, linux-kernel@vger.kernel.org,
shameerali.kolothum.thodi@huawei.com, robdclark@gmail.com,
suravee.suthikulpanit@amd.com,
linux-mediatek@lists.infradead.org, sricharan@codeaurora.org,
baolu.lu@linux.intel.com
Subject: Re: [PATCH v4 0/6] Define EINVAL as device/domain incompatibility
Date: Wed, 21 Sep 2022 09:55:01 +0100 [thread overview]
Message-ID: <YyrRZXVWWxBhW3ST@myrica> (raw)
In-Reply-To: <cover.1663744983.git.nicolinc@nvidia.com>
On Wed, Sep 21, 2022 at 01:22:31AM -0700, Nicolin Chen wrote:
> This series is to replace the previous EMEDIUMTYPE patch in a VFIO series:
> https://lore.kernel.org/kvm/Yxnt9uQTmbqul5lf@8bytes.org/
>
> The purpose is to regulate all existing ->attach_dev callback functions to
> use EINVAL exclusively for an incompatibility error between a device and a
> domain. This allows VFIO and IOMMUFD to detect such a soft error, and then
> try a different domain with the same device.
[...]
> drivers/iommu/amd/iommu.c | 12 +----
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 11 +---
> drivers/iommu/arm/arm-smmu/arm-smmu.c | 3 --
> drivers/iommu/arm/arm-smmu/qcom_iommu.c | 7 +--
> drivers/iommu/fsl_pamu.c | 2 +-
> drivers/iommu/fsl_pamu_domain.c | 4 +-
> drivers/iommu/intel/iommu.c | 10 ++--
> drivers/iommu/intel/pasid.c | 6 ++-
> drivers/iommu/iommu.c | 22 ++++++++
> drivers/iommu/ipmmu-vmsa.c | 2 -
> drivers/iommu/msm_iommu.c | 59 +++++++++++----------
> drivers/iommu/mtk_iommu.c | 4 +-
> drivers/iommu/omap-iommu.c | 6 +--
> drivers/iommu/sprd-iommu.c | 4 +-
> drivers/iommu/tegra-gart.c | 2 +-
> drivers/iommu/virtio-iommu.c | 7 ++-
For virtio-iommu:
Reviewed-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> include/linux/iommu.h | 12 +++++
> 17 files changed, 90 insertions(+), 83 deletions(-)
>
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-21 8:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 8:22 [PATCH v4 0/6] Define EINVAL as device/domain incompatibility Nicolin Chen
2022-09-21 8:23 ` [PATCH v4 3/6] iommu: Add return value rules to attach_dev op and APIs Nicolin Chen
2022-09-22 2:02 ` Baolu Lu
2022-09-22 5:09 ` Nicolin Chen
2022-09-22 8:17 ` Tian, Kevin
2022-09-22 8:38 ` Nicolin Chen
2022-09-21 8:23 ` [PATCH v4 4/6] iommu: Regulate EINVAL in ->attach_dev callback functions Nicolin Chen
2022-09-22 2:14 ` Baolu Lu
2022-09-22 8:18 ` Tian, Kevin
2022-09-21 8:23 ` [PATCH v4 5/6] iommu: Use EINVAL for incompatible device/domain in ->attach_dev Nicolin Chen
2022-09-22 2:16 ` Baolu Lu
2022-09-22 8:19 ` Tian, Kevin
2022-09-21 8:23 ` [PATCH v4 6/6] iommu: Propagate return value in ->attach_dev callback functions Nicolin Chen
2022-09-21 8:55 ` Jean-Philippe Brucker [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=YyrRZXVWWxBhW3ST@myrica \
--to=jean-philippe@linaro.org \
--cc=agross@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baolu.lu@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jon@solid-run.com \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nicolinc@nvidia.com \
--cc=orsonzhai@gmail.com \
--cc=quic_saipraka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=sricharan@codeaurora.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=thunder.leizhen@huawei.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will@kernel.org \
--cc=yangyingliang@huawei.com \
--cc=yong.wu@mediatek.com \
--cc=zhang.lyra@gmail.com \
/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).