diff options
| author | zhenwei pi <pizhenwei@bytedance.com> | 2021-01-10 19:53:57 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-01-27 14:28:17 +0100 |
| commit | 487709fa1be2f27aa8e7de6c60587b4302a21467 (patch) | |
| tree | 3c9efe15e4abc8999957b53452a6a13922f54c24 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 8ba59e9dee31246fc34b4d4bec032093e9c06510 (diff) | |
misc: pvpanic: introduce device capability
According to pvpanic spec:
https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/specs/pvpanic.txt
The guest should determine pvpanic capability by RDPT, so initialize
capability during device probing. There is no need to register panic
notifier callback function if no events supported.
Before sending event to host side, check capability firstly.
Suggested by Greg KH, use sysfs to expose capability to user space,
also add new sysfs attribute in document.
Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Link: https://lore.kernel.org/r/20210110115358.79100-2-pizhenwei@bytedance.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions