All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	"Liu, Jinsong" <jinsong.liu@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Borislav Petkov <bp@amd64.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 1/3] Add mcelog support for xen platform
Date: Mon, 23 Apr 2012 13:03:27 -0400	[thread overview]
Message-ID: <20120423170327.GC22364@phenom.dumpdata.com> (raw)
In-Reply-To: <4F958098.1050402@zytor.com>

On Mon, Apr 23, 2012 at 09:17:28AM -0700, H. Peter Anvin wrote:
> 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

I am _not_ claiming that. If I left you with that impression from my
responses - my fault for not getting my point across (the sleep deprevation
is probably not helping either).

I am _not_ stating that the usage of 'mce_log' or 'struct mce' MUST
remain the same from now on. No. I am saying that the driver will be
changed lock-step as Tony and Boris see fit in changing the functions.

And currently the way the existing MCE drivers do this - is by using
mce_log. This driver does is too - since the in-tree drivers do it this way.
When they change to use a different mechanism - this driver will as well.

> 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.

The ones I know that you are unhappy about are the MMU paravirt interfaces
and I did mention to you that once some prototype work is done and
it showed success, I will work on removing said support.

Why don't you send me your unhappy list so that is on my radar as well please?

> 
> 	-hpa
> 
> -- 
> H. Peter Anvin, Intel Open Source Technology Center
> I work for Intel.  I don't speak on their behalf.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-04-23 17:09 UTC|newest]

Thread overview: 27+ 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-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 [this message]
2012-04-23 17:16           ` H. Peter Anvin
2012-04-24  8:27     ` Andi Kleen
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=20120423170327.GC22364@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=jinsong.liu@intel.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 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.