linux-kernel - Re: [PATCH] sysfs: add per pci device msi[x] irq listing (v3)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Sep 2011 09:21:32 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH] sysfs: add per pci device msi[x] irq listing (v3)

On Thu, Sep 22, 2011 at 07:10:46AM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Sep 22, 2011 at 06:57:06AM -0400, Neil Horman wrote:
> > On Thu, Sep 22, 2011 at 06:49:02AM -0400, Konrad Rzeszutek Wilk wrote:
> > > On Mon, Sep 19, 2011 at 11:47:15AM -0400, Neil Horman wrote:
> > > > So a while back, I wanted to provide a way for irqbalance (and other apps) to
> > > > definitively map irqs to devices, which, for msi[x] irqs is currently not really
> > > > possible in user space.  My first attempt wen't not so well:
> > > > https://lkml.org/lkml/2011/4/21/308
> > > > 
> > > > It was plauged by the same issues that prior attempts were, namely that it
> > > > violated the one-file-one-value sysfs rule.  I wandered off but have recently
> > > > come back to this.  I've got a new implementation here that exports a new
> > > > subdirectory for every pci device,  called msi_irqs.  This subdirectory contanis
> > > > a variable number of numbered subdirectories, in which the number represents an
> > > > msi irq.  Each numbered subdirectory contains attributes for that irq, which
> > > > currently is only the mode it is operating in (msi vs. msix).  I think fits
> > > > within the constraints sysfs requires, and will allow irqbalance to properly map
> > > > msi irqs to devices without having to rely on rickety, best guess methods like
> > > > interface name matching.
> > > 
> > > Are there irqbalance patches that correspond to this? Where would they be available?
> > > 
> > I've got them here locally, shemminger and I are testing them out, when I'm comfortable with
> > them, I'll be comitting them to the public repository at code.google.com
> 
> Right.. asking b/c it might be a good idea to include that in the git
> description of the patch.
> 
meh, its generally useful, just so happens I'm updating irqbalance to use it.
irqd, and all the other vendor specific irqbalance solutions can also make use
of it.  I was going to mention the relationship in the irqbalance changelog
Neil


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/