Re: [RFC] MMIO accessors & barriers documentation
- From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
- Date: Mon, 11 Sep 2006 23:48:33 -0600
Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> writes:
"Except where the underlying device is marked as cachable or
prefetchable"
You aren't supposed to use MMIO accessors on cacheable memory, are you ?
Why not. Providing it is in MMIO space, consider ROMs for example or
write path consider frame buffers.
Frame buffers are rarely cachable as such, on x86 they are usually
write-combining. Which means that the writes can be merged and
possibly reordered while they are being written but they can't be
cached. Most arches I believe have something that roughly corresponds
to write combining.
Ensuring we can still use this optimization to mmio space is
moderately important.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC] MMIO accessors & barriers documentation
- From: Benjamin Herrenschmidt
- Re: [RFC] MMIO accessors & barriers documentation
- References:
- [RFC] MMIO accessors & barriers documentation
- From: Benjamin Herrenschmidt
- Re: [RFC] MMIO accessors & barriers documentation
- From: Alan Cox
- Re: [RFC] MMIO accessors & barriers documentation
- From: Benjamin Herrenschmidt
- Re: [RFC] MMIO accessors & barriers documentation
- From: Alan Cox
- [RFC] MMIO accessors & barriers documentation
- Prev by Date: Re: [RFC] MMIO accessors & barriers documentation
- Next by Date: Re: [PATCH V2] display: Driver ks0108 and cfag12864b
- Previous by thread: Re: [RFC] MMIO accessors & barriers documentation
- Next by thread: Re: [RFC] MMIO accessors & barriers documentation
- Index(es):