From: Sean Christopherson <seanjc@google.com>
To: Mathias Krause <minipli@grsecurity.net>
Cc: stable@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 5.10 00/10] KVM CR0.WP series backport
Date: Thu, 11 May 2023 14:19:25 -0700 [thread overview]
Message-ID: <ZF1b3TVTibSbnHrH@google.com> (raw)
In-Reply-To: <20230508154804.30078-1-minipli@grsecurity.net>
On Mon, May 08, 2023, Mathias Krause wrote:
> This is a backport of the CR0.WP KVM series[1] to Linux v5.10. It
> further extends the v5.15 backport by two patches, namely patch 5 (which
> is the prerequisite for Lai's patches) and patch 8 which was already
> part of the v5.15.27 stable update but didn't made it to v5.10.
>
> I used 'ssdd 10 50000' from rt-tests[2] as a micro-benchmark, running on
> a grsecurity L1 VM. Below table shows the results (runtime in seconds,
> lower is better):
>
> legacy TDP shadow
> Linux v5.10.177 10.37s 88.7s 69.7s
> + patches 4.88s 4.92s 70.1s
>
> TDP MMU is, as for v5.15, slower than shadow paging on a vanilla kernel.
> Fortunately it's disabled by default.
>
> The KVM unit test suite showed no regressions.
>
> Please consider applying.
NAK, same reasoning as the 5.15 backports.
https://lore.kernel.org/all/ZF1a8xIGLwcdJDVZ@google.com
prev parent reply other threads:[~2023-05-11 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 15:47 [PATCH 5.10 00/10] KVM CR0.WP series backport Mathias Krause
2023-05-08 15:47 ` [PATCH 5.10 01/10] KVM: x86/mmu: Avoid indirect call for get_cr3 Mathias Krause
2023-05-08 15:47 ` [PATCH 5.10 02/10] KVM: x86: Do not unload MMU roots when only toggling CR0.WP with TDP enabled Mathias Krause
2023-05-08 15:47 ` [PATCH 5.10 03/10] KVM: x86: Make use of kvm_read_cr*_bits() when testing bits Mathias Krause
2023-05-08 15:47 ` [PATCH 5.10 04/10] KVM: VMX: Make CR0.WP a guest owned bit Mathias Krause
2023-05-08 15:47 ` [PATCH 5.10 05/10] KVM: x86: Read and pass all CR0/CR4 role bits to shadow MMU helper Mathias Krause
2023-05-08 15:48 ` [PATCH 5.10 06/10] KVM: X86: Don't reset mmu context when X86_CR4_PCIDE 1->0 Mathias Krause
2023-05-08 15:48 ` [PATCH 5.10 07/10] KVM: X86: Don't reset mmu context when toggling X86_CR4_PGE Mathias Krause
2023-05-08 15:48 ` [PATCH 5.10 08/10] KVM: X86: Ensure that dirty PDPTRs are loaded Mathias Krause
2023-05-08 15:48 ` [PATCH 5.10 09/10] KVM: x86/mmu: Reconstruct shadow page root if the guest PDPTEs is changed Mathias Krause
2023-05-08 15:48 ` [PATCH 5.10 10/10] KVM: x86/mmu: Refresh CR0.WP prior to checking for emulated permission faults Mathias Krause
2023-05-11 21:19 ` Sean Christopherson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZF1b3TVTibSbnHrH@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=minipli@grsecurity.net \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.