Linux Documentation
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Wei Huang <wei.huang2@amd.com>, <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <skhan@linuxfoundation.org>,
	<corbet@lwn.net>, <rdunlap@infradead.org>
Subject: Re: [PATCH RFC 2/3] PCI: Add per-device debugfs directories
Date: Thu, 19 Nov 2026 08:31:30 +0800	[thread overview]
Message-ID: <28055dc3-13bf-49e1-bdbb-e825df9a0c49@huawei.com> (raw)
In-Reply-To: <20261001155551.4182899-3-wei.huang2@amd.com>

Acked-by: Chengwen Feng <fengchengwen@huawei.com>

On 10/1/2026 11:55 PM, Wei Huang wrote:
> PCI features that export debug information have no common place to put it.
> The only existing user, PTM, creates a "pcie_ptm_<device>" directory in the
> debugfs root, which does not scale as more features follow and leaves each
> user to invent its own lifetime rules and leaf names.
> 
> Add /sys/kernel/debug/pci/<device>/ directories owned by the PCI core.
> pci_dev_debugfs_dir() returns the directory of a device, creating it and
> the PCI root directory on first use, so devices without debug content do
> not get an empty directory. pci_destroy_dev() removes the directory
> recursively, so a feature that pins data in a debugfs file needs no removal
> hook of its own: debugfs_remove_recursive() returns only once no operation
> on those files is still running.
> 
> No functional change for existing users; the next patch is the first
> consumer.
> 
> Signed-off-by: Wei Huang <wei.huang2@amd.com>

  reply	other threads:[~2026-11-19  0:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 15:55 [PATCH RFC 0/3] PCI/TPH: Expose CPU-to-Steering Tag mappings via debugfs Wei Huang
2026-10-01 15:55 ` [PATCH RFC 1/3] PCI/TPH: Factor out the ST _DSM evaluation Wei Huang
2026-11-19  0:18   ` fengchengwen
2026-10-01 15:55 ` [PATCH RFC 2/3] PCI: Add per-device debugfs directories Wei Huang
2026-11-19  0:31   ` fengchengwen [this message]
2026-10-01 15:55 ` [PATCH RFC 3/3] Expose the CPU/Steering Tag mapping via debugfs Wei Huang
2026-11-19  0:59   ` fengchengwen
2026-11-04 21:32 ` [PATCH RFC 0/3] PCI/TPH: Expose CPU-to-Steering Tag mappings " Wei Huang

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=28055dc3-13bf-49e1-bdbb-e825df9a0c49@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=wei.huang2@amd.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