public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ioremap_cached()
Date: Thu, 30 Mar 2006 22:27:53 +0200	[thread overview]
Message-ID: <200603302227.53343.ak@suse.de> (raw)
In-Reply-To: <D3AB1B22-E33B-409F-BF54-2F6FD071337A@kernel.crashing.org>

On Thursday 30 March 2006 22:21, Kumar Gala wrote:
> 
> On Mar 30, 2006, at 2:17 PM, Andi Kleen wrote:
> 
> > On Thursday 30 March 2006 22:14, Matthew Wilcox wrote:
> >
> >> I think you misunderstood.  The right interface to call, that should
> >> work everywhere, should be the simple, obvious one.  ioremap().  That
> >> effectively is what everyone gets anyway (since they test on x86).
> >> So change the *definition* of ioremap() to be uncached.  Then we  
> >> can add
> >> ioremap_wc() and ioremap_cached() for these special purpose mappings.
> >
> > That would break all the current users who do ioremap on memory
> > and want it cached.
> 
> What's an example of this?  I ask since on powerpc ioremap() is  
> always _PAGE_NO_CACHE.

ACPI, IPMI, DMI, ... I bet there are more. It's needed every time
a driver needs to look for some firmware table because it might
not be mapped.

-Andi

  reply	other threads:[~2006-03-30 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 16:41 [PATCH] ioremap_cached() Matthew Wilcox
2006-03-30 18:27 ` Andi Kleen
2006-03-30 19:34   ` Matthew Wilcox
2006-03-30 19:50     ` Andi Kleen
2006-03-30 20:14       ` Matthew Wilcox
2006-03-30 20:17         ` Andi Kleen
2006-03-30 20:21           ` Kumar Gala
2006-03-30 20:27             ` Andi Kleen [this message]
2006-03-31 11:20 ` Arjan van de Ven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200603302227.53343.ak@suse.de \
    --to=ak@suse.de \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox