diff options
| author | Sean Christopherson <sean.j.christopherson@intel.com> | 2019-01-25 07:41:01 -0800 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-02-12 13:12:21 +0100 |
| commit | fbda0fd31a6d683637f848ba17956048dd0c7e48 (patch) | |
| tree | 07a35ae1335cd07a6ac1ce4c4d2edfe5eac3b070 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: nVMX: Reference vmx->loaded_vmcs->launched directly (diff) | |
| download | linux-fbda0fd31a6d683637f848ba17956048dd0c7e48.tar.gz linux-fbda0fd31a6d683637f848ba17956048dd0c7e48.zip | |
KVM: nVMX: Let the compiler select the reg for holding HOST_RSP
...and provide an explicit name for the constraint. Naming the input
constraint makes the code self-documenting and also avoids the fragility
of numerically referring to constraints, e.g. %4 breaks badly whenever
the constraints are modified.
Explicitly using RDX was inherited from vCPU-run, i.e. completely
arbitrary. Even vCPU-run doesn't truly need to explicitly use RDX, but
doing so is more robust as vCPU-run needs tight control over its
register usage.
Note that while the naming "conflict" between host_rsp and HOST_RSP
is slightly confusing, the former will be renamed slightly in a
future patch, at which point HOST_RSP is absolutely what is desired.
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Reviewed-by: Jim Mattson <jmattson@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions