diff options
author | Sean Christopherson <seanjc@google.com> | 2021-11-25 01:49:43 +0000 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-11-26 07:07:49 -0500 |
commit | 40e5f9080472b614eeedcc5ba678289cd98d70df (patch) | |
tree | 74e57e9816caca4e4ba6775e58c4acdcfa7ae5ca /certs | |
parent | 2b4a5a5d56881ece3c66b9a9a8943a6f41bd7349 (diff) | |
download | linux-stable-40e5f9080472b614eeedcc5ba678289cd98d70df.tar.gz linux-stable-40e5f9080472b614eeedcc5ba678289cd98d70df.tar.bz2 linux-stable-40e5f9080472b614eeedcc5ba678289cd98d70df.zip |
KVM: nVMX: Abide to KVM_REQ_TLB_FLUSH_GUEST request on nested vmentry/vmexit
Like KVM_REQ_TLB_FLUSH_CURRENT, the GUEST variant needs to be serviced at
nested transitions, as KVM doesn't track requests for L1 vs L2. E.g. if
there's a pending flush when a nested VM-Exit occurs, then the flush was
requested in the context of L2 and needs to be handled before switching
to L1, otherwise the flush for L2 would effectiely be lost.
Opportunistically add a helper to handle CURRENT and GUEST as a pair, the
logic for when they need to be serviced is identical as both requests are
tied to L1 vs. L2, the only difference is the scope of the flush.
Reported-by: Lai Jiangshan <jiangshanlai+lkml@gmail.com>
Fixes: 07ffaf343e34 ("KVM: nVMX: Sync all PGDs on nested transition with shadow paging")
Cc: stable@vger.kernel.org
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20211125014944.536398-2-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions