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]

Message-ID: <49F60EC9.2050501@ovro.caltech.edu>
Date:	Mon, 27 Apr 2009 13:00:09 -0700
From:	David Hawkins <dwh@...o.caltech.edu>
To:	Kumar Gala <galak@...nel.crashing.org>
CC:	Ira Snyder <iws@...o.caltech.edu>,
	Liu Dave-R63238 <DaveLiu@...escale.com>,
	linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
	Dan Williams <dan.j.williams@...el.com>,
	Timur Tabi <timur@...escale.com>
Subject: Re: [PATCH] fsldma: use PCI Read Multiple command


>> 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 :)
> 
> You can mark the pci inbound window on the 83xx as non-prefetchable 
> (assuming 83xx is host). On a x86 host I doubt there is any easy way to 
> get non-prefetchable memory.

Yep, we were going to do that, but chose to use the
1MB region already setup for the IMMRs since its already
marked as non-prefetchable. We were only doing reads, so
it wasn't going to hurt anything.

I doubt that marking one of the other BAR regions
as non-prefetchable will give a different result.
However, we're more than happy to double-check if
you'd like.

Cheers,
Dave

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