[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080117214228.GD12631@alberich.amd.com>
Date: Thu, 17 Jan 2008 22:42:28 +0100
From: "Andreas Herrmann3" <andreas.herrmann3@....com>
To: "Ingo Molnar" <mingo@...e.hu>
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
On Thu, Jan 17, 2008 at 10:13:08PM +0100, Ingo Molnar wrote:
>
> * Andreas Herrmann3 <andreas.herrmann3@....com> wrote:
>
> > Yes.
> >
> > Meanwhile I have figured out that it is some ACPI stuff that maps the
> > page cached. I've changed the ioremap's in drivers/acpi/osl.c to
> > ioremap_nocache. See attached patch.
> >
> > Now the machine boots without conflicts.
>
> ah, nice!
>
> but in general we must be robust enough in this case and just degrade
> any overlapping page to UC (and emit a warning perhaps) - instead of
> failing the ioremap and thus failing the driver (and the bootup).
>
> Does my third patch (which falls back to UC in case of attribute
> conflicts, also attached below) instead of your ioremap_nocache() patch
> solve your bootup problem too?
I'll check this asap
> but i have not seen this message in your boot log. Could you boot with
> early_ioremap_debug and send us the dmesg - i'm curious which ACPI
> tables are actively mapped while those devices are initialized.
Hmm, early_ioremap_debug exists only in ioremap_32.c
Have to adapt the 64-bit version first.
But wait the 64-bit code contains already debug output for this. See
the boot-logs that I have attached to my previous mails.
(Interestingly the code for 64-bit early_io(re/un)map resides not in
ioremap_64.c but in init_64.c.)
Andreas
--
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