From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
"Kani, Toshimitsu" <toshi.kani@hpe.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac
Date: Wed, 19 Jul 2017 17:57:18 +0200 [thread overview]
Message-ID: <20170719155718.GD16124@nazgul.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F6130D126@ORSMSX114.amr.corp.intel.com>
On Wed, Jul 19, 2017 at 03:14:32PM +0000, Luck, Tony wrote:
> Later when GHES gives you a NODE/CARD/MODULE) in an error record. You need
> to match these up. But SMBIOS only gave you two strings "Locator" and "Bank
> Locator" which have no defined syntax. You are at the mercy of the BIOS writer
> to put in something parseable.
Well, at some point it is only so much we can do, right?
I mean, if FW says it wants to do firmware-first and we go and adhere
to that, it should be expected that said FW vendor marks the silkscreen
labels and DMI data accordingly.
I mean, it is time for FW to put its money where its mouth is, no?
How else would you do this?
Firmware First but the kernel does the figuring out which DIMMs are
where. So FW can't have the cake and eat it too.
:-)
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2017-07-19 15:57 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 21:59 [PATCH 0/3] enable ghes_edac on selected platforms Toshi Kani
2017-07-17 21:59 ` [PATCH 1/3] ACPI / blacklist: add acpi_match_oemlist() interface Toshi Kani
2017-07-18 5:34 ` Borislav Petkov
2017-07-18 15:48 ` Kani, Toshimitsu
2017-07-18 16:43 ` Borislav Petkov
2017-07-18 17:24 ` Kani, Toshimitsu
2017-07-18 17:42 ` Borislav Petkov
2017-07-18 18:49 ` Kani, Toshimitsu
2017-07-18 19:32 ` Borislav Petkov
2017-07-18 20:17 ` Kani, Toshimitsu
2017-07-17 21:59 ` [PATCH 2/3] intel_pstate: convert to use acpi_match_oemlist() Toshi Kani
2017-07-17 21:59 ` [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac Toshi Kani
2017-07-18 6:00 ` Borislav Petkov
2017-07-18 8:08 ` Borislav Petkov
2017-07-18 21:20 ` Kani, Toshimitsu
2017-07-19 5:52 ` Borislav Petkov
2017-07-19 16:10 ` Kani, Toshimitsu
2017-07-19 16:22 ` Borislav Petkov
2017-07-19 16:56 ` Kani, Toshimitsu
2017-07-20 4:16 ` Borislav Petkov
2017-07-20 14:42 ` Kani, Toshimitsu
2017-07-20 15:04 ` Borislav Petkov
2017-07-20 16:55 ` Luck, Tony
2017-07-20 17:05 ` Borislav Petkov
2017-07-20 17:10 ` Luck, Tony
2017-07-20 18:16 ` Mauro Carvalho Chehab
2017-07-19 18:55 ` Aristeu Rozanski
2017-07-19 20:13 ` Kani, Toshimitsu
2017-07-20 4:19 ` Borislav Petkov
2017-07-18 19:58 ` Kani, Toshimitsu
2017-07-18 21:15 ` Mauro Carvalho Chehab
2017-07-19 5:58 ` Borislav Petkov
2017-07-19 15:14 ` Luck, Tony
2017-07-19 15:57 ` Borislav Petkov [this message]
2017-07-19 18:06 ` Luck, Tony
2017-07-19 16:02 ` Mauro Carvalho Chehab
2017-07-19 20:06 ` Luck, Tony
2017-07-20 21:15 ` Luck, Tony
2017-07-21 0:00 ` Mauro Carvalho Chehab
2017-07-21 16:53 ` Luck, Tony
2017-07-19 16:40 ` Kani, Toshimitsu
2017-07-20 4:33 ` Borislav Petkov
2017-07-20 19:50 ` Kani, Toshimitsu
2017-07-20 20:15 ` Mauro Carvalho Chehab
2017-07-20 21:07 ` Kani, Toshimitsu
2017-07-21 13:34 ` Borislav Petkov
2017-07-21 13:40 ` Mauro Carvalho Chehab
2017-07-21 13:47 ` Borislav Petkov
2017-07-21 15:08 ` Kani, Toshimitsu
2017-07-21 15:13 ` Borislav Petkov
2017-07-21 15:34 ` Kani, Toshimitsu
2017-07-21 15:44 ` Mauro Carvalho Chehab
2017-07-21 16:40 ` Kani, Toshimitsu
2017-07-21 17:01 ` Mauro Carvalho Chehab
2017-07-21 17:21 ` Kani, Toshimitsu
2017-07-21 17:23 ` Borislav Petkov
2017-07-21 18:38 ` Kani, Toshimitsu
2017-07-22 6:28 ` Borislav Petkov
2017-07-24 14:49 ` Kani, Toshimitsu
2017-07-24 15:04 ` Borislav Petkov
2017-07-24 15:25 ` Kani, Toshimitsu
2017-07-24 15:37 ` Borislav Petkov
2017-07-24 15:56 ` Kani, Toshimitsu
2017-07-24 16:37 ` Borislav Petkov
2017-07-24 17:44 ` Kani, Toshimitsu
2017-07-24 17:50 ` Boris Petkov
2017-07-24 17:54 ` Kani, Toshimitsu
2017-07-24 18:18 ` Borislav Petkov
2017-07-24 17:56 ` Mauro Carvalho Chehab
2017-07-24 18:12 ` Kani, Toshimitsu
2017-07-24 16:04 ` Mauro Carvalho Chehab
2017-07-24 16:44 ` Borislav Petkov
2017-07-24 18:10 ` Mauro Carvalho Chehab
2017-07-24 18:30 ` Borislav Petkov
2017-07-25 23:00 ` Kani, Toshimitsu
2017-07-21 15:53 ` Borislav Petkov
2017-07-21 16:32 ` Kani, Toshimitsu
2017-07-19 5:55 ` Borislav Petkov
2017-07-18 22:13 ` Luck, Tony
2017-07-19 6:01 ` Borislav Petkov
2017-07-18 14:39 ` Jeffrey Hugo
2017-07-18 15:36 ` Kani, Toshimitsu
2017-07-18 16:24 ` Jeffrey Hugo
2017-07-18 16:42 ` Kani, Toshimitsu
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=20170719155718.GD16124@nazgul.tnic \
--to=bp@alien8.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=toshi.kani@hpe.com \
/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