From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Decode information from ESR upon mem faults
Date: Tue, 11 Jul 2017 18:57:58 +0100 [thread overview]
Message-ID: <20170711175757.GG13977@arm.com> (raw)
In-Reply-To: <42862eff-5e90-31c7-46d7-0270d4ac8e08@arm.com>
On Thu, Jun 29, 2017 at 09:58:12AM +0100, Julien Thierry wrote:
> As you mentioned, this is similar to the register dump and now that I look
> at it, registers are more grouped (2-3 per line). Maybe we could keep the
> debug info on multiple lines but grouping a bit more instead of having 1
> field per line:
>
> [ 122.109118] Mem abort info:
> [ 122.111884] Exception class = DABT (current EL), IL = 32 bits, SET = 0
> [ 122.121507] FnV = 0, EA = 0, S1PTW = 0
> [ 122.128347] Data abort info:
> [ 122.131212] ISS[23:14] invalid
> [ 122.134417] CM = 0, WnR = 1
>
> When ISS is not invalid, it's fields could be printed on the same line.
I'd rather keep the same print structure, regardless of whether or not the
ISS is known or not (and also why I'd like to print the hex value when it's
invalid).
> I think it would keep the code simple and the debug info readable. There
> would be less lines to interleave although that issue would not be
> completely solved.
Sounds good to me.
> Otherwise, maybe we could prefix the lines with a cpu id in order to be able
> to distinguish interleaved debug infos? But that could be done as well for
> the register dumps if this is necessary.
I wouldn't bother with the CPU number.
Will
prev parent reply other threads:[~2017-07-11 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:14 [PATCH] arm64: Decode information from ESR upon mem faults Julien Thierry
2017-06-19 17:13 ` Will Deacon
2017-06-29 8:58 ` Julien Thierry
2017-07-11 17:57 ` Will Deacon [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=20170711175757.GG13977@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).