From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tyler Baicar <tbaicar@codeaurora.org>,
matt@codeblueprint.co.uk, ard.biesheuvel@linaro.org,
will.deacon@arm.com, james.morse@arm.com,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efi: parse ARM error information value
Date: Tue, 17 Oct 2017 22:30:13 +0300 [thread overview]
Message-ID: <1508268613.16112.487.camel@linux.intel.com> (raw)
In-Reply-To: <1508260992-18014-1-git-send-email-tbaicar@codeaurora.org>
On Tue, 2017-10-17 at 11:23 -0600, Tyler Baicar wrote:
> ARM errors just print out the error information value, then the
> value needs to be manually decoded as per the UEFI spec. Add
> decoding of the ARM error information value so that the kernel
> logs capture all of the valid information at first glance.
>
> ARM error information value decoding is captured in UEFI 2.7
> spec tables 263-265.
Could it be located in separate file?
> + printk("%stransaction type: %s\n", pfx,
> + arm_err_trans_type_strs[trans_type]);
Plain printk():s?
> +#define CPER_ARM_ERR_VALID_TRANSACTION_TYPE 0x0001
> +#define CPER_ARM_ERR_VALID_OPERATION_TYPE 0x0002
> +#define CPER_ARM_ERR_VALID_LEVEL 0x0004
> +#define CPER_ARM_ERR_VALID_PROC_CONTEXT_CORRUPT 0x0008
> +#define CPER_ARM_ERR_VALID_CORRECTED 0x0010
> +#define CPER_ARM_ERR_VALID_PRECISE_PC 0x0020
> +#define CPER_ARM_ERR_VALID_RESTARTABLE_PC 0x0040
> +#define CPER_ARM_ERR_VALID_PARTICIPATION_TYPE 0x0080
> +#define CPER_ARM_ERR_VALID_TIME_OUT 0x0100
> +#define CPER_ARM_ERR_VALID_ADDRESS_SPACE 0x0200
> +#define CPER_ARM_ERR_VALID_MEM_ATTRIBUTES 0x0400
> +#define CPER_ARM_ERR_VALID_ACCESS_MODE 0x0800
BIT() is already being used in this file.
> +
> +#define CPER_ARM_ERR_TRANSACTION_SHIFT 16
> +#define CPER_ARM_ERR_TRANSACTION_MASK 0x3
Mask is mask, so GENMASK()
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-10-17 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 17:23 [PATCH] efi: parse ARM error information value Tyler Baicar
2017-10-17 19:30 ` Andy Shevchenko [this message]
2017-10-18 13:54 ` Tyler Baicar
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=1508268613.16112.487.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=james.morse@arm.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=tbaicar@codeaurora.org \
--cc=will.deacon@arm.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