linux-kernel - Re: [PATCH] libata-sff: Don't call bmdma

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]

Date:	Thu, 25 Jan 2007 22:18:21 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Woodhouse <dwmw2@...radead.org>
cc:	Alan <alan@...rguk.ukuu.org.uk>, Jeff Garzik <jgarzik@...ox.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable
 controllers

On Thu, 25 Jan 2007, Linus Torvalds wrote:
> 
> Have you noticed that the resource-allocation code _already_ never returns 
> zero on sparc64?

Btw, that was a rhetorical question, and I'm not actually sure what the 
heck sparc64 will _really_ do ;)

I picked sparc64 as an example, because I _think_ that sparc64 actually is 
an example of an architecture that sets up a separate root resource for 
each PCI domain, and they are actually set up so that the ioport regions 
are literally offset to match the hardware bases (and there are several 
different kinds of PCI domain controllers that sparc supports, so those 
bases will depend on that too).

So on sparc64, "ioport_resource" really is just a container for the actual 
per-domain resource buckets that the hardware (within that domain) will 
then do the resource allocation from. Afaik.

But you should actaully verify that with somebody like Davem if you 
_really_ care.  I cc'd him in case he wants to pipe up and perhaps prove 
me wrong.

			Linus
-
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/