[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1801171032490.1777@nanos>
Date: Wed, 17 Jan 2018 10:33:36 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Yang, Shunyong" <shunyong.yang@...-semitech.com>
cc: "marc.zyngier@....com" <marc.zyngier@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] irqdomain: provide useful debugging information for irq
domain
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
Powered by blists - more mailing lists