mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Yang, Shunyong" <shunyong.yang@hxt-semitech.com>
Cc: "marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] irqdomain: provide useful debugging information for irq domain
Date: Wed, 17 Jan 2018 10:33:36 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1801171032490.1777@nanos> (raw)
In-Reply-To: <1516181177.3280.13.camel@hxt-semitech.com>

On Wed, 17 Jan 2018, Yang, Shunyong wrote:

> Hi, Marc and Thomas,
> 
> Thanks for your feedback.
> 
> On Wed, 2018-01-17 at 10:18 +0100, Thomas Gleixner wrote:
> > On Wed, 17 Jan 2018, Marc Zyngier wrote:
> > > 
> > > In all honesty, I'd be more inclined to remove this debug feature
> > > altogether, as CONFIG_GENERIC_IRQ_DEBUGFS is more complete and more
> > > useful. Is there any feature missing from that infrastructure that
> > > prevents you from using it instead?
> > > 
> > > If the answer is "none", then I'll post a patch removing it.
> > Wanted to do that quite some time ago and never came around to it.
> 
> I think they have different purpose.
> irq_domain_mapping is an overiew of the mapping of each virq to hwirq
> and the domain it belongs. It likes a map or index of each IRQs. I tend
> to suggest to keep it.

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.

Thanks,

	tglx

  reply	other threads:[~2018-01-17  9:33 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 [this message]
     [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
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=alpine.DEB.2.20.1801171032490.1777@nanos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=shunyong.yang@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®