linux-kernel - Re: [PATCH] fsldma: use PCI Read Multiple command

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:	Mon, 27 Apr 2009 15:47:52 -0500
From:	Scott Wood <scottwood@...escale.com>
To:	Timur Tabi <timur@...escale.com>
Cc:	David Hawkins <dwh@...o.caltech.edu>, linuxppc-dev@...abs.org,
	Dan Williams <dan.j.williams@...el.com>,
	Liu Dave-R63238 <DaveLiu@...escale.com>,
	linux-kernel@...r.kernel.org, Ira Snyder <iws@...o.caltech.edu>
Subject: Re: [PATCH] fsldma: use PCI Read Multiple command

On Mon, Apr 27, 2009 at 03:04:49PM -0500, Timur Tabi wrote:
> David Hawkins wrote:
> 
> > Can you give me an example of non-PCI memory that would be
> > non-prefetchable that you'd like us to try? We can see if our
> > host CPUs have an area like that ... we just need to know
> > what device to look for first :)
> 
> Hmmmm.... I was going to say any SOC device in the IMMR, but I don't see
> anything there that would constitute a memory buffer.
> 
> I test this change on an 8610 and DMA to a register I/O, where this bit
> isn't even defined, and it made no difference.  So I guess this change
> is okay.

I thought the driver only used the bit if the device tree indicated it
was an 83xx-era DMA controller?

That said, the bits are documented as specifically for PCI, so it would
be surprising if it had any effect elsewhere.

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