public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Joey Gouly" <joey.gouly@arm.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
	"leif@nuviainc.com" <leif@nuviainc.com>,
	Sami Mujawar <Sami.Mujawar@arm.com>, nd <nd@arm.com>
Subject: Re: [PATCH v2 1/1] ShellPkg: Validate that the Boot CPU is present in MADT
Date: Tue, 9 Mar 2021 15:47:40 +0000	[thread overview]
Message-ID: <DB8PR08MB5433789E8D3FD980A7E7A03194929@DB8PR08MB5433.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20210115144340.6511-1-joey.gouly@arm.com>

> From: Joey Gouly <joey.gouly@arm.com>
> Subject: [PATCH v2 1/1] ShellPkg: Validate that the Boot CPU is present in MADT
>
> The ACPI 6.3 Specification, January 2019, section 5.2.12.14 states that
> the firmware must convey each processor’s GIC information to the OS using
> the GICC structure.
>
> If a GICC structure for the boot CPU is missing some standards-based
> operating system may crash with an error code. It may be difficult to
> diagnose the reason for the crash as the error code may be too generic
> and mean firmware error.
>
> Therefore add validation to the MADT table parser to check that a GICC is
> present for the boot CPU.

Ping.

Is anyone able to review this patch adding some more validation checks to Acpiview / MADT?

Thanks,
Joey

  reply	other threads:[~2021-03-09 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 14:43 [PATCH v2 1/1] ShellPkg: Validate that the Boot CPU is present in MADT Joey Gouly
2021-03-09 15:47 ` Joey Gouly [this message]
2021-03-10  1:32 ` [edk2-devel] " Ni, Ray
2021-03-10 15:25   ` Joey Gouly

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-list 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=DB8PR08MB5433789E8D3FD980A7E7A03194929@DB8PR08MB5433.eurprd08.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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