From: Borislav Petkov <bp@amd64.org>
To: Greg KH <greg@kroah.com>
Cc: Borislav Petkov <bp@amd64.org>,
EDAC devel <linux-edac@vger.kernel.org>, X86-ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] EDAC, MCE, AMD: Add hw_inject and cpu sysfs attrs
Date: Sun, 8 May 2011 21:43:16 +0200 [thread overview]
Message-ID: <20110508194316.GA1070@aftab> (raw)
In-Reply-To: <20110508191853.GA10273@kroah.com>
On Sun, May 08, 2011 at 03:18:53PM -0400, Greg KH wrote:
> > > You forgot to add the proper Documentation/ABI/ files for these new
> > > sysfs files. Please do that.
> >
> > Yeah, so those sprang up as a testing module and the final goal is to
> > have all injection done through perf events but it could also be prudent
> > to keep those as a fallback alternative.
> >
> > I'm thinking something like
> > Documentation/ABI/testing/sysfs-devices-system-edac but looking
> > at Documentation/ABI/README and reading the "testing/" category
> > description, I don't think it applies to those interfaces just yet for
> > the simple reason that they're still changing and I wouldn't want to
> > cast them in stone now.
> >
> > Can we add them to a "unstable" category instead or maybe delay making
> > the ABI description for now?
>
> No. If you add sysfs files to the kernel, you had better be sure that
> they are correct and are what you want to be doing. Otherwise, don't
> add them.
I cannot be sure right now because this whole RAS thing is being
developed now and we're more or less learning by doing. I don't think
anyone can tell you what we're going to need a year from now on
interfaces for error injection.
> As you really want to do this through perf, just do it through perf.
> Please don't create a user/kernel api that you are not going to want
> to use in the end.
As I said above, it is going to be used as a fallback alternative to the
perf option for systems which cannot do perf. This injection method will
be the fallback.
Also, this whole module is default-N in Kconfig and you have to really
know what you're doing when enabling it.
Which brings me to a much better idea: this whole interface should
actually go to debugfs! This is more or less a debugging module, so
debugfs, doh!
/me slaps himself on the forehead and goes to rework the patches.
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-05-08 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 16:49 [PATCH 0/4] x86, MCE, AMD: Hardware MCE injection Borislav Petkov
2011-05-05 16:49 ` [PATCH 1/4] x86, MCE: Add a HW injection flag Borislav Petkov
2011-05-05 16:49 ` [PATCH 2/4] EDAC, MCE, AMD: Add function to enable direct write to MCE MSRs Borislav Petkov
2011-05-05 16:49 ` [PATCH 3/4] EDAC, MCE, AMD: Add hw_inject and cpu sysfs attrs Borislav Petkov
2011-05-08 16:40 ` Greg KH
2011-05-08 18:49 ` Borislav Petkov
2011-05-08 19:18 ` Greg KH
2011-05-08 19:43 ` Borislav Petkov [this message]
2011-05-05 16:49 ` [PATCH 4/4] EDAC, MCE, AMD: Add an injector function Borislav Petkov
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=20110508194316.GA1070@aftab \
--to=bp@amd64.org \
--cc=greg@kroah.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.