From: "H. Peter Anvin" <hpa@zytor.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@amd64.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"Liu, Jinsong" <jinsong.liu@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Xen-devel] [PATCH 1/3] Add mcelog support for xen platform
Date: Mon, 23 Apr 2012 09:17:28 -0700 [thread overview]
Message-ID: <4F958098.1050402@zytor.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F170EF841@ORSMSX104.amr.corp.intel.com>
On 04/23/2012 08:27 AM, Luck, Tony wrote:
>> Because, if you'd hooked into it, just imagine one fine day, when we
>> remove mcelog support, what screaming the xen people will be doing when
>> mcelog doesn't work anymore.
>
> Agreed. Even before we get to deleting mcelog, "struct mce" can change (new
> fields could be added) ... and you don't want to have your hypervisor to
> have to know which version of Linux it is talking to.
This is a great example on the fundamental problem with Xen, or rather
the approach that Xen has taken of grabbing random kernel internals and
claiming them as APIs (or, in some cases even as ABIs.) A lot of these
have had problems that are now very nearly unfixable, and that has
seriously stalled out the ability of evolve the Linux kernel in some
areas. Note that the cost of this is borne by the development
community, not by the Xen maintainers.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-04-23 16:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 13:29 [PATCH 1/3] Add mcelog support for xen platform Liu, Jinsong
2012-04-20 18:40 ` Konrad Rzeszutek Wilk
2012-04-20 20:00 ` Liu, Jinsong
2012-04-21 4:14 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-04-21 10:45 ` Borislav Petkov
2012-04-23 2:18 ` Konrad Rzeszutek Wilk
2012-04-23 6:09 ` Borislav Petkov
2012-04-23 15:06 ` Konrad Rzeszutek Wilk
2012-04-23 15:59 ` Borislav Petkov
2012-04-23 16:23 ` Luck, Tony
2012-04-23 16:54 ` Konrad Rzeszutek Wilk
2012-04-23 16:17 ` Liu, Jinsong
2012-04-23 15:27 ` Luck, Tony
2012-04-23 15:32 ` Konrad Rzeszutek Wilk
2012-04-23 16:17 ` Luck, Tony
2012-04-23 16:51 ` Konrad Rzeszutek Wilk
2012-04-23 15:43 ` Liu, Jinsong
2012-04-23 16:26 ` H. Peter Anvin
2012-04-23 17:05 ` Konrad Rzeszutek Wilk
2012-04-23 17:23 ` H. Peter Anvin
2012-04-23 16:17 ` H. Peter Anvin [this message]
2012-04-23 17:03 ` Konrad Rzeszutek Wilk
2012-04-23 17:16 ` H. Peter Anvin
2012-04-24 8:27 ` Andi Kleen
2012-04-25 8:11 ` Ingo Molnar
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=4F958098.1050402@zytor.com \
--to=hpa@zytor.com \
--cc=bp@amd64.org \
--cc=jinsong.liu@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox