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 6.2 0/5] KVM CR0.WP series backport
Date: Thu, 11 May 2023 14:16:22 -0700 [thread overview]
Message-ID: <ZF1bJgJSepCwE02l@google.com> (raw)
In-Reply-To: <20230508154457.29956-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 v6.2. All
> commits applied either clean or with only minor changes needed to
> account for missing prerequisite patches, e.g. the lack of a
> kvm_is_cr0_bit_set() helper for patch 5 or the slightly different
> surrounding context in patch 4 (__always_inline vs. plain inline for
> to_kvm_vmx()).
>
> 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 v6.2.10 7.61s 7.98s 68.6s
> + patches 3.37s 3.41s 70.2s
>
> The KVM unit test suite showed no regressions.
>
> Please consider applying.
>
> Thanks,
> Mathias
>
> [1] https://lore.kernel.org/kvm/20230322013731.102955-1-minipli@grsecurity.net/
> [2] https://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
>
>
> Mathias Krause (3):
> KVM: x86: Do not unload MMU roots when only toggling CR0.WP with TDP
> enabled
> KVM: x86: Make use of kvm_read_cr*_bits() when testing bits
> KVM: VMX: Make CR0.WP a guest owned bit
>
> Paolo Bonzini (1):
> KVM: x86/mmu: Avoid indirect call for get_cr3
>
> Sean Christopherson (1):
> KVM: x86/mmu: Refresh CR0.WP prior to checking for emulated permission
> faults
Acked-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2023-05-11 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 15:44 [PATCH 6.2 0/5] KVM CR0.WP series backport Mathias Krause
2023-05-08 15:44 ` [PATCH 6.2 1/5] KVM: x86/mmu: Avoid indirect call for get_cr3 Mathias Krause
2023-05-08 15:44 ` [PATCH 6.2 2/5] KVM: x86: Do not unload MMU roots when only toggling CR0.WP with TDP enabled Mathias Krause
2023-05-08 15:44 ` [PATCH 6.2 3/5] KVM: x86: Make use of kvm_read_cr*_bits() when testing bits Mathias Krause
2023-05-08 15:44 ` [PATCH 6.2 4/5] KVM: VMX: Make CR0.WP a guest owned bit Mathias Krause
2023-05-08 15:44 ` [PATCH 6.2 5/5] KVM: x86/mmu: Refresh CR0.WP prior to checking for emulated permission faults Mathias Krause
2023-05-11 21:16 ` Sean Christopherson [this message]
2023-05-12 11:17 ` [PATCH 6.2 0/5] KVM CR0.WP series backport Mathias Krause
2023-05-12 0:24 ` Sasha Levin
2023-05-12 0:30 ` Sasha Levin
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=ZF1bJgJSepCwE02l@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox