From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [pvops-dom0]Update MCE LOG data
Date: Mon, 19 Apr 2010 12:53:36 -0700 [thread overview]
Message-ID: <4BCCB4C0.4040601@goop.org> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731D797FC3@shsmsx501.ccr.corp.intel.com>
On 04/19/2010 01:55 AM, Ke, Liping wrote:
> Hi, Jeremy and all
> This small patch is to pass mcg_cap information from XEN to DOM0 since now
> new pv-ops kernel's mce data structure is changed and need this mcg_cap information.
>
Is this forwards and backwards compatible?
J
> Thanks& Regards,
> Criping
>
>
>
>
> From 475b637e8dabb32446ee28e6b1235729e4b0f4bb Mon Sep 17 00:00:00 2001
> From: Liping Ke <liping.ke@intel.com>
> Date: Mon, 19 Apr 2010 16:42:48 +0800
> Subject: [PATCH] Update MCE LOG data
> More mce data is provided in new DOM0 kernel, we need to pass
> mcg_cap information from XEN to DOM0 in vIRQ accordingly.
>
> ---
> drivers/xen/mce.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/xen/mce.c b/drivers/xen/mce.c
> index b354dc8..8758e75 100644
> --- a/drivers/xen/mce.c
> +++ b/drivers/xen/mce.c
> @@ -72,6 +72,7 @@ static int convert_log(struct mc_info *mi)
> m.socketid = g_physinfo[i].mc_chipid;
> m.cpu = m.extcpu = g_physinfo[i].mc_cpunr;
> m.cpuvendor = (__u8)g_physinfo[i].mc_vendor;
> + m.mcgcap = g_physinfo[i].mc_msrvalues[0].value;
> x86_mcinfo_lookup(&mic, mi, MC_TYPE_BANK);
> do {
> if (mic == NULL || mic->size == 0)
> @@ -83,6 +84,7 @@ static int convert_log(struct mc_info *mi)
> m.addr = mc_bank->mc_addr;
> m.tsc = mc_bank->mc_tsc;
> m.bank = mc_bank->mc_bank;
> + m.finished = 1;
> /*log this record*/
> mce_log(&m);
> }
>
next prev parent reply other threads:[~2010-04-19 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 8:55 [pvops-dom0]Update MCE LOG data Ke, Liping
2010-04-19 19:53 ` Jeremy Fitzhardinge [this message]
2010-04-20 1:16 ` Ke, Liping
-- strict thread matches above, loose matches on Subject: below --
2010-04-19 8:56 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=4BCCB4C0.4040601@goop.org \
--to=jeremy@goop.org \
--cc=liping.ke@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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.