linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Baicar, Tyler" <tbaicar@codeaurora.org>
To: "Luck, Tony" <tony.luck@intel.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>, Huang Ying <ying.huang@intel.com>,
	Borislav Petkov <bp@suse.de>,
	Tomasz Nowicki <tomasz.nowicki@linaro.org>,
	Jonathan Zhang <zjzhang@codeaurora.org>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3] ACPI / APEI: Boot Error Record Table processing was needlessly complicated
Date: Fri, 19 May 2017 15:39:29 -0600	[thread overview]
Message-ID: <276be033-dcbb-bff3-fa52-9a84a57a9d2e@codeaurora.org> (raw)
In-Reply-To: <20170516225806.5702-1-tony.luck@intel.com>

On 5/16/2017 4:58 PM, Luck, Tony wrote:
> From: Tony Luck <tony.luck@intel.com>
>
> Quoting version 6.1 of the ACPI specification. Section 18.3.1 "Boot
> Error Source" says:
>
>    The Boot Error Region is a range of addressable memory OSPM can access
>    during initialization to determine if an unhandled error condition
>    occurred. System firmware must report this memory range as firmware
>    reserved. The format of the Boot Error Region follow that of an Error
>    Status Block, this is defined in Section 18.3.2.7. The format of the
>    error status block is described by Table 18-342.
>
> This clarifies some points that were obfuscated in earlier versions.
> E.g. there is no longer a separate table to describe the format of the
> "Boot Error Region" (which was identical to the "Error Status Block").
> Also saying "follow that of *an* Error Status Block" makes it clear that
> there is just one block (which can still contain multiple "Generic Error
> Data Entry structures").
>
> The loop inside bert_print_all() is unnecessary (but probably harmless
> as the "while (remain > sizeof(struct acpi_bert_region))" loop should
> terminate after we skipped over the first entry.
>
> We can drop the "bert_print_all()" function and just move the four
> relevant lines inline in "bert_init()".
>
> Cc: Len Brown <lenb@kernel.org>
> Cc: Huang Ying <ying.huang@intel.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Tomasz Nowicki <tomasz.nowicki@linaro.org>
> Cc: Jonathan (Zhixiong) Zhang <zjzhang@codeaurora.org>
> Cc: Tyler Baicar <tbaicar@codeaurora.org>
> Cc: linux-acpi@vger.kernel.org
> Reviewed-by: Borislav Petkov <bp@suse.de>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
Tested-by: Tyler Baicar <tbaicar@codeaurora.org>

-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.


      reply	other threads:[~2017-05-19 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 18:10 [PATCH] ACPI / APEI: Boot Error Record Table processing was needlessly complicated Luck, Tony
2017-05-05 18:12 ` Luck, Tony
2017-05-05 19:52 ` Rafael J. Wysocki
2017-05-12 12:01 ` Borislav Petkov
2017-05-12 21:42   ` [PATCH v2 0/2] Clean up ACPI Boot Error Record Table code Luck, Tony
2017-05-12 21:42     ` [PATCH v2 1/2] ACPI / APEI: Boot Error Record Table processing was needlessly complicated Luck, Tony
2017-05-12 21:42     ` [PATCH v2 2/2] ACPI / APEI: No remaining users of struct acpi_bert_region Luck, Tony
2017-05-12 21:46       ` Rafael J. Wysocki
2017-05-12 22:32         ` Luck, Tony
2017-05-12 22:52           ` Rafael J. Wysocki
2017-05-16 22:12     ` [PATCH v2 0/2] Clean up ACPI Boot Error Record Table code Baicar, Tyler
2017-05-16 22:58       ` [PATCH v3] ACPI / APEI: Boot Error Record Table processing was needlessly complicated Luck, Tony
2017-05-19 21:39         ` Baicar, Tyler [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=276be033-dcbb-bff3-fa52-9a84a57a9d2e@codeaurora.org \
    --to=tbaicar@codeaurora.org \
    --cc=bp@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tomasz.nowicki@linaro.org \
    --cc=tony.luck@intel.com \
    --cc=ying.huang@intel.com \
    --cc=zjzhang@codeaurora.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;
as well as URLs for NNTP newsgroup(s).