[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080117223551.GA23543@elte.hu>
Date: Thu, 17 Jan 2008 23:35:51 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Andreas Herrmann3 <andreas.herrmann3@....com>
Cc: Venki Pallipadi <venkatesh.pallipadi@...el.com>, ak@....de,
ebiederm@...ssion.com, rdreier@...co.com,
torvalds@...ux-foundation.org, gregkh@...e.de, airlied@...net.ie,
davej@...hat.com, tglx@...utronix.de, hpa@...or.com,
akpm@...ux-foundation.org, arjan@...radead.org,
jesse.barnes@...el.com, davem@...emloft.net,
linux-kernel@...r.kernel.org, suresh.b.siddha@...el.com
Subject: Re: [patch 0/4] x86: PAT followup - Incremental changes and bug
fixes
* Andreas Herrmann3 <andreas.herrmann3@....com> wrote:
> > I'll check this asap
>
> So, now that I've avoided this tiny NULL-pointer-dereference, the
> system boots fine as well with your (slightly modified) patch. See
> dmesg attached.
for now i applied your ioremap_uncached() patch and removed my patch.
my patch might work if the MTRR marks that area UC. Does it on your
system?
if the MTRRs (as set up by the BIOS) keep it at WB, then the ACPI
ioremap() is already unsafe: the mmio area that happens to be there
might be prefetched by the CPU.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists