public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Andi Kleen <andi@firstfloor.org>, Frans Pop <elendil@planet.nl>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Unable to continue testing of 2.6.25
Date: Tue, 19 Feb 2008 11:42:46 -0800	[thread overview]
Message-ID: <20080219194246.GA20438@linux-os.sc.intel.com> (raw)
In-Reply-To: <adahcg6jco7.fsf@cisco.com>

On Mon, Feb 18, 2008 at 11:18:48AM -0800, Roland Dreier wrote:
>  > > AFAIK mapping PCI memory WB is not allowed, so WC is really our only
>  > > choice.
> 
>  > afaik that depends on the BAR being prefetchable or not.
> 
> In my case the BAR is prefetchable.

Even if the BAR is prefetchable, on some platforms mapping MMIO space
as WB can cause bad results like machine check etc.

>  > (and by your argument, ioremap_cached() would not be useful, and since that was, until
>  > 2.6.25-rc1, the default behavior for ioremap(), would have caused massive problems)
> 
> I'm not sure what ioremap_cached() would really do in my case, since
> the MTRRs for PCI memory are set to UC, so without monkeying with MTRR
> contents (which can't really be done safely) the only choices we have
> are leaving the mapping as UC or using PAT to get WC.

thanks,
suresh

      reply	other threads:[~2008-02-19 19:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17  9:25 Unable to continue testing of 2.6.25 Frans Pop
2008-02-17 13:16 ` Adrian Bunk
2008-02-17 19:24   ` Tilman Schmidt
2008-02-17 19:44     ` Adrian Bunk
2008-02-17 20:38       ` Paul Jackson
2008-02-17 20:51         ` Arjan van de Ven
2008-02-19 22:41           ` Frans Pop
2008-02-18  2:33     ` David Miller
2008-02-18 11:40       ` Tilman Schmidt
2008-02-18 12:27       ` Andi Kleen
2008-02-19 21:55   ` Frans Pop
2008-02-19 21:59     ` Arjan van de Ven
2008-02-19 22:15     ` Harvey Harrison
2008-02-19 22:19     ` Adrian Bunk
2008-02-19 22:49       ` Frans Pop
2008-02-17 20:46 ` Arjan van de Ven
2008-02-18 12:31   ` Andi Kleen
2008-02-18 16:50     ` Arjan van de Ven
2008-02-18 17:11       ` Andi Kleen
2008-02-18 17:32         ` Arjan van de Ven
2008-02-18 18:40           ` Alan Cox
2008-02-18 18:52             ` Arjan van de Ven
2008-02-18 20:15               ` Alan Cox
2008-02-18 18:52           ` Andi Kleen
2008-02-18 18:32             ` Arjan van de Ven
2008-02-18 19:18             ` Ingo Molnar
2008-02-19  9:35               ` Andi Kleen
2008-02-18 18:53           ` Roland Dreier
2008-02-18 19:07             ` Arjan van de Ven
2008-02-18 19:18               ` Roland Dreier
2008-02-19 19:42                 ` Siddha, Suresh B [this message]

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=20080219194246.GA20438@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    --cc=torvalds@linux-foundation.org \
    /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