linux-kernel - Re: libata, devm

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <497698E2.7090807@rtr.ca>
Date:	Tue, 20 Jan 2009 22:39:14 -0500
From:	Mark Lord <liml@....ca>
To:	Daniel Barkalow <barkalow@...ervon.org>
Cc:	IDE/ATA development list <linux-ide@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Tejun Heo <htejun@...il.com>, Jeff Garzik <jgarzik@...ox.com>,
	linux-pci@...r.kernel.org
Subject: Re: libata, devm_*, and MSI ?

Daniel Barkalow wrote:
..
> Initially, the core didn't do anything, and some drivers implemented the 
> need-intx-off quirk; eventually this went into the core as the default 
> behavior. Then some drivers implemented the need-intx-on quirk. Then some 
> common drivers for different hardware turned out to need it both ways, and 
> the core got a real quirk for it. But not all of the drivers have dropped 
> the local setting stuff.
> 
> The right way to go is to do nothing in the driver and use quirks if you 
> need it.
..

Perfect, thanks.

Next.. who knows something about debugging MSI across PCI bridges ?
I've got a 64-bit box here, PCIe near the core, but with full PCI-X
slots on the far side of two bridges.

The kernel happily allows my driver to setup MSI, but the interrupts
never arrive.  So something somewhere in between is either

(1) not set up or quirked quite right, or
(2) one of the bridges won't pass MSI and we don't detect that.

I'll poke more at it later and post some info, if somebody out there
knows enough about this kind of thing to provide some basic hints.

Cheers!
--
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/