From: Christoph Egger <Christoph.Egger@amd.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: "Frank.Vanderlinden@Sun.COM" <Frank.Vanderlinden@sun.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [RFC] [PATCH 0/2] Some clean-up to MCA handling
Date: Mon, 19 Apr 2010 12:06:52 +0200 [thread overview]
Message-ID: <201004191206.53002.Christoph.Egger@amd.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731D797FD1@shsmsx501.ccr.corp.intel.com>
On Monday 19 April 2010 10:58:44 Jiang, Yunhong wrote:
> These two patches includes some clean-up/changes to MCA handling.
>
> The mce_extended.patch change the method to get the extended MCA
> information. This change is somwhat straightforward and is easy to
> understand. But please notice it changes some interface in
> include/public/arch-x86/xen-mca.h.
This breaks backward-compatibility. You can't change the API/ABI just for the
sake of "easier" internal handling.
Please explain:
- what exactly is wrong with the interface as it is in upstream ?
- what *requries* an API/ABI change ?
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-04-19 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 8:58 [RFC] [PATCH 0/2] Some clean-up to MCA handling Jiang, Yunhong
2010-04-19 10:06 ` Christoph Egger [this message]
2010-04-19 15:32 ` Jiang, Yunhong
2010-04-19 15:52 ` Christoph Egger
2010-04-20 8:06 ` Jiang, Yunhong
2010-04-20 8:56 ` Christoph Egger
2010-04-20 9:21 ` Jiang, Yunhong
-- strict thread matches above, loose matches on Subject: below --
2010-06-07 9:05 Jiang, Yunhong
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=201004191206.53002.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Frank.Vanderlinden@sun.com \
--cc=keir.fraser@eu.citrix.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.