From: Avadhut Naik <avadnaik@amd.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"bp@alien8.de" <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yazen.ghannam@amd.com" <yazen.ghannam@amd.com>,
Avadhut Naik <avadhut.naik@amd.com>
Subject: [RESEND v2] ACPI: APEI: Skip initialization of GHES_ASSIST structures for Machine Check Architecture
Date: Thu, 30 Nov 2023 14:31:02 -0600 [thread overview]
Message-ID: <b58c799c-8d3f-4fd8-9ddb-ebb06ef005d5@amd.com> (raw)
In-Reply-To: <SJ1PR11MB60839D04A329087D11933B6CFC82A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Hi,
On 11/30/2023 14:03, Luck, Tony wrote:
>> Actually, caching of values from an earlier structure to be compared against values
>> in a later structure is what we intend to do here i.e. comparing cached source_id
>> from an earlier structure with related_source_id in a later structure. To hint
>> towards the same, I had added the below comment on top of the static structure's
>> declaration:
>>
>>>>> + * Since GHES_ASSIST is not supported, skip initialization
>>>>> + * of GHES_ASSIST structures for MCA.
>>>>> + * During HEST parsing, detected MCA error sources are cached.
>>>>> + * Flags and Source Id fields from these cached values are
>>>>> + * then referred to determine if the encountered GHES_ASSIST
>>>>> + * structure should be initialized.
>>>>> + */
>>
>> Is this not good enough? Should I make it more explicit?
>
> I understand now, but missed that the caching and use are across
> different entries in the HEST table.
>
> Maybe something like this:
>
> * Since GHES_ASSIST is not supported, skip initialization of GHES_ASSIST
> * structures for MCA. During HEST parsing, detected MCA error sources
> * are cached from early table entries so that Flags and Source Id
> * fields from these cached values are then referred to in later table
> * entries to determine if the encountered GHES_ASSIST structure should
> * be initialized.
>
Sounds good! Thank you for this. Will update accordingly and resubmit.
> -Tony
--
Thanks,
Avadhut Naik
prev parent reply other threads:[~2023-11-30 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 20:13 [RESEND v2] ACPI: APEI: Skip initialization of GHES_ASSIST structures for Machine Check Architecture Avadhut Naik
2023-11-06 20:42 ` Luck, Tony
2023-11-06 23:47 ` Avadhut Naik
2023-11-29 18:29 ` Avadhut Naik
2023-11-29 18:52 ` Tony Luck
2023-11-30 18:03 ` Avadhut Naik
2023-11-30 20:03 ` Luck, Tony
2023-11-30 20:31 ` Avadhut Naik [this message]
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=b58c799c-8d3f-4fd8-9ddb-ebb06ef005d5@amd.com \
--to=avadnaik@amd.com \
--cc=avadhut.naik@amd.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=yazen.ghannam@amd.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