Re: cacheble to uncachble change

From: David Mosberger <>
Date: 2004-04-27 10:03:23
>>>>> On Mon, 26 Apr 2004 16:35:55 -0500, Robin Holt <> said:

  >> In any case, just be careful about not introducing memory attribute
  >> aliases.  You need to be especially careful since the kernel accesses
  >> memory with granule-sized mappings (normally 64MB page size, but on
  >> some machines its 16MB).

  Robin> Be very careful when using uncached memory.  On the SGI
  Robin> systems, we always allocate memory for uncached out of a
  Robin> seperate granule.  We were experiencing memory corruption due
  Robin> to kernel speculative load which fetched the cache line
  Robin> dirty.  This would result in cache lines that were
  Robin> occasionally out of date.  The problem was resolved on our
  Robin> kernels by drivers/char/fetchop.c which provides a seperate
  Robin> device for mapping when you want uncached or write coalesced
  Robin> memory.

Are you just re-stating my caveat about memory-attribute-aliasing or
are you saying something else?  If the latter, I'm not following.  If
the former, I certainly agree: memory attribute-aliasing leads to
really nasty-to-track-down bugs.  Hence, you want to make sure
_upfront_ that it doesn't occur.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Mon Apr 26 20:03:39 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:25 EST