From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: x86: kvm_init_msr_list() cleanup
Date: Mon, 18 May 2020 12:52:19 +0200 [thread overview]
Message-ID: <f630dc53-61db-71fb-d868-cb8eb70f504d@redhat.com> (raw)
In-Reply-To: <20200218234012.7110-1-sean.j.christopherson@intel.com>
On 19/02/20 00:40, Sean Christopherson wrote:
> Three cleanup patches in kvm_init_msr_list() and related code.
>
> Note, these were previously posted as the first three patches of larger
> series[*] that mutated into an entirely different beast, which is how they
> have been reviewed by Vitaly despite being v1.
>
> [*] https://patchwork.kernel.org/cover/11357065/
>
> Sean Christopherson (3):
> KVM: x86: Remove superfluous brackets from case statement
> KVM: x86: Take an unsigned 32-bit int for has_emulated_msr()'s index
> KVM: x86: Snapshot MSR index in a local variable when processing lists
>
> arch/x86/include/asm/kvm_host.h | 2 +-
> arch/x86/kvm/svm.c | 2 +-
> arch/x86/kvm/vmx/vmx.c | 2 +-
> arch/x86/kvm/x86.c | 26 +++++++++++++++-----------
> 4 files changed, 18 insertions(+), 14 deletions(-)
>
Queued (better late than never).
Paolo
prev parent reply other threads:[~2020-05-18 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 23:40 [PATCH 0/3] KVM: x86: kvm_init_msr_list() cleanup Sean Christopherson
2020-02-18 23:40 ` [PATCH 1/3] KVM: x86: Remove superfluous brackets from case statement Sean Christopherson
2020-02-18 23:40 ` [PATCH 2/3] KVM: x86: Take an unsigned 32-bit int for has_emulated_msr()'s index Sean Christopherson
2020-02-18 23:40 ` [PATCH 3/3] KVM: x86: Snapshot MSR index in a local variable when processing lists Sean Christopherson
2020-05-18 10:52 ` Paolo Bonzini [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=f630dc53-61db-71fb-d868-cb8eb70f504d@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).