Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752497AbeAQKUk convert rfc822-to-8bit (ORCPT + 1 other); Wed, 17 Jan 2018 05:20:40 -0500 Received: from mx01.hxt-semitech.com.96.203.223.in-addr.arpa ([223.203.96.7]:34243 "EHLO barracuda.hxt-semitech.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1750816AbeAQKUh (ORCPT ); Wed, 17 Jan 2018 05:20:37 -0500 X-ASG-Debug-ID: 1516184429-093b7e0d7737f80001-xx1T2L X-Barracuda-Envelope-From: shunyong.yang@hxt-semitech.com From: "Yang, Shunyong" To: "tglx@linutronix.de" , "marc.zyngier@arm.com" CC: "linux-kernel@vger.kernel.org" , "Zheng, Joey" Subject: Re: Re: Re: [PATCH] irqdomain: provide useful debugging information for irq domain Thread-Topic: Re: Re: [PATCH] irqdomain: provide useful debugging information for irq domain X-ASG-Orig-Subj: Re: Re: Re: [PATCH] irqdomain: provide useful debugging information for irq domain Thread-Index: AQHTj3zQcHfoHCwoCUip2S/uhG+tNg== Date: Wed, 17 Jan 2018 10:20:35 +0000 Message-ID: <1516184428.3280.25.camel@hxt-semitech.com> References: <1516163877-32396-1-git-send-email-shunyong.yang@hxt-semitech.com> <210f90d0-1588-2185-4845-d5d143183621@arm.com> <1516181177.3280.13.camel@hxt-semitech.com> <1516182426.3280.19.camel@hxt-semitech.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.64.6.73] Content-Type: text/plain; charset=US-ASCII Content-ID: <9475E27A2FD11141B14A218618BDAD14@hxt-semitech.com> Content-Transfer-Encoding: 7BIT MIME-Version: 1.0 X-Barracuda-Connect: localhost[10.128.0.14] X-Barracuda-Start-Time: 1516184429 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://192.168.50.101:443/cgi-mod/mark.cgi X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.4948 1.0000 0.0000 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.46964 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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