From: Borislav Petkov <bp@amd64.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: tony.luck@intel.com, andi@firstfloor.org,
gong.chen@linux.intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, linux-edac@vger.kernel.org,
ananth@in.ibm.com, Chris McDermott <lcm@us.ibm.com>,
masbock@linux.vnet.ibm.com
Subject: Re: [PATCH] x86: mce: Honour bios-set CMCI threshold
Date: Mon, 27 Aug 2012 11:12:35 +0200 [thread overview]
Message-ID: <20120827091235.GB26602@aftab.osrc.amd.com> (raw)
In-Reply-To: <50361A59.2020308@linux.vnet.ibm.com>
On Thu, Aug 23, 2012 at 05:26:09PM +0530, Naveen N. Rao wrote:
> Sure - sounds like a good idea. Further, a #define could eliminate
> the need to change other references, but I'm not sure that's
> GENERALLacceptable
>
> #define mce_bios_cmci_threshold boot_flags.mce_bios_cmci_threshold
>
> could eliminate the need to change other references, but I'm not sure
> that's acceptable
Yeah, that's kinda obfuscating it for no reason. As I said before, we
can always add it later if it makes sense.
> But, I just had a quick look and it seems to me that these were
> defined as integers since they are exposed via sysfs. For instance:
>
> static struct dev_ext_attribute dev_attr_cmci_disabled = {
> __ATTR(cmci_disabled, 0644, device_show_int, set_cmci_disabled),
> &mce_cmci_disabled
> };
>
> Converting mce_cmci_disabled to a bit-field doesn't work since we
> take its address above. We could ignore and not set the second field
> at all (dev_ext_attribute->var) and define our own callbacks, but
> that'll be more work and I'm not sure if we work fine without
Right,
but take a look at set_cmci_disabled(): it converts the newly read value
to bool anyway:
if (mce_cmci_disabled ^ !!new) {
so we can do later
flags.mce_cmci_disabled = true;
or
flags.mce_cmci_disabled = false;
instead of assigning 0 or 1 to it.
And, about showing it with device_show_int, a simple test works:
---
#include <stdio.h>
#include <stdbool.h>
int main()
{
bool a = true;
printf("%d\n", a);
return 0;
}
--
but even if there are troubles with that, we can change device_show_int
to a locally defined function.
But, anyway, long story short: I wasn't suggesting you go and change all
of them - simply start by adding your flag mce_bios_cmci_threshold to a
struct <something>_flags and I'll take care of the rest.
Unless you really want to do it, of course :-)
Oh, and the more important thing is, Tony would need to review your
Intel-specific changes so pls keep him CCed on your next iteration too.
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
next prev parent reply other threads:[~2012-08-27 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 12:30 Naveen N. Rao
2012-08-22 12:46 ` Borislav Petkov
2012-08-23 11:56 ` Naveen N. Rao
2012-08-27 9:12 ` Borislav Petkov [this message]
2012-08-27 9:54 ` Naveen N. Rao
2012-08-23 12:08 ` Naveen N. Rao
2012-08-23 12:29 ` 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=20120827091235.GB26602@aftab.osrc.amd.com \
--to=bp@amd64.org \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=gong.chen@linux.intel.com \
--cc=lcm@us.ibm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masbock@linux.vnet.ibm.com \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--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