public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, torvalds@linux-foundation.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.32-rc not booting with Xen-3.2 (bisected)
Date: Tue, 27 Oct 2009 19:10:30 -0700	[thread overview]
Message-ID: <4AE7A816.3050607@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.01.0910271158100.9408@bogon.housecafe.de>

On 10/27/09 12:01, Christian Kujau wrote:
> On Tue, 27 Oct 2009 at 11:18, Jeremy Fitzhardinge wrote:
>   
>> $ gdb vmlinux
>> (gdb) x/i 0xffffffff812c50ad
>>     
> The value is always ffffffff812c50ad, gdb says:
>
> (gdb) x/i 0xffffffff812c50ad
> 0xffffffff812c50ad <xen_load_gdt_boot+252>:     ud2a  
>   

Please try the patch below.

>> Hm, sounds like a xenstored bug, or something is just pounding on it. 
>> Are there any other domains running, or other busy processes?
>>     
> Yes, there's another domU running. But the high load and xenstored 
> spinning is only happening when I try to start the domain with this 
> 2.6.32-rc kernel.
>   

That seems unlikely to be related (or a secondary effect of having a
domain crash).

    J

Subject: [PATCH] xen: set up mmu_ops before trying to set any ptes

xen_setup_stackprotector() ends up trying to set page protections,
so we need to have vm_mmu_ops set up before trying to do so.
Failing to do so causes an early boot crash.

[ Impact: Fix early crash under Xen. ]

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 3439616..23a4d80 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -1075,6 +1075,8 @@ asmlinkage void __init xen_start_kernel(void)
 	 * Set up some pagetable state before starting to set any ptes.
 	 */
 
+	xen_init_mmu_ops();
+
 	/* Prevent unwanted bits from being set in PTEs. */
 	__supported_pte_mask &= ~_PAGE_GLOBAL;
 	if (!xen_initial_domain())
@@ -1099,7 +1101,6 @@ asmlinkage void __init xen_start_kernel(void)
 	 */
 	xen_setup_stackprotector();
 
-	xen_init_mmu_ops();
 	xen_init_irq_ops();
 	xen_init_cpuid_mask();
 



  parent reply	other threads:[~2009-10-29 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 22:02 2.6.32-rc not booting with Xen-3.2 (bisected) Christian Kujau
2009-10-26 22:17 ` Christian Kujau
2009-10-26 22:55   ` Jeremy Fitzhardinge
2009-10-27  1:14     ` Christian Kujau
2009-10-27  1:26       ` Christian Kujau
2009-10-27  4:20         ` Jeremy Fitzhardinge
2009-10-27  5:01           ` Christian Kujau
2009-10-27 18:18             ` Jeremy Fitzhardinge
2009-10-27 19:01               ` Christian Kujau
2009-10-27 19:12                 ` Jeremy Fitzhardinge
2009-10-28  2:10                 ` Jeremy Fitzhardinge [this message]
2009-11-02  6:53                   ` Christian Kujau

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=4AE7A816.3050607@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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