aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorThomas Huth <[email protected]>2022-11-23 10:08:33 +0100
committerJanosch Frank <[email protected]>2022-11-24 14:43:17 +0100
commit0dd4cdccdab3d74bd86b868768a7dca216bcce7e (patch)
treed542c9bcd6e7f6107db186a5b890ab3a2892bdd4 /tools/perf/util/scripting-engines/trace-event-python.c
parenteb7081409f94a9a8608593d0fb63a1aa3d6f95d8 (diff)
KVM: s390: vsie: Fix the initialization of the epoch extension (epdx) field
We recently experienced some weird huge time jumps in nested guests when rebooting them in certain cases. After adding some debug code to the epoch handling in vsie.c (thanks to David Hildenbrand for the idea!), it was obvious that the "epdx" field (the multi-epoch extension) did not get set to 0xff in case the "epoch" field was negative. Seems like the code misses to copy the value from the epdx field from the guest to the shadow control block. By doing so, the weird time jumps are gone in our scenarios. Link: https://bugzilla.redhat.com/show_bug.cgi?id=2140899 Fixes: 8fa1696ea781 ("KVM: s390: Multiple Epoch Facility support") Signed-off-by: Thomas Huth <[email protected]> Reviewed-by: Christian Borntraeger <[email protected]> Acked-by: David Hildenbrand <[email protected]> Reviewed-by: Claudio Imbrenda <[email protected]> Reviewed-by: Janosch Frank <[email protected]> Cc: [email protected] # 4.19+ Link: https://lore.kernel.org/r/[email protected] Message-Id: <[email protected]> Signed-off-by: Janosch Frank <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions