summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2022-05-26 21:08:13 +0000
committerPaolo Bonzini <pbonzini@redhat.com>2022-06-10 10:01:30 -0400
commit0cbc60d44c35b1070eb4070b499164d27d050576 (patch)
treece1cfd691810beb5465fded0c0a621e6737b138b /tools/perf/scripts/python/bin/stackcollapse-record
parenta5ba67b42f07952ec45755bbdd66d7c6e49f555c (diff)
downloadlinux-0cbc60d44c35b1070eb4070b499164d27d050576.tar.gz
linux-0cbc60d44c35b1070eb4070b499164d27d050576.zip
KVM: x86: Use 16-bit fields to track dirty/valid emulator GPRs
Use a u16 instead of a u32 to track the dirty/valid status of GPRs in the emulator. Unlike struct kvm_vcpu_arch, x86_emulate_ctxt tracks only the "true" GPRs, i.e. doesn't include RIP in its array, and so only needs to track 16 registers. Note, maxing out at 16 GPRs is a fundamental property of x86-64 and will not change barring a massive architecture update. Legacy x86 ModRM and SIB encodings use 3 bits for GPRs, i.e. support 8 registers. x86-64 uses a single bit in the REX prefix for each possible reference type to double the number of supported GPRs to 16 registers (4 bits). Reviewed-by: Kees Cook <keescook@chromium.org> Signed-off-by: Sean Christopherson <seanjc@google.com> Message-Id: <20220526210817.3428868-5-seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions