From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Borislav Petkov <bp@amd64.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"Liu, Jinsong" <jinsong.liu@intel.com>,
tony.luck@intel.com, x86@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>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
torvalds@linux-foundation.org
Subject: Re: [Xen-devel] [PATCH 1/3] Add mcelog support for xen platform
Date: Wed, 25 Apr 2012 10:11:25 +0200 [thread overview]
Message-ID: <20120425081125.GA19849@gmail.com> (raw)
In-Reply-To: <m2aa21o7pk.fsf@firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> Borislav Petkov <bp@amd64.org> writes:
>
> > 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.
>
> That's simple. /dev/mcelog is a widely used user space ABI
> [...]
*COUGH* *SPLUTTER* *LAUGH*.
Thanks for making my day with the self-serving exaggeration of
the year.
In truth /dev/mcelog is one of the crappiest ABIs Linux has -
full stop. As a result it's barely used by anyone who can avoid
it - its main usecase is the utility you wrote for it and some
enterprise folks who desperately need that data and don't care
how they get it. The mcelog user-space utility sucks too,
understandably.
Nevertheless we probably have to keep the ABI around until a
truly better replacement is out there (the RAS daemon for
example) and mcelog usage eclipses to obscurity, but by all
means we want to limit its further spreading /dev/mcelog to
areas it has not polluted yet ...
Thanks,
Ingo
prev parent reply other threads:[~2012-04-25 8:11 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
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 [this message]
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=20120425081125.GA19849@gmail.com \
--to=mingo@kernel.org \
--cc=andi@firstfloor.org \
--cc=bp@amd64.org \
--cc=hpa@zytor.com \
--cc=jinsong.liu@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).