diff options
| author | Sean Christopherson <sean.j.christopherson@intel.com> | 2020-07-03 05:35:29 +0300 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-07-09 20:29:38 +0300 |
| commit | 53a3f4877152fe1c1d6c499a49bf573b60f5dc41 (patch) | |
| tree | 31d66894cbe587c173a9755e6bcc522c0242439b /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 284aa868688ac87d0eac7792b22b9c05f7a3cc45 (diff) | |
| download | linux-53a3f4877152fe1c1d6c499a49bf573b60f5dc41.tar.xz | |
KVM: x86/mmu: Try to avoid crashing KVM if a MMU memory cache is empty
Attempt to allocate a new object instead of crashing KVM (and likely the
kernel) if a memory cache is unexpectedly empty. Use GFP_ATOMIC for the
allocation as the caches are used while holding mmu_lock. The immediate
BUG_ON() makes the code unnecessarily explosive and led to confusing
minimums being used in the past, e.g. allocating 4 objects where 1 would
suffice.
Reviewed-by: Ben Gardon <bgardon@google.com>
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Message-Id: <20200703023545.8771-6-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