From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: machine check report on HVM startup
Date: Wed, 13 Aug 2008 15:17:09 +0200 [thread overview]
Message-ID: <200808131517.09722.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C4C89694.2564F%keir.fraser@eu.citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
On Wednesday 13 August 2008 14:48:04 Keir Fraser wrote:
> On 13/8/08 13:40, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> >>>> This looks to me, there's a non-public event channel using the same
> >>>> number as VIRQ_MCA which fires when launching memtest as HVM guest.
> >>>
> >>> I don't think this is the case. Sounds easy to repro this issue though.
> >>> I'll give it a go.
> >>
> >> I can boot a memtest-3.4 ISO in an HVM guest on PAE hypervisor just
> >> fine.
> >
> > Does your Dom0 kernel registrate the machine check event handler ?
> > If not, then it things go fine. If yes, then you should see the flood of
> > VIRQ_MCA events in the Dom0.
>
> How do I make it do that?
Assuming you use Linux as Dom0, apply the attached patch to your local tree.
With it, you should see a flood of "xen_mca: HW reported correctable error(s)"
Dom0 kernel messages.
Note, the patch is not intended to go upstream. There will be something better
in the future.
Christoph
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
[-- Attachment #2: linux_xenmca.diff --]
[-- Type: text/x-diff, Size: 1127 bytes --]
diff -r c110692c140f arch/i386/kernel/cpu/mcheck/non-fatal.c
--- a/arch/i386/kernel/cpu/mcheck/non-fatal.c Wed Aug 13 10:00:09 2008 +0100
+++ b/arch/i386/kernel/cpu/mcheck/non-fatal.c Wed Aug 13 15:10:47 2008 +0200
@@ -60,9 +60,31 @@ static void mce_work_fn(void *data)
schedule_delayed_work(&mce_work, MCE_RATE);
}
+/* Privileged receive callback and transmit kicker. */
+static irqreturn_t xenmca_event(int irq, void *dev_id,
+ struct pt_regs *regs)
+{
+ printk("xen_mca: HW reported correctable error(s)\n");
+
+ return IRQ_HANDLED;
+}
+
+static int mca_event_irq;
+
static int __init init_nonfatal_mce_checker(void)
{
struct cpuinfo_x86 *c = &boot_cpu_data;
+
+ if (is_initial_xendomain()) {
+ mca_event_irq = bind_virq_to_irqhandler(
+ VIRQ_MCA,
+ 0,
+ xenmca_event,
+ 0,
+ "mca0",
+ NULL);
+ BUG_ON(mca_event_irq < 0);
+ }
/* Check for MCE support */
if (!cpu_has(c, X86_FEATURE_MCE))
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-08-13 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 11:48 machine check report on HVM startup Christoph Egger
2008-08-13 12:27 ` Keir Fraser
2008-08-13 12:36 ` Keir Fraser
2008-08-13 12:40 ` Christoph Egger
2008-08-13 12:48 ` Keir Fraser
2008-08-13 13:17 ` Christoph Egger [this message]
2008-08-13 13:22 ` Keir Fraser
2008-08-13 13:17 ` Keir Fraser
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=200808131517.09722.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=keir.fraser@eu.citrix.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 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.