From: Liang Li <liang.li@windriver.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, wangchen@cn.fujitsu.com,
akpm@linux-foundation.org
Subject: Re: [PATCH] x86: let 'reservetop' functioning right
Date: Wed, 31 Mar 2010 10:49:44 +0800 [thread overview]
Message-ID: <20100331024944.GB9847@localhost> (raw)
In-Reply-To: <1269478445-4335-1-git-send-email-liang.li@windriver.com>
Hi Ingo,
Seems the problem still there in 2.6.34-rc3. When pass
'reservetop=0x1000' to x86_32 kernel, kernel hangs on
very early boot stage.
Do we have any plan to abandon 'reservetop' or due to
some reason that the patch is non-acceptable?
Thanks,
-Liang Li
On Thu, Mar 25, 2010 at 08:54:05AM +0800, Liang Li wrote:
> When specify 'reservetop=0xabc000' kernel parameter, kernel will hang
> on boot due to a early_ioremap bug that relate to commit 8827247ff.
>
> The root cause of boot failure problem is the value of 'slot_virt[i]'
> was initialized in setup_arch->early_ioremap_init. But later in
> setup_arch, the function 'parse_early_param' will modify 'FIXADDR_TOP'
> when 'reservetop=0xbadc0de' being specified.
>
> The simplest fix might be use __fix_to_virt(idx0) to get updated value
> of 'FIXADDR_TOP' in '__early_ioremap' instead of reference old value
> from slot_virt[slot] directly.
>
> Signed-off-by: Liang Li <liang.li@windriver.com>
> ---
> arch/x86/mm/ioremap.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index 5eb1ba7..ea82ef0 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86/mm/ioremap.c
> @@ -537,9 +537,9 @@ __early_ioremap(resource_size_t phys_addr, unsigned long size, pgprot_t prot)
> --nrpages;
> }
> if (early_ioremap_debug)
> - printk(KERN_CONT "%08lx + %08lx\n", offset, slot_virt[slot]);
> + printk(KERN_CONT "%08lx + %08lx\n", offset, __fix_to_virt(idx0));
>
> - prev_map[slot] = (void __iomem *)(offset + slot_virt[slot]);
> + prev_map[slot] = (void __iomem *)(offset + __fix_to_virt(idx0));
> return prev_map[slot];
> }
>
> --
> 1.6.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2010-03-31 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 0:54 [PATCH] x86: let 'reservetop' functioning right Liang Li
2010-03-31 2:49 ` Liang Li [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=20100331024944.GB9847@localhost \
--to=liang.li@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wangchen@cn.fujitsu.com \
/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