mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Tony Luck <tony.luck@intel.com>
Cc: EDAC devel <linux-edac@vger.kernel.org>, X86-ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] x86, RAS: Add a barebones RAS subtree
Date: Tue, 9 Oct 2012 15:20:42 +0200	[thread overview]
Message-ID: <20121009132042.GD26450@aftab.osrc.amd.com> (raw)
In-Reply-To: <CA+8MBb+LgCSmV_J-ZeRXuBF_F3qPvUzkvYCC9vo7mugGDNSG7Q@mail.gmail.com>

On Mon, Oct 08, 2012 at 04:53:46PM -0700, Tony Luck wrote:
> On Mon, Oct 8, 2012 at 10:11 AM, Borislav Petkov <bp@amd64.org> wrote:
> > +config X86_RAS
> > +       def_bool y
> > +       prompt "X86 RAS features"
> > +       ---help---
> > +       A collection of Reliability, Availability and Serviceability software
> > +       features which enable hardware error logging and reporting. Leave it
> > +       at 'y' unless you really know what you're doing.
> > +
> 
> The intent of "X86_RAS" is just to show/hide all the menu
> options for the individual features - which will all use
>           depends on X86_RAS
> right? Having this set to "y" doesn't actually enable any of
> the features - they all have their own CONFIG_* variables.
> 
> Perhaps we could make that clearer in the help text? And
> ditch the "Leave it at 'y' ... ", I don't think it helps anyone.

Good point. I've changed it to a simple bool which opens a submenu when
enabled (diff ontop):

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 85f666390b5e..d39c2fc20a81 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -688,12 +688,10 @@ config X86_CYCLONE_TIMER
        depends on X86_SUMMIT
 
 config X86_RAS
-       def_bool y
-       prompt "X86 RAS features"
+       bool "X86 RAS features"
        ---help---
        A collection of Reliability, Availability and Serviceability software
-       features which enable hardware error logging and reporting. Leave it
-       at 'y' unless you really know what you're doing.
+       features which enable hardware error logging and reporting.

The def_bool y intent was from earlier but it materialized in a patch
which I sent last week or so which makes CONFIG_X86_MCE enabled by
default so no need to enable those additional RAS stuff by default.

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

  reply	other threads:[~2012-10-09 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 17:11 [PATCH 0/6] AMD MCE injection improvs Borislav Petkov
2012-10-08 17:11 ` [PATCH 1/6] x86, RAS: Add a barebones RAS subtree Borislav Petkov
2012-10-08 23:53   ` Tony Luck
2012-10-09 13:20     ` Borislav Petkov [this message]
2012-10-08 17:11 ` [PATCH 2/6] x86, RAS: Move AMD MCE injection code into ras/ Borislav Petkov
2012-10-08 17:11 ` [PATCH 3/6] x86, RAS: Convert mce-inject module to debugfs Borislav Petkov
2012-10-08 17:11 ` [PATCH 4/6] x86, RAS: Add function enabling direct writes to MCE MSRs Borislav Petkov
2012-10-08 17:11 ` [PATCH 5/6] x86, RAS: Add attributes needed for HW injection Borislav Petkov
2012-10-08 17:11 ` [PATCH 6/6] x86, RAS: Add an injector function Borislav Petkov
2012-10-08 23:58 ` [PATCH 0/6] AMD MCE injection improvs Tony Luck
2012-10-09  6:18   ` 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=20121009132042.GD26450@aftab.osrc.amd.com \
    --to=bp@amd64.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome