public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	tglx@linutronix.de, kw@linux.com, kwilczynski@kernel.org,
	bhelgaas@google.com, cassel@kernel.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq/msi: Add the address and data that show MSI/MSIX
Date: Fri, 28 Feb 2025 17:00:22 +0800	[thread overview]
Message-ID: <d3bfa9c9-bf72-4ddc-bed3-1fe9ef88d518@163.com> (raw)
In-Reply-To: <Z8Co4ZnqObpnEbg7@lizhi-Precision-Tower-5810>



On 2025/2/28 02:03, Frank Li wrote:
> On Fri, Feb 28, 2025 at 12:49:38AM +0800, Hans Zhang wrote:
>> Thanks Mani for the tip.
>>
>> If I want to implement similar functionality, where should I add it? Since
>> this sysfs node is the only one that displays the MSI/MSIX interrupt number,
>> I don't know where to implement similar debug functionality at this time. Do
>> you have any suggestions? Or it shouldn't have a similar function.
> 
> I think it is useful feature to help debug. Generally only one property
> for one sys file.
> 
> A possible create 3 files under
> 
> /sys/kernel/irq/26/
> 	address_hi, address_lo, msg_data.
> 
> cat address_hi, only show 0x00000000. ... ABI doc need update also.
> 
> Thomas(tglx) may provide better suggestions.

Thank you very much for Frank's opinion and agreeing with my idea. I 
also think this is a good debug method.

I will reply to Thomas(tglx) later, and then please review whether the 
patch I provided is OK?

Best regards
Hans


  reply	other threads:[~2025-02-28  9:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 16:28 [PATCH] genirq/msi: Add the address and data that show MSI/MSIX Hans Zhang
2025-02-27 16:39 ` Manivannan Sadhasivam
2025-02-27 16:49   ` Hans Zhang
2025-02-27 18:03     ` Frank Li
2025-02-28  9:00       ` Hans Zhang [this message]
2025-02-27 17:51   ` Thomas Gleixner
2025-02-28  9:04     ` Hans Zhang
2025-02-28 11:26       ` Thomas Gleixner
2025-02-28 15:17         ` Hans Zhang
2025-02-28 18:14           ` Thomas Gleixner
2025-03-01 12:33             ` Hans Zhang

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=d3bfa9c9-bf72-4ddc-bed3-1fe9ef88d518@163.com \
    --to=18255117159@163.com \
    --cc=Frank.li@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=kw@linux.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=tglx@linutronix.de \
    /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