From: Paolo Bonzini <pbonzini@redhat.com>
To: "Sean Christopherson" <sean.j.christopherson@intel.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: x86/mmu: minor MMIO SPTE cleanup
Date: Sat, 3 Aug 2019 08:30:04 +0200 [thread overview]
Message-ID: <c2860baa-6ef9-1020-eb6f-886a3b7cda65@redhat.com> (raw)
In-Reply-To: <20190801203523.5536-1-sean.j.christopherson@intel.com>
On 01/08/19 22:35, Sean Christopherson wrote:
> A few loosely related MMIO SPTE patches to get rid of a bit of cruft that
> has been a source of annoyance when mucking around in the MMIO code.
>
> No functional changes intended.
>
> Sean Christopherson (3):
> KVM: x86: Rename access permissions cache member in struct
> kvm_vcpu_arch
> KVM: x86/mmu: Add explicit access mask for MMIO SPTEs
> KVM: x86/mmu: Consolidate "is MMIO SPTE" code
>
> Documentation/virtual/kvm/mmu.txt | 4 ++--
> arch/x86/include/asm/kvm_host.h | 2 +-
> arch/x86/kvm/mmu.c | 31 +++++++++++++++++--------------
> arch/x86/kvm/mmu.h | 2 +-
> arch/x86/kvm/vmx/vmx.c | 2 +-
> arch/x86/kvm/x86.c | 2 +-
> arch/x86/kvm/x86.h | 2 +-
> 7 files changed, 24 insertions(+), 21 deletions(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2019-08-03 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 20:35 [PATCH 0/3] KVM: x86/mmu: minor MMIO SPTE cleanup Sean Christopherson
2019-08-01 20:35 ` [PATCH 1/3] KVM: x86: Rename access permissions cache member in struct kvm_vcpu_arch Sean Christopherson
2019-08-01 20:35 ` [PATCH 2/3] KVM: x86/mmu: Add explicit access mask for MMIO SPTEs Sean Christopherson
2019-08-01 20:35 ` [PATCH 3/3] KVM: x86/mmu: Consolidate "is MMIO SPTE" code Sean Christopherson
2019-08-03 6:30 ` 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=c2860baa-6ef9-1020-eb6f-886a3b7cda65@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.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).