diff options
| author | Mahesh Salgaonkar <mahesh@linux.ibm.com> | 2020-03-18 13:04:20 +0530 |
|---|---|---|
| committer | David Gibson <david@gibson.dropbear.id.au> | 2020-03-24 11:05:37 +1100 |
| commit | cb9fb64d0789a3ec47eb0d7549026e353e98b8c1 (patch) | |
| tree | 9c1ac37174912fd684cd24c7c43787ea65c66e05 /monitor | |
| parent | c532b954d96f96d361ca31308f75f1b95bd4df76 (diff) | |
| download | qemu-cb9fb64d0789a3ec47eb0d7549026e353e98b8c1.zip qemu-cb9fb64d0789a3ec47eb0d7549026e353e98b8c1.tar.gz qemu-cb9fb64d0789a3ec47eb0d7549026e353e98b8c1.tar.bz2 | |
ppc/spapr: Set the effective address provided flag in mc error log.
Per PAPR, it is expected to set effective address provided flag in
sub_err_type member of mc extended error log (i.e
rtas_event_log_v6_mc.sub_err_type). This somehow got missed in original
fwnmi-mce patch series. The current code just updates the effective address
but does not set the flag to indicate that it is available. Hence guest
fails to extract effective address from mce rtas log. This patch fixes
that.
Without this patch guest MCE logs fails print DAR value:
[ 11.933608] Disabling lock debugging due to kernel taint
[ 11.933773] MCE: CPU0: machine check (Severe) Host TLB Multihit [Recovered]
[ 11.933979] MCE: CPU0: NIP: [c000000000090b34] radix__flush_tlb_range_psize+0x194/0xf00
[ 11.934223] MCE: CPU0: Initiator CPU
[ 11.934341] MCE: CPU0: Unknown
After the change:
[ 22.454149] Disabling lock debugging due to kernel taint
[ 22.454316] MCE: CPU0: machine check (Severe) Host TLB Multihit DAR: deadbeefdeadbeef [Recovered]
[ 22.454605] MCE: CPU0: NIP: [c0000000003e5804] kmem_cache_alloc+0x84/0x330
[ 22.454820] MCE: CPU0: Initiator CPU
[ 22.454944] MCE: CPU0: Unknown
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.ibm.com>
Message-Id: <158451653844.22972.17999316676230071087.stgit@jupiter>
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'monitor')
0 files changed, 0 insertions, 0 deletions