[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1547622.IrIylJTC5Q@ws-stein>
Date: Wed, 23 Mar 2016 12:19:30 +0100
From: Alexander Stein <alexander.stein@...tec-electronic.com>
To: Marc Zyngier <marc.zyngier@....com>
Cc: linux-kernel@...r.kernel.org,
Minghuan Lian <Minghuan.Lian@....com>,
linux-arm-kernel@...ts.infradead.org,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Roy Zang <roy.zang@....com>, Mingkai Hu <mingkai.hu@....com>,
Stuart Yoder <stuart.yoder@....com>,
Yang-Leo Li <leoyang.li@....com>
Subject: Re: [PATCH 2/2 v5] irqchip/Layerscape: Add SCFG MSI controller support
On Wednesday 23 March 2016 11:08:04, Marc Zyngier wrote:
> > Using an intel e1000e card which uses 3 MSIs. But the IRQ numbers are a bit strange though:
> >> grep eth3 /proc/interrupts
> >>
> >> 63: 49 0 MSI 134742016 Edge eth3-rx-0
> >> 64: 3 0 MSI 134742017 Edge eth3-tx-0
> >> 65: 4 0 MSI 134742018 Edge eth3
>
> This is a virtual interrupt number (despite being displayed as a hwirq),
> computed from the PCI requester ID and the MSI index. You shouldn't
> infer anything from it.
Why show it anyway then if you can't infer anything?
Best regards,
Alexander
Powered by blists - more mailing lists