From: Jeremy Fitzhardinge <jeremy@goop.org>
To: deshantm@gmail.com
Cc: Ingo Molnar <mingo@elte.hu>,
xen-devel mailing list <xen-devel@lists.xensource.com>
Subject: Re: 2.6.27-rc4 pvops domU on Xen 3.3 Kernel panic
Date: Thu, 28 Aug 2008 10:23:19 -0700 [thread overview]
Message-ID: <48B6DF07.7040103@goop.org> (raw)
In-Reply-To: <1e16a9ed0808272026me171d36g34efe97f51194cdc@mail.gmail.com>
Todd Deshane wrote:
> I'm trying to build a kernel.org domU to run on Xen 3.3
>
> My first attempt produced a kernel panic.
>
> Below is my setup and the panic that occurred during boot right after:
>
> [ 0.004000] Initializing cgroup subsys cpuacct
> [ 0.008000]
> [ 0.008000] CPU 0/0 -> Node 0
> [ 0.008000] CPU: Physical Processor ID: 0
> [ 0.008000] CPU: Processor Core ID: 0
> [ 0.008000] SMP alternatives: switching to UP code
> [ 0.020001] Freeing SMP alternatives: 22k freed
>
> The same panic happens for both default vcpus, vcpus=1, and vcpus=2
>
> Any ideas or hints?
>
Ah, it's a bug which has been since fixed, but it looks like the fix
hasn't made it into mainline. Patch below.
(Ingo, can you push this to Linus? It needs to be in mainline.)
J
commit b56afe1d41653fb07ab1b5af5ccc12001c4dd5a0
Author: Eduardo Habkost <ehabkost@redhat.com>
Date: Thu Jul 24 12:15:45 2008 -0300
x86, xen: Use native_pte_flags instead of native_pte_val for .pte_flags
Using native_pte_val triggers the BUG_ON() in the paravirt_ops
version of pte_flags().
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 06219e6..e2767c2 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -1347,7 +1347,7 @@ static const struct pv_mmu_ops xen_mmu_ops __initdata = {
.ptep_modify_prot_commit = __ptep_modify_prot_commit,
.pte_val = xen_pte_val,
- .pte_flags = native_pte_val,
+ .pte_flags = native_pte_flags,
.pgd_val = xen_pgd_val,
.make_pte = xen_make_pte,
next prev parent reply other threads:[~2008-08-28 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 3:26 2.6.27-rc4 pvops domU on Xen 3.3 Kernel panic Todd Deshane
2008-08-28 17:23 ` Jeremy Fitzhardinge [this message]
2008-08-29 1:12 ` Todd Deshane
2008-08-29 14:03 ` Todd Deshane
2008-09-06 18:14 ` Ingo Molnar
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=48B6DF07.7040103@goop.org \
--to=jeremy@goop.org \
--cc=deshantm@gmail.com \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.