diff options
| author | Sean Christopherson <seanjc@google.com> | 2022-08-31 00:17:06 +0000 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2022-11-30 16:19:43 -0800 |
| commit | 1f158147181b83c5ae02273d0b3b9eddaebcc854 (patch) | |
| tree | 0dba7accc8bd2cf5959aca04dc01e4fbf0660401 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | b93d2ec34ef368bb854289db99d8d6ca7f523e25 (diff) | |
KVM: x86: Clean up KVM_CAP_X86_USER_SPACE_MSR documentation
Clean up the KVM_CAP_X86_USER_SPACE_MSR documentation to eliminate
misleading and/or inconsistent verbiage, and to actually document what
accesses are intercepted by which flags.
- s/will/may since not all #GPs are guaranteed to be intercepted
- s/deflect/intercept to align with common KVM terminology
- s/user space/userspace to align with the majority of KVM docs
- Avoid using "trap" terminology, as KVM exits to userspace _before_
stepping, i.e. doesn't exhibit trap-like behavior
- Actually document the flags
Signed-off-by: Sean Christopherson <seanjc@google.com>
Link: https://lore.kernel.org/r/20220831001706.4075399-4-seanjc@google.com
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions