From: Punit Agrawal <punit.agrawal@arm.com>
To: "Luck\, Tony" <tony.luck@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Boris Petkov <bp@suse.de>,
Tyler Baicar <tbaicar@codeaurora.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI/APEI: Add BERT data driver
Date: Tue, 15 Aug 2017 11:22:06 +0100 [thread overview]
Message-ID: <87k225p1v5.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <20170814165613.25561-1-tony.luck@intel.com> (Tony Luck's message of "Mon, 14 Aug 2017 09:56:13 -0700")
Hi Tony,
"Luck, Tony" <tony.luck@intel.com> writes:
> From: Tony Luck <tony.luck@intel.com>
>
> The ACPI Boot Error Record Table provides a method for platform
> firmware to give information to the operating system about error
> that occurred prior to boot (of particular interest are problems
> that caused the previous OS instance to crash).
>
> The BERT table simply provides the size and address of the error
> record in BIOS reserved memory. In an earlier age we might have
> used /dev/mem to retrieve this error record, but many systems
> disable /dev/mem for security reasons.
>
> This driver provides read-only access to the data via a character
> special device "/dev/bert-data".
There is already a bert driver which prints the error record. Would it
make sense to integrate the character device there instead of creating a
new driver?
[...]
next prev parent reply other threads:[~2017-08-15 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 16:56 [PATCH] ACPI/APEI: Add BERT data driver Luck, Tony
2017-08-15 10:22 ` Punit Agrawal [this message]
2017-08-15 21:15 ` Luck, Tony
2017-08-16 13:14 ` Punit Agrawal
2017-08-16 15:22 ` Luck, Tony
2017-08-17 10:25 ` Punit Agrawal
2017-08-17 17:49 ` Luck, Tony
2017-08-17 19:28 ` Rafael J. Wysocki
2017-08-17 20:29 ` Luck, Tony
2017-08-17 20:41 ` Rafael J. Wysocki
2017-08-17 21:39 ` [PATCH] ACPI / sysfs: Extend ACPI sysfs to provide access to boot error region Luck, Tony
2017-08-18 0:30 ` Alan Cox
2017-08-18 2:12 ` Luck, Tony
2017-08-23 14:56 ` Luck, Tony
2017-08-29 0:10 ` Kees Cook
2017-08-29 15:55 ` Luck, Tony
2017-08-18 17:38 ` Punit Agrawal
2017-08-18 23:19 ` [PATCH v4] " Luck, Tony
2017-08-28 20:55 ` Rafael J. Wysocki
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=87k225p1v5.fsf@e105922-lin.cambridge.arm.com \
--to=punit.agrawal@arm.com \
--cc=bp@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tbaicar@codeaurora.org \
--cc=tony.luck@intel.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