aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorSean Christopherson <sean.j.christopherson@intel.com>2019-01-25 07:41:12 -0800
committerPaolo Bonzini <pbonzini@redhat.com>2019-02-20 22:48:13 +0100
commit5e0781df18990497f4cd96a959ca583d83b6d1e0 (patch)
tree191aea7cc7477ff88d9d678fee228a801ca5d5d3 /tools/perf/scripts/python
parentKVM: VMX: Create a stack frame in vCPU-run (diff)
downloadlinux-5e0781df18990497f4cd96a959ca583d83b6d1e0.tar.gz
linux-5e0781df18990497f4cd96a959ca583d83b6d1e0.zip
KVM: VMX: Move vCPU-run code to a proper assembly routine
As evidenced by the myriad patches leading up to this moment, using an inline asm blob for vCPU-run is nothing short of horrific. It's also been called "unholy", "an abomination" and likely a whole host of other names that would violate the Code of Conduct if recorded here and now. The code is relocated nearly verbatim, e.g. quotes, newlines, tabs and __stringify need to be dropped, but other than those cosmetic changes the only functional changees are to add the "call" and replace the final "jmp" with a "ret". Note that STACK_FRAME_NON_STANDARD is also dropped from __vmx_vcpu_run(). Suggested-by: Andi Kleen <ak@linux.intel.com> Suggested-by: Josh Poimboeuf <jpoimboe@redhat.com> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions