diff options
| author |   Sean Christopherson <seanjc@google.com> | 2025-03-14 19:34:48 -0700 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2025-04-04 07:07:40 -0400 |
| commit | 81d480fdf8b7d9b13fe87e1f0516f89794708094 (patch) | |
| tree | dc764547bbd6d5dfbc2177c1c61cd7ea785058e4 /scripts/lib/kdoc/kdoc_files.py | |
| parent | KVM: selftests: Add option to rseq test to override /dev/cpu_dma_latency (diff) | |
| download | linux-rng-81d480fdf8b7d9b13fe87e1f0516f89794708094.tar.xz linux-rng-81d480fdf8b7d9b13fe87e1f0516f89794708094.zip | |
KVM: x86/mmu: Wrap sanity check on number of TDP MMU pages with KVM_PROVE_MMU
Wrap the TDP MMU page counter in CONFIG_KVM_PROVE_MMU so that the sanity
check is omitted from production builds, and more importantly to remove
the atomic accesses to account pages. A one-off memory leak in production
is relatively uninteresting, and a WARN_ON won't help mitigate a systemic
issue; it's as much about helping triage memory leaks as it is about
detecting them in the first place, and doesn't magically stop the leaks.
I.e. production environments will be quite sad if a severe KVM bug escapes,
regardless of whether or not KVM WARNs.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-ID: <20250315023448.2358456-1-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions