Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 18/18] PCI/P2PDMA: Log detailed ACS routing diagnostics
Date: Sat, 22 Aug 2026 16:28:10 +0300	[thread overview]
Message-ID: <20260822132810.GF66924@unreal> (raw)
In-Reply-To: <20260821200246.423701F000E9@smtp.kernel.org>

On Fri, Aug 21, 2026 at 08:02:45PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] Unconditional debug logging in the high-frequency P2PDMA mapping fast path causes severe log flooding.
> --
> 
> --- Patch [18]: [PATCH v4 18/18] PCI/P2PDMA: Log detailed ACS routing diagnostics ---
> commit 6ad59be5d5d93d88cf70cbce85e9046d3c5b0adb
> Author: Leon Romanovsky <leon@kernel.org>
> 
>     PCI/P2PDMA: Log detailed ACS routing diagnostics
> 
> This commit adds detailed ACS routing diagnostics to assist in identifying
> P2PDMA mapping failures. It emits info-level logs covering path details,
> ACS controls, and cache state.
> 
> > diff --git a/drivers/pci/p2pdma.c b/drivers/pci/p2pdma.c
> > index e54901d21d8a2..b79eb4ce09f47 100644
> > --- a/drivers/pci/p2pdma.c
> > +++ b/drivers/pci/p2pdma.c
> 
> [ ... ]
> 
> > @@ -1237,23 +1467,38 @@ enum pci_p2pdma_map_type pci_p2pdma_map_type(struct p2pdma_provider *provider,
> >  	struct pci_dev *pdev = to_pci_dev(provider->owner);
> >  	struct pci_dev *client;
> >  	struct pci_p2pdma *p2pdma;
> > +	unsigned long cache_index;
> > +	bool provider_state;
> >  	int dist;
> >  
> > -	if (!pdev->p2pdma)
> > +	if (!pdev->p2pdma) {
> > +		pci_info(pdev,
> > +			 "P2PDMA ACS debug: map lookup rejected; provider state is absent\n");
> >  		return PCI_P2PDMA_MAP_NOT_SUPPORTED;
> > +	}
> >  
> > -	if (!dev_is_pci(dev))
> > +	if (!dev_is_pci(dev)) {
> > +		dev_info(dev,
> > +			 "P2PDMA ACS debug: provider=%s map lookup rejected; client is not PCI\n",
> > +			 pci_name(pdev));
> >  		return PCI_P2PDMA_MAP_NOT_SUPPORTED;
> > +	}
> >  
> >  	client = to_pci_dev(dev);
> > +	cache_index = map_types_idx(client);
> >  
> >  	rcu_read_lock();
> >  	p2pdma = rcu_dereference(pdev->p2pdma);
> >  
> >  	if (p2pdma)
> >  		type = xa_to_value(xa_load(&p2pdma->map_types,
> > -					   map_types_idx(client)));
> > +					   cache_index));
> > +	provider_state = !!p2pdma;
> >  	rcu_read_unlock();
> > +	pci_info(client,
> > +		 "P2PDMA ACS debug: map lookup provider=%s index=%#lx cached=%s(%d) provider-state=%u\n",
> > +		 pci_name(pdev), cache_index, pci_p2pdma_map_type_name(type),
> > +		 type, provider_state);
> 
> [Severity: High]
> Does this code risk flooding the kernel log buffer and causing severe performance
> degradation?
> 
> Since pci_p2pdma_map_type() is invoked on the DMA mapping fast path (for
> example, once per P2PDMA I/O request via pci_p2pdma_state() in dma_map_sg()
> loops), this unconditional logging will execute on every single P2PDMA
> map lookup even when a cached route is successfully used.
> 
> Will this saturate the kernel log buffer and cause severe printk/console lock
> contention for any P2PDMA-capable block I/O or RDMA operation?

No, these are debug prints and are not enabled by default. ACS
successes and failures are deterministic, and a single operation is
sufficient to determine the cause of a failure.

Thanks

> 
> >  
> >  	if (type == PCI_P2PDMA_MAP_UNKNOWN)
> >  		return calc_map_type_and_dist(pdev, client, &dist, true);
> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20260821-fix-p2p-acs-v4-0-v4-0-94426b96de73@nvidia.com?part=18
> 

  reply	other threads:[~2026-08-22 13:28 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 19:38 [PATCH v4 00/18] PCI/P2PDMA: Fix ACS egress control handling Leon Romanovsky
2026-08-21 19:38 ` [PATCH v4 01/18] PCI/P2PDMA: Do not tear down the allocate attribute on registration failure Leon Romanovsky
2026-08-21 19:53   ` sashiko-bot
2026-08-21 23:08   ` Logan Gunthorpe
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-21 19:38 ` [PATCH v4 02/18] PCI/P2PDMA: Wait for RCU readers before freeing state Leon Romanovsky
2026-08-21 19:48   ` sashiko-bot
2026-08-21 23:10   ` Logan Gunthorpe
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-21 19:38 ` [PATCH v4 03/18] PCI/P2PDMA: Restrict the p2pmem search to pool backed providers Leon Romanovsky
2026-08-21 19:59   ` sashiko-bot
2026-08-21 23:14   ` Logan Gunthorpe
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-21 19:38 ` [PATCH v4 04/18] PCI/P2PDMA: Safely terminate ACS redirect lists Leon Romanovsky
2026-08-21 19:47   ` sashiko-bot
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-21 19:38 ` [PATCH v4 05/18] PCI/P2PDMA: Document the pdev->p2pdma lifetime and RCU rules Leon Romanovsky
2026-08-21 19:56   ` sashiko-bot
2026-08-24 20:29   ` I Logan Gunthorpe
2026-08-30  9:14     ` I Leon Romanovsky
2026-08-21 19:38 ` [PATCH v4 06/18] PCI/P2PDMA: Gate the host bridge whitelist warning on verbose Leon Romanovsky
2026-08-21 19:47   ` sashiko-bot
2026-08-24 21:08   ` Logan Gunthorpe
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-21 19:38 ` [PATCH v4 07/18] PCI/P2PDMA: Document the Address Type assumption Leon Romanovsky
2026-08-21 19:43   ` sashiko-bot
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-21 19:38 ` [PATCH v4 08/18] PCI: Account for Direct Translated P2P in ACS isolation checks Leon Romanovsky
2026-08-21 19:54   ` sashiko-bot
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-25 15:59   ` Logan Gunthorpe
2026-08-21 19:38 ` [PATCH v4 09/18] PCI: Add ACS egress control vector accessor Leon Romanovsky
2026-08-21 19:50   ` sashiko-bot
2026-08-21 19:38 ` [PATCH v4 10/18] PCI: Account for ACS egress control in isolation checks Leon Romanovsky
2026-08-21 19:51   ` sashiko-bot
2026-08-24 23:22   ` Jason Gunthorpe
2026-08-30  9:20     ` Leon Romanovsky
2026-08-31 12:02       ` Jason Gunthorpe
2026-08-21 19:38 ` [PATCH v4 11/18] PCI/P2PDMA: Derive peer-to-peer routing from ACS control bits Leon Romanovsky
2026-08-21 19:54   ` sashiko-bot
2026-08-22 13:31     ` Leon Romanovsky
2026-08-25 19:17   ` Logan Gunthorpe
2026-08-21 19:38 ` [PATCH v4 12/18] PCI/P2PDMA: Honor ACS egress control vectors Leon Romanovsky
2026-08-21 19:56   ` sashiko-bot
2026-08-25 19:25   ` Logan Gunthorpe
2026-08-21 19:38 ` [PATCH v4 13/18] PCI/P2PDMA: Document ACS egress control handling Leon Romanovsky
2026-08-21 19:44   ` sashiko-bot
2026-08-25 19:52   ` Logan Gunthorpe
2026-08-21 19:38 ` [PATCH v4 14/18] PCI/P2PDMA: Extract pure ACS routing decision helpers Leon Romanovsky
2026-08-21 19:49   ` sashiko-bot
2026-08-25 19:55   ` Logan Gunthorpe
2026-08-21 19:38 ` [PATCH v4 15/18] PCI/P2PDMA: Add KUnit tests for ACS routing decisions Leon Romanovsky
2026-08-21 19:50   ` sashiko-bot
2026-08-21 19:38 ` [PATCH v4 16/18] PCI/P2PDMA: Add KUnit coverage for the ACS P2P routing walk Leon Romanovsky
2026-08-21 19:51   ` sashiko-bot
2026-08-21 19:38 ` [PATCH v4 17/18] PCI: Add KUnit coverage for ACS isolation checks Leon Romanovsky
2026-08-21 19:52   ` sashiko-bot
2026-08-21 19:38 ` [PATCH v4 18/18] PCI/P2PDMA: Log detailed ACS routing diagnostics Leon Romanovsky
2026-08-21 20:02   ` sashiko-bot
2026-08-22 13:28     ` Leon Romanovsky [this message]
2026-08-25 20:02   ` Logan Gunthorpe
2026-08-30  8:37     ` Leon Romanovsky
2026-08-24 23:22 ` [PATCH v4 00/18] PCI/P2PDMA: Fix ACS egress control handling Jason Gunthorpe
2026-08-30  9:02   ` Leon Romanovsky
2026-08-31 12: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=20260822132810.GF66924@unreal \
    --to=leon@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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