linux-kernel - Re: [RFC] AGP initial support for chipset flushing..

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: <Pine.LNX.4.64.0710291951100.1170@skynet.skynet.ie>
Date:	Mon, 29 Oct 2007 19:52:43 +0000 (GMT)
From:	Dave Airlie <airlied@...ux.ie>
To:	Jesse Barnes <jesse.barnes@...el.com>
cc:	dri-devel@...ts.sourceforge.net, keithp@...thp.com,
	linux-kernel@...r.kernel.org, dri-devel@...ts.sf.net
Subject: Re: [RFC] AGP initial support for chipset flushing..


> 
> In this case, we're performing basically a dma_sync*(...DMA_TO_DEVICE) 
> right?  Can we be sure that a single flush is sufficient?  Is there any 
> window between when we flush and when we start accessing memory with 
> the device that we could get into more caching trouble?

Not that I can think off, but I don't work for the company who screwed up 
the coherency :-), and I don't have the docs, so please investigate for me 
;-)

> Looks reasonable, I'm not sure we can do much better.  The only concern 
> I have is that allocating some more PCI space like that may end up 
> clobbering some *other* hidden BIOS mapping, but there's not a whole 
> lot we can do about that.

Again I'm trying to workaround broken BIOS.. nothing I can do.

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/