tree 21ce1a75949de05e0803fe18c6e127a2ea25ed88
parent bc7af854d7e14472e27c2baf0c4ccbdb83d41ae5
author Marco Nelissen <marcone@google.com> 1611176601 -0800
committer Marco Nelissen <marcone@google.com> 1611251204 -0800

[arch][arm64] Fix and improve fault logging

The fault code (bits 5:0 of ESR) was only printed if ISV was set,
however ISV indicates whether the instruction syndrome (bits 23:14)
is valid.
Parse and print fault code for data and instruction faults.
Parse and print instruction syndrome when ISV is set.
For data faults say whather the error occurred reading or writing.
Use more descriptive naming for "FAR" and "DFSC".
Don't print ISS twice.
Shift IL value so it's printed as 0x0 or 0x1, not 0x2000000.

Example before:

secure os: data fault: PC at 0x1edb87901778(0x19778), FAR 0x0, iss 0x44
secure os: load bias: 0x1edb878e8000
secure os: ESR 0x92000044: ec 0x24, il 0x2000000, iss 0x44

after:

secure os: data fault writing to 0x0, PC at 0x1edb87901778(0x19778)
secure os: fault code 0x4: Translation fault, level 0
secure os: load bias: 0x1edb878e8000
secure os: ESR 0x92000044: ec 0x24, il 0x1, iss 0x44

Change-Id: I4922328373e13443c999c2c79ea0ba2606417aeb