From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "Kleen, Andi" <andi.kleen@intel.com>,
Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [pvops-dom0] Adding MCA logging support in pv_ops
Date: Thu, 13 Aug 2009 13:55:33 -0700 [thread overview]
Message-ID: <4A847DC5.4070604@goop.org> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098402CE11BCA8@PDSMSX501.ccr.corp.intel.com>
On 08/09/09 20:08, Ke, Liping wrote:
> Hi, Jeremy
> Thanks for the detailed comments. I modified below:
> 1. change cs902 to cs: 75ebfa7fbdc
> 2. I renamed mce_dom0.c to mce.c and dom0 related message/variables.
> 3. use #ifdef CONFIG_XEN_MCE instead.
> Thanks a lot!
>
I pushed this to rebase/dom0/mce, but I haven't merged it with master
yet. I changed the way the MCE/MCA feature bits get masked: they're
masked in non-dom0 domains like ACPI and APIC, but left as-is otherwise,
since the kernel shouldn't care about them unless CONFIG_X86_MCE_INTEL
is enabled anyway.
J
next prev parent reply other threads:[~2009-08-13 20:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 5:15 [pvops-dom0] Adding MCA logging support in pv_ops Ke, Liping
2009-07-30 8:24 ` Jan Beulich
2009-07-30 8:45 ` Ke, Liping
2009-07-30 9:23 ` Ke, Liping
2009-07-30 17:14 ` Jeremy Fitzhardinge
2009-08-05 2:13 ` Ke, Liping
2009-08-05 22:55 ` Jeremy Fitzhardinge
2009-08-07 2:32 ` Ke, Liping
2009-08-07 18:07 ` Jeremy Fitzhardinge
2009-08-10 3:08 ` Ke, Liping
2009-08-13 20:55 ` Jeremy Fitzhardinge [this message]
2009-08-18 9:02 ` Jan Beulich
2009-08-18 9:25 ` Ke, Liping
2009-08-18 17:51 ` Jeremy Fitzhardinge
2009-08-19 1:25 ` Ke, Liping
2009-08-19 1:31 ` Ke, Liping
2009-08-05 2:54 ` Ke, Liping
2009-08-05 2:57 ` Ke, Liping
2009-07-31 15:19 ` Andi Kleen
2009-07-30 9:57 ` Christoph Egger
2009-08-05 1:57 ` Ke, Liping
2009-08-05 9:16 ` Christoph Egger
2009-08-06 1:37 ` Ke, Liping
2009-08-06 7:27 ` Christoph Egger
2009-08-06 8:49 ` Christoph Egger
2009-08-07 1:48 ` Ke, Liping
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=4A847DC5.4070604@goop.org \
--to=jeremy@goop.org \
--cc=Christoph.Egger@amd.com \
--cc=JBeulich@novell.com \
--cc=andi.kleen@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=liping.ke@intel.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.