From: Yi Liu <yi.l.liu@intel.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
Kevin Tian <kevin.tian@intel.com>,
"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
Nicolin Chen <nicolinc@nvidia.com>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>,
Yan Zhao <yan.y.zhao@intel.com>, <iommu@lists.linux.dev>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 02/12] iommu/arm-smmu-v3: Remove unrecoverable faults reporting
Date: Mon, 4 Dec 2023 18:54:47 +0800 [thread overview]
Message-ID: <4593a682-b33b-4284-b94c-7f7fd9351171@intel.com> (raw)
In-Reply-To: <20231115030226.16700-3-baolu.lu@linux.intel.com>
On 2023/11/15 11:02, Lu Baolu wrote:
> No device driver registers fault handler to handle the reported
> unrecoveraable faults. Remove it to avoid dead code.
I noticed only ARM code is removed. So intel iommu driver does not have
code that tries to report unrecoveraable faults?
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
> ---
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 46 ++++++---------------
> 1 file changed, 13 insertions(+), 33 deletions(-)
>
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> index 7445454c2af2..505400538a2e 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> @@ -1463,7 +1463,6 @@ arm_smmu_find_master(struct arm_smmu_device *smmu, u32 sid)
> static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
> {
> int ret;
> - u32 reason;
> u32 perm = 0;
> struct arm_smmu_master *master;
> bool ssid_valid = evt[0] & EVTQ_0_SSV;
> @@ -1473,16 +1472,9 @@ static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
>
> switch (FIELD_GET(EVTQ_0_ID, evt[0])) {
> case EVT_ID_TRANSLATION_FAULT:
> - reason = IOMMU_FAULT_REASON_PTE_FETCH;
> - break;
> case EVT_ID_ADDR_SIZE_FAULT:
> - reason = IOMMU_FAULT_REASON_OOR_ADDRESS;
> - break;
> case EVT_ID_ACCESS_FAULT:
> - reason = IOMMU_FAULT_REASON_ACCESS;
> - break;
> case EVT_ID_PERMISSION_FAULT:
> - reason = IOMMU_FAULT_REASON_PERMISSION;
> break;
> default:
> return -EOPNOTSUPP;
> @@ -1492,6 +1484,9 @@ static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
> if (evt[1] & EVTQ_1_S2)
> return -EFAULT;
>
> + if (!(evt[1] & EVTQ_1_STALL))
> + return -EOPNOTSUPP;
> +
> if (evt[1] & EVTQ_1_RnW)
> perm |= IOMMU_FAULT_PERM_READ;
> else
> @@ -1503,32 +1498,17 @@ static int arm_smmu_handle_evt(struct arm_smmu_device *smmu, u64 *evt)
> if (evt[1] & EVTQ_1_PnU)
> perm |= IOMMU_FAULT_PERM_PRIV;
>
> - if (evt[1] & EVTQ_1_STALL) {
> - flt->type = IOMMU_FAULT_PAGE_REQ;
> - flt->prm = (struct iommu_fault_page_request) {
> - .flags = IOMMU_FAULT_PAGE_REQUEST_LAST_PAGE,
> - .grpid = FIELD_GET(EVTQ_1_STAG, evt[1]),
> - .perm = perm,
> - .addr = FIELD_GET(EVTQ_2_ADDR, evt[2]),
> - };
> + flt->type = IOMMU_FAULT_PAGE_REQ;
> + flt->prm = (struct iommu_fault_page_request) {
> + .flags = IOMMU_FAULT_PAGE_REQUEST_LAST_PAGE,
> + .grpid = FIELD_GET(EVTQ_1_STAG, evt[1]),
> + .perm = perm,
> + .addr = FIELD_GET(EVTQ_2_ADDR, evt[2]),
> + };
>
> - if (ssid_valid) {
> - flt->prm.flags |= IOMMU_FAULT_PAGE_REQUEST_PASID_VALID;
> - flt->prm.pasid = FIELD_GET(EVTQ_0_SSID, evt[0]);
> - }
> - } else {
> - flt->type = IOMMU_FAULT_DMA_UNRECOV;
> - flt->event = (struct iommu_fault_unrecoverable) {
> - .reason = reason,
> - .flags = IOMMU_FAULT_UNRECOV_ADDR_VALID,
> - .perm = perm,
> - .addr = FIELD_GET(EVTQ_2_ADDR, evt[2]),
> - };
> -
> - if (ssid_valid) {
> - flt->event.flags |= IOMMU_FAULT_UNRECOV_PASID_VALID;
> - flt->event.pasid = FIELD_GET(EVTQ_0_SSID, evt[0]);
> - }
> + if (ssid_valid) {
> + flt->prm.flags |= IOMMU_FAULT_PAGE_REQUEST_PASID_VALID;
> + flt->prm.pasid = FIELD_GET(EVTQ_0_SSID, evt[0]);
> }
>
> mutex_lock(&smmu->streams_mutex);
--
Regards,
Yi Liu
next prev parent reply other threads:[~2023-12-04 10:52 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 3:02 [PATCH v7 00/12] iommu: Prepare to deliver page faults to user space Lu Baolu
2023-11-15 3:02 ` [PATCH v7 01/12] iommu: Move iommu fault data to linux/iommu.h Lu Baolu
2023-12-04 10:52 ` Yi Liu
2023-11-15 3:02 ` [PATCH v7 02/12] iommu/arm-smmu-v3: Remove unrecoverable faults reporting Lu Baolu
2023-12-01 15:42 ` Jason Gunthorpe
2023-12-04 10:54 ` Yi Liu [this message]
2023-12-05 11:48 ` Baolu Lu
2023-11-15 3:02 ` [PATCH v7 03/12] iommu: Remove unrecoverable fault data Lu Baolu
2023-12-04 10:58 ` Yi Liu
2023-12-05 11:55 ` Baolu Lu
2023-11-15 3:02 ` [PATCH v7 04/12] iommu: Cleanup iopf data structure definitions Lu Baolu
2023-12-04 11:03 ` Yi Liu
2023-11-15 3:02 ` [PATCH v7 05/12] iommu: Merge iopf_device_param into iommu_fault_param Lu Baolu
2023-12-04 12:32 ` Yi Liu
2023-12-05 12:01 ` Baolu Lu
2023-11-15 3:02 ` [PATCH v7 06/12] iommu: Remove iommu_[un]register_device_fault_handler() Lu Baolu
2023-12-04 12:36 ` Yi Liu
2023-12-05 12:09 ` Baolu Lu
2023-11-15 3:02 ` [PATCH v7 07/12] iommu: Merge iommu_fault_event and iopf_fault Lu Baolu
2023-12-01 19:09 ` Jason Gunthorpe
2023-12-04 12:40 ` Yi Liu
2023-11-15 3:02 ` [PATCH v7 08/12] iommu: Prepare for separating SVA and IOPF Lu Baolu
2023-12-05 7:10 ` Yi Liu
2023-11-15 3:02 ` [PATCH v7 09/12] iommu: Make iommu_queue_iopf() more generic Lu Baolu
2023-12-01 19:14 ` Jason Gunthorpe
2023-12-05 7:13 ` Yi Liu
2023-12-05 12:13 ` Baolu Lu
2023-11-15 3:02 ` [PATCH v7 10/12] iommu: Separate SVA and IOPF Lu Baolu
2023-11-15 3:02 ` [PATCH v7 11/12] iommu: Consolidate per-device fault data management Lu Baolu
2023-12-01 19:46 ` Jason Gunthorpe
2023-12-04 0:58 ` Baolu Lu
2023-11-15 3:02 ` [PATCH v7 12/12] iommu: Improve iopf_queue_flush_dev() Lu Baolu
2023-12-01 20:35 ` Jason Gunthorpe
2023-12-03 8:53 ` Baolu Lu
2023-12-03 14:14 ` Jason Gunthorpe
2023-12-04 1:32 ` Baolu Lu
2023-12-04 5:37 ` Tian, Kevin
2023-12-04 13:25 ` Jason Gunthorpe
2023-12-05 1:32 ` Tian, Kevin
2023-12-05 1:53 ` Jason Gunthorpe
2023-12-05 3:23 ` Tian, Kevin
2023-12-05 15:52 ` Jason Gunthorpe
2023-12-04 13:12 ` Jason Gunthorpe
2023-12-04 3:46 ` Baolu Lu
2023-12-04 13:27 ` Jason Gunthorpe
2023-12-05 1:13 ` Baolu Lu
2023-11-24 6:30 ` [PATCH v7 00/12] iommu: Prepare to deliver page faults to user space liulongfang
2023-11-24 12:01 ` Baolu Lu
2023-11-25 4:05 ` liulongfang
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=4593a682-b33b-4284-b94c-7f7fd9351171@intel.com \
--to=yi.l.liu@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.org \
--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 \
--cc=yan.y.zhao@intel.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
all inboxes | Powered by JetHome®