From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: [2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents
Date: Mon, 26 Mar 2018 22:09:55 +0200 [thread overview]
Message-ID: <20180326200955.GG28372@pd.tnic> (raw)
On Mon, Mar 26, 2018 at 08:05:37PM +0000, Ghannam, Yazen wrote:
> Sure, I can do that. But I didn't think it was necessary because it doesn't hurt
> to read the registers whether or not the valid bits are set.
No, this needs to be AMD-specific because it will confuse people using
Intel machines.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH 2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents
Date: Mon, 26 Mar 2018 22:09:55 +0200 [thread overview]
Message-ID: <20180326200955.GG28372@pd.tnic> (raw)
In-Reply-To: <DM5PR12MB1916CB8536B257923AC76CA7F8AD0@DM5PR12MB1916.namprd12.prod.outlook.com>
On Mon, Mar 26, 2018 at 08:05:37PM +0000, Ghannam, Yazen wrote:
> Sure, I can do that. But I didn't think it was necessary because it doesn't hurt
> to read the registers whether or not the valid bits are set.
No, this needs to be AMD-specific because it will confuse people using
Intel machines.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next reply other threads:[~2018-03-26 20:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 20:09 Borislav Petkov [this message]
2018-03-26 20:09 ` [PATCH 2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2018-08-23 17:53 [1/2] Revert "x86/mce/AMD: Collect error info even if valid bits are not set" Yazen Ghannam
2018-08-23 17:53 ` [PATCH 1/2] " Ghannam, Yazen
2018-08-23 12:24 [1/2] " Borislav Petkov
2018-08-23 12:24 ` [PATCH 1/2] " Borislav Petkov
2018-03-27 15:59 [1/2] " Yazen Ghannam
2018-03-27 15:59 ` [PATCH 1/2] " Ghannam, Yazen
2018-03-27 14:07 [2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents Yazen Ghannam
2018-03-27 14:07 ` [PATCH 2/2] " Ghannam, Yazen
2018-03-27 14:02 [1/2] Revert "x86/mce/AMD: Collect error info even if valid bits are not set" Yazen Ghannam
2018-03-27 14:02 ` [PATCH 1/2] " Ghannam, Yazen
2018-03-26 20:27 [2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents Luck, Tony
2018-03-26 20:27 ` [PATCH 2/2] " Luck, Tony
2018-03-26 20:07 [1/2] Revert "x86/mce/AMD: Collect error info even if valid bits are not set" Borislav Petkov
2018-03-26 20:07 ` [PATCH 1/2] " Borislav Petkov
2018-03-26 20:05 [2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents Yazen Ghannam
2018-03-26 20:05 ` [PATCH 2/2] " Ghannam, Yazen
2018-03-26 19:58 [1/2] Revert "x86/mce/AMD: Collect error info even if valid bits are not set" Yazen Ghannam
2018-03-26 19:58 ` [PATCH 1/2] " Ghannam, Yazen
2018-03-26 19:35 [2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents Borislav Petkov
2018-03-26 19:35 ` [PATCH 2/2] " Borislav Petkov
2018-03-26 19:30 [1/2] Revert "x86/mce/AMD: Collect error info even if valid bits are not set" Borislav Petkov
2018-03-26 19:30 ` [PATCH 1/2] " Borislav Petkov
2018-03-26 19:15 [2/2] x86/MCE: Always save MCA_{ADDR,MISC,SYND} register contents Yazen Ghannam
2018-03-26 19:15 ` [PATCH 2/2] " Yazen Ghannam
2018-03-26 19:15 [1/2] Revert "x86/mce/AMD: Collect error info even if valid bits are not set" Yazen Ghannam
2018-03-26 19:15 ` [PATCH 1/2] " Yazen Ghannam
2018-03-28 18:39 ` [tip:ras/core] " tip-bot for Yazen Ghannam
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=20180326200955.GG28372@pd.tnic \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--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 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.