From owner-freebsd-current Fri Feb 1 17:10:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 3108C37B477 for ; Fri, 1 Feb 2002 17:09:06 -0800 (PST) Received: from pool0542.cvx40-bradley.dialup.earthlink.net ([216.244.44.32] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Wofm-0000yf-00; Fri, 01 Feb 2002 17:08:54 -0800 Message-ID: <3C5B3C20.1A8C3A9C@mindspring.com> Date: Fri, 01 Feb 2002 17:08:48 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Erik Trulsson Cc: =?iso-8859-1?Q?G=E9rard?= Roudier , Jason Evans , Kenneth Culver , Cameron@FreeBSD.ORG, Frank , David Malone , freebsd-current@FreeBSD.ORG Subject: Re: AMD AGP Bug References: <20020131173408.B63502@canonware.com> <20020131211810.B1769-100000@gerard> <20020201215006.GA50090@student.uu.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Erik Trulsson wrote: > > The Athlon rewriting same value to cacheable memory under the knees of > > programmers looks a severe issue to me if it is true. Not only AGP memory > > can be affected. What about SMP, MMIO (if some cacheable mapping exists), > > etc...? > > I am not familiar with the acronym MMIO is so I can't comment on that. "Memory Mapped I/O". 8-). > In general though, having memoryspace used for memory-mapped I/O > devices (including AGP) marked as cacheable is a bad idea unless you > are very careful and know exactly what you are doing. "What he said". 8-) 8-). > For SMP it shouldn't be any problem. Multi-CPU systems normally > run some cache-coherence protocol between themselves to make sure that > things like this is not a problem. I think the problem is pages in which there are inter-CPU locks being set and cleared. Say you had a speculative write that would clear a lock, only you decide not to clear it because it doesn't happen. > > In my opinion, OSes having some cacheable mapping to AGP memory is not the > > real problem. Just it has revealed the AMD issue. > > It might be argued that there should be some cache-coherence protocol > between the CPU and the AGP device. This is what Bruce and Peter suggested; Peter said that he was working on a rewrite of the pmap code and would look in that area. > Not knowing how AGP is specified I don't know if this interaction > between the CPU and AGP is a bug or just working as specified. I > suspect it is the latter though. "If it doesn't have to be correct, I can make it as fast as you want!" "The CPU is so fast, it can execute an infinite loop is 6 seconds!" -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message