From: Borislav Petkov <bp@amd64.org>
To: EDAC devel <linux-edac@vger.kernel.org>
Cc: Tony Luck <tony.luck@intel.com>, Ingo Molnar <mingo@elte.hu>,
X86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: [RFC -v2] x86 RAS: Reorganize functionality
Date: Wed, 19 Oct 2011 16:50:57 +0200 [thread overview]
Message-ID: <1319035866-29570-1-git-send-email-bp@amd64.org> (raw)
From: Borislav Petkov <borislav.petkov@amd.com>
Hi all,
this is the second version of a first attempt at reorganizing and
concentrating x86 RAS features under arch/x86/. The idea is to put them
close to the MCA code so that code reuse and extending functionality can
be done much more easily.
This deals only with AMD RAS features but I expect that we can put
all into one unified menu entry in Kconfig after we've agreed on the
structure. Tony, let me know what from below makes sense or not - once
we've agreed on the hierarchy, we should move the Intel pieces there
too. Right now with this patchset we have:
[*] Machine Check / overheating reporting
[ ] Intel MCE features
AMD RAS features --->
[*] Error Thresholding (NEW)
<*> Decode MCEs in human-readable form (NEW)
< > Inject MCEs (NEW)
and what I actually would like to see is something like
[ ] Reliability, Availability, Serviceability
[ ] Machine Check Architecture
[ ] Intel-specific features
[ ] CMCI / overheating reporting
[ ] MCE decoding
[ ] MCE injection
[ ] AMD-specific features
[ ] Error thresholding
[ ] MCE decoding
[ ] MCE injection
[ ] ...
and where further features will be added. How does that sound?
Patches 5-9 add the hw MCE injection for AMD which is contingent on the
MCE injection module.
As always, all comments are welcome.
Thanks.
next reply other threads:[~2011-10-19 14:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 14:50 Borislav Petkov [this message]
2011-10-19 14:50 ` [PATCH 1/9] x86, mce: Enable MCA support by default Borislav Petkov
2011-10-19 14:50 ` [PATCH 2/9] x86, RAS: Start reorganizing RAS features support Borislav Petkov
2011-10-19 17:13 ` Luck, Tony
2011-10-19 17:22 ` Mauro Carvalho Chehab
2011-10-19 18:11 ` Borislav Petkov
2011-10-19 19:14 ` Mauro Carvalho Chehab
2011-10-20 15:12 ` Borislav Petkov
2011-10-19 14:51 ` [PATCH 3/9] x86, RAS: Move MCE decoding code into ras/ Borislav Petkov
2011-10-19 14:51 ` [PATCH 4/9] x86, RAS: Move MCE injection " Borislav Petkov
2011-10-19 14:51 ` [PATCH 5/9] x86, MCE: Add a HW injection flag Borislav Petkov
2011-10-19 14:51 ` [PATCH 6/9] x86, RAS: Convert mce-inject module to debugfs Borislav Petkov
2011-10-19 14:51 ` [PATCH 7/9] x86, RAS: Add function enabling direct writes to MCE MSRs Borislav Petkov
2011-10-19 14:51 ` [PATCH 8/9] x86, RAS: Add attributes needed for HW injection Borislav Petkov
2011-10-19 21:03 ` David Rientjes
2011-10-19 21:09 ` Borislav Petkov
2011-10-19 21:19 ` David Rientjes
2011-10-20 15:06 ` Borislav Petkov
2011-10-19 14:51 ` [PATCH 9/9] x86, RAS: Add an injector function Borislav Petkov
2011-10-19 17:08 ` [RFC -v2] x86 RAS: Reorganize functionality Luck, Tony
2011-10-19 17:13 ` 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=1319035866-29570-1-git-send-email-bp@amd64.org \
--to=bp@amd64.org \
--cc=borislav.petkov@amd.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.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 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).