diff options
| author | Sean Christopherson <sean.j.christopherson@intel.com> | 2020-09-23 15:04:24 -0700 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-09-28 07:57:36 -0400 |
| commit | c4371c2a682e0da1ed2cd7e3c5496f055d873554 (patch) | |
| tree | c571cd8be6d9b2eea3ba172ea86fb3462cdf0a15 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: x86/mmu: Invert RET_PF_* check when falling through to emulation (diff) | |
| download | linux-c4371c2a682e0da1ed2cd7e3c5496f055d873554.tar.gz linux-c4371c2a682e0da1ed2cd7e3c5496f055d873554.zip | |
KVM: x86/mmu: Return unique RET_PF_* values if the fault was fixed
Introduce RET_PF_FIXED and RET_PF_SPURIOUS to provide unique return
values instead of overloading RET_PF_RETRY. In the short term, the
unique values add clarity to the code and RET_PF_SPURIOUS will be used
by set_spte() to avoid unnecessary work for spurious faults.
In the long term, TDX will use RET_PF_FIXED to deterministically map
memory during pre-boot. The page fault flow may bail early for benign
reasons, e.g. if the mmu_notifier fires for an unrelated address. With
only RET_PF_RETRY, it's impossible for the caller to distinguish between
"cool, page is mapped" and "darn, need to try again", and thus cannot
handle benign cases like the mmu_notifier retry.
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Message-Id: <20200923220425.18402-4-sean.j.christopherson@intel.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