All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Christian Benvenuti <benve@cisco.com>,
	Heiko Stuebner <heiko@sntech.de>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Joerg Roedel <joro@8bytes.org>, Leon Romanovsky <leon@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-rockchip@lists.infradead.org"
	<linux-rockchip@lists.infradead.org>,
	"linux-sunxi@lists.linux.dev" <linux-sunxi@lists.linux.dev>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Nelson Escobar <neescoba@cisco.com>,
	Rob Clark <robin.clark@oss.qualcomm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Samuel Holland <samuel@sholland.org>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Chen-Yu Tsai <wens@csie.org>, Will Deacon <will@kernel.org>,
	Yong Wu <yong.wu@mediatek.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: Re: [PATCH v2 2/3] iommu/amd: Don't call report_iommu_fault()
Date: Tue, 18 Nov 2025 14:58:31 -0400	[thread overview]
Message-ID: <20251118185831.GQ10864@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB5276EFE7D236FF918A79263C8CC9A@BN9PR11MB5276.namprd11.prod.outlook.com>

On Mon, Nov 17, 2025 at 06:38:51AM +0000, Tian, Kevin wrote:
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > Sent: Friday, November 7, 2025 4:35 AM
> > 
> > This old style API is only used by drivers/gpu/drm/msm,
> > drivers/remoteproc/omap_remoteproc.c, and
> > drivers/remoteproc/qcom_q6v5_adsp.c none are used on x86 HW.
> > 
> > Remove the dead code to discourage new users.
> > 
> > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> > ---
> >  drivers/iommu/amd/iommu.c | 7 -------
> >  1 file changed, 7 deletions(-)
> > 
> > diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> > index 2e1865daa1cee8..d4d9a5dbfa6333 100644
> > --- a/drivers/iommu/amd/iommu.c
> > +++ b/drivers/iommu/amd/iommu.c
> > @@ -854,13 +854,6 @@ static void amd_iommu_report_page_fault(struct
> > amd_iommu *iommu,
> >  						   PCI_FUNC(devid),
> > domain_id);
> >  				goto out;
> >  			}
> > -
> > -			if (!report_iommu_fault(&dev_data->domain-
> > >domain,
> > -						&pdev->dev, address,
> > -						IS_WRITE_REQUEST(flags) ?
> > -
> > 	IOMMU_FAULT_WRITE :
> > -
> > 	IOMMU_FAULT_READ))
> > -				goto out;
> >  		}
> > 
> >  		if (__ratelimit(&dev_data->rs)) {
> 
> Remove amd_iommu_report_page_fault() too?

I don't understand this remark?

amd_iommu_report_page_fault() generates the dmesg logging on iommu
faults?

Jason


WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Christian Benvenuti <benve@cisco.com>,
	Heiko Stuebner <heiko@sntech.de>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Joerg Roedel <joro@8bytes.org>, Leon Romanovsky <leon@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-rockchip@lists.infradead.org"
	<linux-rockchip@lists.infradead.org>,
	"linux-sunxi@lists.linux.dev" <linux-sunxi@lists.linux.dev>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Nelson Escobar <neescoba@cisco.com>,
	Rob Clark <robin.clark@oss.qualcomm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Samuel Holland <samuel@sholland.org>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Chen-Yu Tsai <wens@csie.org>, Will Deacon <will@kernel.org>,
	Yong Wu <yong.wu@mediatek.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: Re: [PATCH v2 2/3] iommu/amd: Don't call report_iommu_fault()
Date: Tue, 18 Nov 2025 14:58:31 -0400	[thread overview]
Message-ID: <20251118185831.GQ10864@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB5276EFE7D236FF918A79263C8CC9A@BN9PR11MB5276.namprd11.prod.outlook.com>

On Mon, Nov 17, 2025 at 06:38:51AM +0000, Tian, Kevin wrote:
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > Sent: Friday, November 7, 2025 4:35 AM
> > 
> > This old style API is only used by drivers/gpu/drm/msm,
> > drivers/remoteproc/omap_remoteproc.c, and
> > drivers/remoteproc/qcom_q6v5_adsp.c none are used on x86 HW.
> > 
> > Remove the dead code to discourage new users.
> > 
> > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> > ---
> >  drivers/iommu/amd/iommu.c | 7 -------
> >  1 file changed, 7 deletions(-)
> > 
> > diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> > index 2e1865daa1cee8..d4d9a5dbfa6333 100644
> > --- a/drivers/iommu/amd/iommu.c
> > +++ b/drivers/iommu/amd/iommu.c
> > @@ -854,13 +854,6 @@ static void amd_iommu_report_page_fault(struct
> > amd_iommu *iommu,
> >  						   PCI_FUNC(devid),
> > domain_id);
> >  				goto out;
> >  			}
> > -
> > -			if (!report_iommu_fault(&dev_data->domain-
> > >domain,
> > -						&pdev->dev, address,
> > -						IS_WRITE_REQUEST(flags) ?
> > -
> > 	IOMMU_FAULT_WRITE :
> > -
> > 	IOMMU_FAULT_READ))
> > -				goto out;
> >  		}
> > 
> >  		if (__ratelimit(&dev_data->rs)) {
> 
> Remove amd_iommu_report_page_fault() too?

I don't understand this remark?

amd_iommu_report_page_fault() generates the dmesg logging on iommu
faults?

Jason

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2025-11-18 18:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 20:34 [PATCH v2 0/3] Cleanup around iommu_set_fault_handler() Jason Gunthorpe
2025-11-06 20:34 ` Jason Gunthorpe
2025-11-06 20:34 ` [PATCH v2 1/3] RDMA/usnic: Remove iommu_set_fault_handler() Jason Gunthorpe
2025-11-06 20:34   ` Jason Gunthorpe
2025-11-17  6:37   ` Tian, Kevin
2025-11-17  6:37     ` Tian, Kevin
2025-11-06 20:34 ` [PATCH v2 2/3] iommu/amd: Don't call report_iommu_fault() Jason Gunthorpe
2025-11-06 20:34   ` Jason Gunthorpe
2025-11-08 11:17   ` Vasant Hegde
2025-11-08 11:17     ` Vasant Hegde
2025-11-18 18:57     ` Jason Gunthorpe
2025-11-18 18:57       ` Jason Gunthorpe
2025-11-17  6:38   ` Tian, Kevin
2025-11-17  6:38     ` Tian, Kevin
2025-11-18 18:58     ` Jason Gunthorpe [this message]
2025-11-18 18:58       ` Jason Gunthorpe
2025-11-18 23:58       ` Tian, Kevin
2025-11-18 23:58         ` Tian, Kevin
2025-11-20 19:35         ` Jason Gunthorpe
2025-11-20 19:35           ` Jason Gunthorpe
2025-11-06 20:34 ` [PATCH v2 3/3] iommu: Allow drivers to say if they use report_iommu_fault() Jason Gunthorpe
2025-11-06 20:34   ` Jason Gunthorpe
2025-11-08 11:20   ` Vasant Hegde
2025-11-08 11:20     ` Vasant Hegde
2025-11-17  6:43   ` Tian, Kevin
2025-11-17  6:43     ` Tian, Kevin
2025-11-18  1:30   ` Chaoyi Chen
2025-11-18  1:30     ` Chaoyi Chen
2025-11-18 19:00     ` Jason Gunthorpe
2025-11-18 19:00       ` Jason Gunthorpe

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=20251118185831.GQ10864@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=benve@cisco.com \
    --cc=heiko@sntech.de \
    --cc=iommu@lists.linux.dev \
    --cc=jernej.skrabec@gmail.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=leon@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=matthias.bgg@gmail.com \
    --cc=neescoba@cisco.com \
    --cc=patches@lists.linux.dev \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=robin.murphy@arm.com \
    --cc=samuel@sholland.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=wens@csie.org \
    --cc=will@kernel.org \
    --cc=yong.wu@mediatek.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 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.