xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Luke S Crawford <lsc@prgmr.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board
Date: Wed, 12 May 2010 09:10:22 +0100	[thread overview]
Message-ID: <C8102100.1408D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C80A4888.13B50%keir.fraser@eu.citrix.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

On 07/05/2010 22:45, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

> On 07/05/2010 22:10, "Luke S Crawford" <lsc@prgmr.com> wrote:
> 
>> Keir Fraser <keir.fraser@eu.citrix.com> writes:

> Ah, looks like half the MCE stuff is not even hooked up the mce boot
> parameter. Well, I expect Christoph Egger can help: he implemented a lot of
> the MCE mechanism, and especially the AMD parts.
> 
> I think the mce boot parameter should, when disabled, cause the MCE feature
> bits to be removed from Xen's copy of CPUID feature flags. That would easily
> disable all MCE logic throughout Xen.

Actually I think the attached patch should work, in conjunction with
specifying no-mce (4.0/unstable) or nomce (3.4) as a Xen boot parameter. Let
me know if it works okay for you.

I've applied the patch to xen-unstable as c/s 21360.

 -- Keir


[-- Attachment #2: 00-mce --]
[-- Type: application/octet-stream, Size: 387 bytes --]

diff -r 0079f76e906f xen/arch/x86/cpu/mcheck/non-fatal.c
--- a/xen/arch/x86/cpu/mcheck/non-fatal.c	Wed May 12 08:53:27 2010 +0100
+++ b/xen/arch/x86/cpu/mcheck/non-fatal.c	Wed May 12 09:06:37 2010 +0100
@@ -91,7 +91,7 @@
 	struct cpuinfo_x86 *c = &boot_cpu_data;
 
 	/* Check for MCE support */
-	if (!mce_available(c))
+	if (mce_disabled || !mce_available(c))
 		return -ENODEV;
 
 	/*

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-05-12  8:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  1:45 (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board Luke S Crawford
2010-05-07  7:14 ` Keir Fraser
2010-05-07 21:10   ` Luke S Crawford
2010-05-07 21:45     ` Keir Fraser
2010-05-12  8:10       ` Keir Fraser [this message]
2010-05-20  9:13         ` Luke S Crawford
2010-05-20 12:54           ` Keir Fraser
2010-05-20 14:01             ` Christoph Egger
2010-07-15  5:40         ` Luke S Crawford
2010-07-15  7:04           ` Keir Fraser
2010-07-15  8:34             ` Luke S Crawford

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=C8102100.1408D%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=lsc@prgmr.com \
    --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;
as well as URLs for NNTP newsgroup(s).