From: "Radim Krčmář" <rkrcmar@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v1 00/13] KVM x86/VMX cleanups
Date: Thu, 10 Aug 2017 19:58:48 +0200 [thread overview]
Message-ID: <20170810175847.GC22461@flask> (raw)
In-Reply-To: <20170804131428.15844-1-david@redhat.com>
2017-08-04 15:14+0200, David Hildenbrand:
> Some cleanups discovered while digging through the code.
>
> David Hildenbrand (13):
> KVM: x86: mmu: returning void in a void function is strange
> KVM: x86: mmu: use for_each_shadow_entry_lockless()
> KVM: x86: mmu: free_page can handle NULL
> KVM: x86: drop BUG_ON(vcpu->kvm)
> KVM: VMX: vmx_vcpu_setup() cannot fail
> KVM: x86: no need to inititalize vcpu members to 0
> KVM: VMX: drop enable_ept check from ept_sync_context()
> KVM: VMX: call ept_sync_global() with enable_ept only
> KVM: VMX: drop unnecessary function declarations
> KVM: nVMX: no need to set vcpu->cpu when switching vmcs
> KVM: VMX: cleanup init_rmode_identity_map()
> KVM: x86: document special identity map address value
> KVM: x86: allow setting identity map addr with no vcpus only
>
> Documentation/virtual/kvm/api.txt | 4 ++++
> arch/x86/kvm/mmu.c | 26 ++++++++------------
> arch/x86/kvm/vmx.c | 50 ++++++++++-----------------------------
> arch/x86/kvm/x86.c | 21 +++++++---------
> 4 files changed, 35 insertions(+), 66 deletions(-)
Nice cleanup,
Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>
next prev parent reply other threads:[~2017-08-10 17:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 13:14 [PATCH v1 00/13] KVM x86/VMX cleanups David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 01/13] KVM: x86: mmu: returning void in a void function is strange David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 02/13] KVM: x86: mmu: use for_each_shadow_entry_lockless() David Hildenbrand
2017-08-14 10:21 ` Paolo Bonzini
2017-08-17 10:12 ` David Hildenbrand
2017-08-17 10:23 ` Paolo Bonzini
2017-08-17 10:39 ` David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 03/13] KVM: x86: mmu: free_page can handle NULL David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 04/13] KVM: x86: drop BUG_ON(vcpu->kvm) David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 05/13] KVM: VMX: vmx_vcpu_setup() cannot fail David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 06/13] KVM: x86: no need to inititalize vcpu members to 0 David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 07/13] KVM: VMX: drop enable_ept check from ept_sync_context() David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 08/13] KVM: VMX: call ept_sync_global() with enable_ept only David Hildenbrand
2017-08-14 10:25 ` Paolo Bonzini
2017-08-17 10:06 ` David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 09/13] KVM: VMX: drop unnecessary function declarations David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 10/13] KVM: nVMX: no need to set vcpu->cpu when switching vmcs David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 11/13] KVM: VMX: cleanup init_rmode_identity_map() David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 12/13] KVM: x86: document special identity map address value David Hildenbrand
2017-08-04 13:14 ` [PATCH v1 13/13] KVM: x86: allow setting identity map addr with no vcpus only David Hildenbrand
2017-08-10 17:58 ` Radim Krčmář [this message]
2017-08-14 10:30 ` [PATCH v1 00/13] KVM x86/VMX cleanups Paolo Bonzini
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=20170810175847.GC22461@flask \
--to=rkrcmar@redhat.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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