lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 17 Jan 2018 10:20:35 +0000
From:   "Yang, Shunyong" <shunyong.yang@...-semitech.com>
To:     "tglx@...utronix.de" <tglx@...utronix.de>,
        "marc.zyngier@....com" <marc.zyngier@....com>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Zheng, Joey" <yu.zheng@...-semitech.com>
Subject: Re: Re: Re: [PATCH] irqdomain: provide useful debugging information
 for irq domain

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?

Thanks
Shunyong

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ