All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	ak@linux.intel.com, bp@amd64.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
	ananth@in.ibm.com
Subject: Re: [PATCH] [mcelog] Start using the new sysfs tunables location
Date: Thu, 06 Sep 2012 12:10:17 +0530	[thread overview]
Message-ID: <50484551.8080700@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+8MBbKx7x=MxgtV5URYuDWQcxz0nqohVB8gRpBHtDxqMBb9uw@mail.gmail.com>

On 09/06/2012 12:39 AM, Tony Luck wrote:
> On Wed, Sep 5, 2012 at 11:47 AM, Andi Kleen <andi@firstfloor.org> wrote:
>> On Wed, Sep 05, 2012 at 04:02:37PM +0530, Naveen N. Rao wrote:
>>> All the current mce tunables are now available under
>>> /sys/devices/system/machinecheck. Start using this new location, but fall back
>>> to the older per-cpu location so that we continue working with older kernels.
>>
>> Who did that change in the kernel?
>>
>> That breaks Linus rule that the kernel should not break userland.
>> Kernel needs to fix that.
>
> The change is still under discussion. Stage one is to add the new global
> pathnames in addition to keeping the old per-cpu ones. Also fix all utilities
> (just mcelog(8) as far as we know) to prefer the new paths.
>
> After some time[1] ... delete the old paths. This is allowable under Linus'
> modified edict that you can change ABI "if nobody complains". If we wait
> long enough that the new mcelog is widely deployed, then nobody should
> complain.
>
> -Tony
>
> [1] several years - not just a kernel release or two.
>

Tony,
Thanks for clarifying. I should have mentioned in the patch description 
that this is indeed subject to the original patch making it into the kernel.

On a related topic. I recently noticed that we don't have an entry for 
machinecheck in Documentation/ABI/. Should we add an entry in there? We 
could perhaps add the existing entries under obsolete/ and the new 
location under testing/?


- Naveen


  reply	other threads:[~2012-09-06  6:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 10:21 [PATCH 0/3] x86:mce: Some cleanups and bios-set CMCI thresholds Naveen N. Rao
2012-09-05 10:21 ` [PATCH 1/3] x86/mce: Make sysfs tunables available globally across all cpus Naveen N. Rao
2012-09-05 10:32   ` [PATCH] [mcelog] Start using the new sysfs tunables location Naveen N. Rao
2012-09-05 18:47     ` Andi Kleen
2012-09-05 19:09       ` Tony Luck
2012-09-06  6:40         ` Naveen N. Rao [this message]
2012-09-06 12:28         ` Andi Kleen
2012-09-06 12:34           ` Naveen N. Rao
2012-09-06 12:51             ` Alan Cox
2012-09-06 13:21             ` Andi Kleen
2012-09-05 10:22 ` [PATCH 2/3] x86/mce: Pack boolean MCE flags into a structure Naveen N. Rao
2012-09-05 17:15   ` Joe Perches
2012-09-05 18:56   ` Tony Luck
2012-09-06  6:48     ` Naveen N. Rao
2012-09-06 12:15       ` Borislav Petkov
2012-09-05 10:22 ` [PATCH 3/3] x86/mce: Honour bios-set CMCI threshold Naveen N. Rao

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=50484551.8080700@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ak@linux.intel.com \
    --cc=ananth@in.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=bp@amd64.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@gmail.com \
    --cc=x86@kernel.org \
    /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.