From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir.fraser@eu.citrix.com>,
"Ke, Liping" <liping.ke@intel.com>
Subject: Re: [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
Date: Mon, 12 Jan 2009 15:03:16 +0100 [thread overview]
Message-ID: <200901121503.17232.Christoph.Egger@amd.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401C4C32E95@PDSMSX501.ccr.corp.intel.com>
On Friday 19 December 2008 07:19:16 Ke, Liping wrote:
> Hi, all
>
> Patch 4 is the main patch for CMCI enabling in XEN. It adds the CMCI
> interrupt handler, new common CMCI/MCA init process,CMCI owner judge
> algorithm when bring_up CPUs, CPU on/offline and polling mechanisms, etc
>
> Thanks & Regards,
> Criping
This patch changes the public API. There's no need to change
struct mcinfo_extended. The marshalling technique allows to use
this structure as often as needed. Please undo this change.
struct mcinfo_global is also changed. Why can't mc_coreid not be
filled with the apicid ? Adding the apicid field breaks the alignment
causing troubles on 32bit-guest-on-64bit-hypervisor.
Christoph
--
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34
85609 Dornach b. München
Geschäftsführer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis München
Registergericht München, HRB Nr. 43632
next prev parent reply other threads:[~2009-01-12 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 6:19 [patch 4/4]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs Ke, Liping
2009-01-12 14:03 ` Christoph Egger [this message]
2009-01-13 2:12 ` Ke, Liping
2009-01-13 11:21 ` Christoph Egger
2009-01-13 16:48 ` Frank Van Der Linden
2009-01-13 17:11 ` Christoph Egger
2009-01-13 17:29 ` Frank van der Linden
2009-01-14 2:11 ` Jiang, Yunhong
2009-01-14 1:35 ` Ke, Liping
2009-01-14 2:58 ` Jiang, Yunhong
2009-01-14 4:13 ` Frank van der Linden
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=200901121503.17232.Christoph.Egger@amd.com \
--to=christoph.egger@amd.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.