From: Marc Zyngier <marc.zyngier@arm.com>
To: "Yang, Shunyong" <shunyong.yang@hxt-semitech.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zheng, Joey" <yu.zheng@hxt-semitech.com>
Subject: Re: [PATCH] irqdomain: provide useful debugging information for irq domain
Date: Thu, 18 Jan 2018 08:54:07 +0000 [thread overview]
Message-ID: <f12b7b93-cf0e-d246-224a-2eb791a9d718@arm.com> (raw)
In-Reply-To: <1516240404.15644.23.camel@hxt-semitech.com>
On 18/01/18 01:53, Yang, Shunyong wrote:
> Hi, Marc
>
> On Wed, 2018-01-17 at 10:43 +0000, Marc Zyngier wrote:
>> On 17/01/18 10:20, Yang, Shunyong wrote:
>>>
>>> Hi, Thomas and Marc,
>>>
>>> On Wed, 2018-01-17 at 11:01 +0100, Thomas Gleixner wrote:
>>>>
>>>> On Wed, 17 Jan 2018, Yang, Shunyong wrote:
>>>>>
>>>>>
>>>>> On Wed, 2018-01-17 at 10:33 +0100, Thomas Gleixner wrote:
>>>>>>
>>>>>>
>>>>>> And how is that different from:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The nodes under debugfs irq/irqs describes information of
>>>>>>> every
>>>>>>> single
>>>>>>> irq.
>>>>>> Not at all. It contains the complete hierarchical information
>>>>>> of
>>>>>> each
>>>>>> virq.
>>>>>>
>>>>> I think irq_domain_mapping can provide some high-level
>>>>> information
>>>>> in a
>>>>> summary style.
>>>>> For example, we can check all the IRQs connect to a specific
>>>>> irq
>>>>> chip
>>>>> or irq domain.
>>>> You can retrieve the same information from the irq/irqs files.
>>>> All it
>>>> takes
>>>> is a shell script.
>>>>
>>>> Aside of that with hierarchical irq domains the old debug output
>>>> is
>>>> just
>>>> useless.
>>>>
>>> Umm...Agree. Need I post a patch to remove it?
>> I'm on it.
>>
> In addition to the "%p" to "%px" change in IRQ_DOMAIN_DEBUG you have
> posted patch to remove it, my original patch includes several other
> changes:
> 1. change to "%px" in kasprintf() parameters in
> function __irq_domain_alloc_fwnode() to build name which reflects the
> real pointer address from caller, this may be useful when reading debug
> information.
>
> n = kasprintf(GFP_KERNEL, "irqchip@%px", data);
Have you investigated whether %pK would work in a debug context?
>
> 2. other 3 changes from "%p" to "%px" in existing pr_debug().
>
> Could I submit a V2 patch which depends on your "irqdomain: Kill
> CONFIG_IRQ_DOMAIN_DEBUG" patch to handle this?
> Following is the link of your patch,
> https://patchwork.kernel.org/patch/10169367/
Sure. If you think something is missing, feel free to send an additional
patch.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-01-18 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 4:37 Yang Shunyong
2018-01-17 8:37 ` Marc Zyngier
2018-01-17 9:18 ` Thomas Gleixner
2018-01-17 9:26 ` Marc Zyngier
2018-01-17 9:26 ` Yang, Shunyong
2018-01-17 9:33 ` Thomas Gleixner
[not found] ` <1516182426.3280.19.camel@hxt-semitech.com>
2018-01-17 9:56 ` [此邮件可能存在风险] " Marc Zyngier
[not found] ` <alpine.DEB.2.20.1801171056330.1777@nanos>
2018-01-17 10:20 ` Yang, Shunyong
2018-01-17 10:41 ` Thomas Gleixner
2018-01-17 10:43 ` Marc Zyngier
2018-01-18 1:53 ` Yang, Shunyong
2018-01-18 8:54 ` Marc Zyngier [this message]
2018-01-18 12:06 ` Yang, Shunyong
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=f12b7b93-cf0e-d246-224a-2eb791a9d718@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shunyong.yang@hxt-semitech.com \
--cc=tglx@linutronix.de \
--cc=yu.zheng@hxt-semitech.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
all inboxes | Powered by JetHome®