Re: pgprot_writecombine & shub 1.x

From: Jes Sorensen <>
Date: 2005-01-20 20:03:19
>>>>> "David" == David Mosberger <> writes:

>>>>> On Wed, 19 Jan 2005 09:28:27 -0800, Jesse Barnes <> said:
Jesse> So I guess we need to add ia64_set_page_wc() and
Jesse> ia64_set_page_uc() functions that set the appropriate page bits
Jesse> or return errors if the EFI memory map says a particular mode
Jesse> isn't allowed?  How does that sound to you, Tony & David?
Jesse> Fortunately there aren't that many users of pgprot_writecombine
Jesse> so fixing them up should be easy.

David> I'm still not clear which case you're concerned about: mapping
David> I/O memory with WC or mapping real memory with WC.  For the
David> latter, I think we may need an API to allocate memory that can
David> be mapped WC (if possible at all).


What about real memory and mapping it uncached? Do we need to play the
same trick before allowing it to be mapped uncached? and for IO memory
mapped uncached?

Trying to map real memory uncached was what made me stumble upon the
PREFETCH_VISIBILITY limitation in the PAL code.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Thu Jan 20 04:03:56 2005

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