[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101014060617.GA4751@elte.hu>
Date: Thu, 14 Oct 2010 08:06:17 +0200
From: Ingo Molnar <mingo@...e.hu>
To: mingo@...hat.com, hpa@...or.com, jeremy@...p.org,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
hpa@...ux.intel.com, jeremy.fitzhardinge@...rix.com,
Yinghai Lu <yinghai@...nel.org>
Cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:core/memblock] x86-64: Only set max_pfn_mapped to 512 MiB
if we enter via head_64.S
* Ingo Molnar <mingo@...e.hu> wrote:
> * tip-bot for Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>
> > Commit-ID: 859ee4f57fb4e91de8439496f62eb996f4a28ca8
> > Gitweb: http://git.kernel.org/tip/859ee4f57fb4e91de8439496f62eb996f4a28ca8
> > Author: Jeremy Fitzhardinge <jeremy@...p.org>
> > AuthorDate: Wed, 13 Oct 2010 16:34:15 -0700
> > Committer: H. Peter Anvin <hpa@...ux.intel.com>
> > CommitDate: Wed, 13 Oct 2010 17:09:59 -0700
> >
> > x86-64: Only set max_pfn_mapped to 512 MiB if we enter via head_64.S
> >
> > head_64.S maps up to 512 MiB, but that is not necessarity true for
> > other entry paths, such as Xen.
>
> These two commits are a boot crasher on x86 defconfig (64-bit):
Caused by this one of the two:
859ee4f: x86-64: Only set max_pfn_mapped to 512 MiB if we enter via head_64.S
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