From: Joerg Roedel <joro@8bytes.org>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: quic_saipraka@quicinc.com,
virtualization@lists.linux-foundation.org,
linux-tegra@vger.kernel.org, thierry.reding@gmail.com,
will@kernel.org, jean-philippe@linaro.org, zhang.lyra@gmail.com,
jon@solid-run.com, jonathanh@nvidia.com, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, jgg@nvidia.com,
yangyingliang@huawei.com, orsonzhai@gmail.com,
dwmw2@infradead.org, linux-arm-msm@vger.kernel.org,
vdumpa@nvidia.com, christophe.jaillet@wanadoo.fr,
baolin.wang@linux.alibaba.com, thunder.leizhen@huawei.com,
matthias.bgg@gmail.com, tglx@linutronix.de, yong.wu@mediatek.com,
robin.murphy@arm.com, linux-kernel@vger.kernel.org,
shameerali.kolothum.thodi@huawei.com, robdclark@gmail.com,
suravee.suthikulpanit@amd.com,
linux-mediatek@lists.infradead.org, quic_jjohnson@quicinc.com,
baolu.lu@linux.intel.com
Subject: Re: [PATCH v6 0/5] Define EINVAL as device/domain incompatibility
Date: Mon, 26 Sep 2022 14:23:05 +0200 [thread overview]
Message-ID: <YzGZqXCuw6yoXBla@8bytes.org> (raw)
In-Reply-To: <cover.1663899032.git.nicolinc@nvidia.com>
Hi Nicolin,
On Fri, Sep 23, 2022 at 12:16:29AM -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/
\o/
> Nicolin Chen (5):
> iommu/amd: Drop unnecessary checks in amd_iommu_attach_device()
> iommu: Add return value rules to attach_dev op and APIs
> iommu: Regulate EINVAL in ->attach_dev callback functions
> iommu: Use EINVAL for incompatible device/domain in ->attach_dev
> iommu: Propagate return value in ->attach_dev callback functions
This looks good to me, but I'd like to have the SMMU people have a look
at patch 4. And I think it is too late for this to make it into 6.1, so
please re-send after 6.1-rc1 is out.
Thanks,
Joerg
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
parent reply other threads:[~2022-09-26 12:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <cover.1663899032.git.nicolinc@nvidia.com>]
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=YzGZqXCuw6yoXBla@8bytes.org \
--to=joro@8bytes.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baolu.lu@linux.intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=jon@solid-run.com \
--cc=jonathanh@nvidia.com \
--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_jjohnson@quicinc.com \
--cc=quic_saipraka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=thunder.leizhen@huawei.com \
--cc=vdumpa@nvidia.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).