public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Cc: Arnd Hannemann <Arnd.Hannemann@nets.rwth-aachen.de>,
	LKML <linux-kernel@vger.kernel.org>,
	"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ingo Molnar <mingo@elte.hu>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [bisected] 2.6.31 regression: fails to boot as xen guest
Date: Tue, 25 Aug 2009 22:07:51 +0300	[thread overview]
Message-ID: <1251227271.13451.16.camel@penberg-laptop> (raw)
In-Reply-To: <1251226720.13451.15.camel@penberg-laptop>

On Tue, 2009-08-25 at 21:58 +0300, Pekka Enberg wrote:
> On Tue, 2009-08-25 at 20:22 +0200, Arnd Hannemann wrote:
> > Pekka Enberg wrote:
> > > On Tue, 2009-08-25 at 19:49 +0200, Arnd Hannemann wrote:
> > >> Hi Pekka,
> > >>
> > >> Pekka Enberg wrote:
> > >>> On Tue, 2009-08-25 at 18:49 +0200, Arnd Hannemann wrote:
> > >>>>> Thanks for doing the bisect! Can we also see your .config
> > >>>>> also?
> > >>>> Config for -rc7 is attached. My bisect configs were based on
> > >>>> that
> > >>> Thanks! While we wait for the Xen people, you can try the
> > >>> following patch to see if we can narrow the bug down to
> > >>> trap_init().
> > >> Yes seems to be trap_init(). -rc7 with this patch applied boots up
> > >> to the prompt.
> > >
> > > Thanks for testing! Ingo, what do you think of the following patch?
> > > AFAICT, x86-32 is the only architecture playing with traps in
> > > mem_init() so this should be the safest fix for 2.6.31.
> > 
> > Hmm, -rc7 + this fix does not work for me :-/
> > Still hangs before any output...
> 
> Arnd, does this work for you?

Here's a version of the patch that actually compiles. :-)

			Pekka

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 13ffa5d..b6ff185 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -50,6 +50,7 @@ config X86
 	select HAVE_KERNEL_BZIP2
 	select HAVE_KERNEL_LZMA
 	select HAVE_ARCH_KMEMCHECK
+	select HAVE_ARCH_MEM_INIT_LATE if X86_32
 
 config OUTPUT_FORMAT
 	string
@@ -86,6 +87,10 @@ config STACKTRACE_SUPPORT
 config HAVE_LATENCYTOP_SUPPORT
 	def_bool y
 
+config HAVE_ARCH_MEM_INIT_LATE
+	def_bool y
+	depends on X86_32
+
 config FAST_CMPXCHG_LOCAL
 	bool
 	default y
diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c
index 3cd7711..488ed4b 100644
--- a/arch/x86/mm/init_32.c
+++ b/arch/x86/mm/init_32.c
@@ -956,13 +956,17 @@ void __init mem_init(void)
 	BUG_ON(VMALLOC_START				>= VMALLOC_END);
 	BUG_ON((unsigned long)high_memory		> VMALLOC_START);
 
-	if (boot_cpu_data.wp_works_ok < 0)
-		test_wp_bit();
-
 	save_pg_dir();
 	zap_low_mappings(true);
 }
 
+void __init mem_init_late(void)
+{
+	/* Interrupts are enabled at this point. */
+	if (boot_cpu_data.wp_works_ok < 0)
+		test_wp_bit();
+}
+
 #ifdef CONFIG_MEMORY_HOTPLUG
 int arch_add_memory(int nid, u64 start, u64 size)
 {
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 9a72cc7..eefcfbe 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1052,6 +1052,14 @@ extern void si_meminfo(struct sysinfo * val);
 extern void si_meminfo_node(struct sysinfo *val, int nid);
 extern int after_bootmem;
 
+#ifdef CONFIG_HAVE_ARCH_MEM_INIT_LATE
+extern void mem_init_late(void);
+#else
+static inline void mem_init_late(void)
+{
+}
+#endif
+
 #ifdef CONFIG_NUMA
 extern void setup_per_cpu_pageset(void);
 #else
diff --git a/init/main.c b/init/main.c
index 2d9d6bd..45d8dbd 100644
--- a/init/main.c
+++ b/init/main.c
@@ -643,6 +643,7 @@ asmlinkage void __init start_kernel(void)
 	set_gfp_allowed_mask(__GFP_BITS_MASK);
 
 	kmem_cache_init_late();
+	mem_init_late();
 
 	/*
 	 * HACK ALERT! This is early. We're enabling the console before



  reply	other threads:[~2009-08-25 19:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 15:48 [bisected] 2.6.31 regression: fails to boot as xen guest Arnd Hannemann
2009-08-25 16:29 ` Pekka Enberg
2009-08-25 16:49   ` Arnd Hannemann
2009-08-25 16:52     ` Pekka Enberg
2009-08-25 17:49       ` Arnd Hannemann
2009-08-25 18:03         ` Pekka Enberg
2009-08-25 18:08           ` Jeremy Fitzhardinge
2009-08-25 18:22           ` Arnd Hannemann
2009-08-25 18:25             ` Ingo Molnar
2009-08-25 18:30               ` Jeremy Fitzhardinge
2009-08-25 18:38                 ` Arnd Hannemann
2009-08-25 18:43                   ` Pekka Enberg
2009-08-25 19:31                     ` Jeremy Fitzhardinge
2009-08-25 19:30                   ` Jeremy Fitzhardinge
2009-08-25 18:58             ` Pekka Enberg
2009-08-25 19:07               ` Pekka Enberg [this message]
2009-08-25 19:13                 ` Arnd Hannemann
2009-08-26  9:59           ` Benjamin Herrenschmidt
2009-08-25 18:06       ` Jeremy Fitzhardinge
2009-08-25 18:14         ` Pekka Enberg
2009-08-26 11:54 ` Pasi Kärkkäinen
2009-08-26 12:00   ` Pekka Enberg

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=1251227271.13451.16.camel@penberg-laptop \
    --to=penberg@cs.helsinki.fi \
    --cc=Arnd.Hannemann@nets.rwth-aachen.de \
    --cc=benh@kernel.crashing.org \
    --cc=hannemann@nets.rwth-aachen.de \
    --cc=hannes@cmpxchg.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=xen-devel@lists.xensource.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