public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Hans Zhang <18255117159@163.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: 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 12:26:39 +0100	[thread overview]
Message-ID: <874j0ee2ds.ffs@tglx> (raw)
In-Reply-To: <251ce5c0-8c10-4b29-9ffb-592e908187fd@163.com>

On Fri, Feb 28 2025 at 17:04, Hans Zhang wrote:
> Is the following patch OK?

No.

>   static void
>   irq_debug_show_chip(struct seq_file *m, struct irq_data *data, int ind)
>   {
> @@ -178,6 +199,7 @@ static int irq_debug_show(struct seq_file *m, void *p)
>          seq_printf(m, "node:     %d\n", irq_data_get_node(data));
>          irq_debug_show_masks(m, desc);
>          irq_debug_show_data(m, data, 0);
> +       irq_debug_show_msi_msix(m, data, 0);
>          raw_spin_unlock_irq(&desc->lock);
>          return 0;
>   }

This is just violating the layering and I told you what to do:

    "implement a debug_show() callback in the MSI core code and assign
     it to domain ops::debug_show() on domain creation, if it does not
     provide its own callback."

If you don't understand what I tell you, then please ask instead of
going off and hacking up something completely different.

Here is another hint:

     Look at msi_domain_ops_default and at msi_domain_update_dom_ops()

If you still have questions, feel free to ask.

Thanks,

        tglx



  reply	other threads:[~2025-02-28 11:26 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
2025-02-27 17:51   ` Thomas Gleixner
2025-02-28  9:04     ` Hans Zhang
2025-02-28 11:26       ` Thomas Gleixner [this message]
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=874j0ee2ds.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=18255117159@163.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 \
    /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