From: Lai Jiangshan <jiangshanlai@gmail.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>
Cc: Lai Jiangshan <jiangshan.ljs@antgroup.com>
Subject: [PATCH V2 0/5] KVM: X86: permission_fault() for SMAP
Date: Fri, 11 Mar 2022 15:03:40 +0800 [thread overview]
Message-ID: <20220311070346.45023-1-jiangshanlai@gmail.com> (raw)
From: Lai Jiangshan <jiangshan.ljs@antgroup.com>
Some change in permission_fault() for SMAP. It also reduces
calls two callbacks to get CPL and RFLAGS in come cases, but it
has not any measurable performance change in tests (kernel build
in guest).
Changed from 1:
gross implicit access into @access as Sean suggested.
Use my official email address (Ant Group). The work is backed
by my company and I was incorrectly misunderstood that
XXX@linux.alibaba.com is the only portal for opensource work
in the corporate group.
[V1]: https://lore.kernel.org/kvm/20211207095039.53166-1-jiangshanlai@gmail.com/
Lai Jiangshan (6):
KVM: X86: Change the type of access u32 to u64
KVM: X86: Fix comments in update_permission_bitmask
KVM: X86: Rename variable smap to not_smap in permission_fault()
KVM: X86: Handle implicit supervisor access with SMAP
KVM: X86: Only get rflags when needed in permission_fault()
KVM: X86: Propagate the nested page fault info to the guest
arch/x86/include/asm/kvm_host.h | 6 +++-
arch/x86/kvm/kvm_emulate.h | 3 +-
arch/x86/kvm/mmu.h | 54 ++++++++++++++++++++++-----------
arch/x86/kvm/mmu/mmu.c | 10 +++---
arch/x86/kvm/mmu/paging_tmpl.h | 16 ++++++----
arch/x86/kvm/svm/nested.c | 10 ++----
arch/x86/kvm/vmx/nested.c | 11 +++++++
arch/x86/kvm/x86.c | 32 ++++++++++---------
8 files changed, 89 insertions(+), 53 deletions(-)
--
2.19.1.6.gb485710b
next reply other threads:[~2022-03-11 7:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 7:03 Lai Jiangshan [this message]
2022-03-11 7:03 ` [PATCH V2 1/5] KVM: X86: Change the type of access u32 to u64 Lai Jiangshan
2022-03-11 7:03 ` [PATCH V2 2/5] KVM: X86: Fix comments in update_permission_bitmask Lai Jiangshan
2022-03-11 7:03 ` [PATCH V2 3/5] KVM: X86: Rename variable smap to not_smap in permission_fault() Lai Jiangshan
2022-03-11 7:03 ` [PATCH V2 4/5] KVM: X86: Handle implicit supervisor access with SMAP Lai Jiangshan
2022-03-15 21:04 ` Paolo Bonzini
2022-03-11 7:03 ` [PATCH V2 5/5] KVM: X86: Only get rflags when needed in permission_fault() Lai Jiangshan
2022-03-11 7:03 ` [RFC PATCH V2 6/5] KVM: X86: Propagate the nested page fault info to the guest Lai Jiangshan
2022-03-15 21:06 ` [PATCH V2 0/5] KVM: X86: permission_fault() for SMAP Paolo Bonzini
2022-03-16 2:38 ` Lai Jiangshan
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=20220311070346.45023-1-jiangshanlai@gmail.com \
--to=jiangshanlai@gmail.com \
--cc=jiangshan.ljs@antgroup.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/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
all inboxes | Powered by JetHome®