From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.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,
Jia He <justin.he@arm.com>
Subject: Re: [PATCH 0/3] KVM: x86/mmu: kvm_mmu_page cleanups
Date: Mon, 6 Sep 2021 12:20:00 +0200 [thread overview]
Message-ID: <6636f9c9-96e9-40bf-e344-c0b3f6ed7bed@redhat.com> (raw)
In-Reply-To: <20210901221023.1303578-1-seanjc@google.com>
On 02/09/21 00:10, Sean Christopherson wrote:
> Patch 1 is from Jia He to remove a defunct boolean from kvm_mmu_page
> (link[*] below if you want to take it directly).
>
> Patch 2 builds on that patch to micro-optimize the TDP MMU flag.
>
> Patch 3 is another micro-optimization that probably doesn't buy much
> performance (I didn't check), feel free to ignore it.
>
> [*] https://lkml.kernel.org/r/20210830145336.27183-1-justin.he@arm.com
>
> Jia He (1):
> KVM: x86/mmu: Remove unused field mmio_cached in struct kvm_mmu_page
>
> Sean Christopherson (2):
> KVM: x86/mmu: Relocate kvm_mmu_page.tdp_mmu_page for better cache
> locality
> KVM: x86/mmu: Move lpage_disallowed_link further "down" in
> kvm_mmu_page
>
> arch/x86/kvm/mmu/mmu_internal.h | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2021-09-06 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 22:10 [PATCH 0/3] KVM: x86/mmu: kvm_mmu_page cleanups Sean Christopherson
2021-09-01 22:10 ` [PATCH 1/3] KVM: x86/mmu: Remove unused field mmio_cached in struct kvm_mmu_page Sean Christopherson
2021-09-01 22:10 ` [PATCH 2/3] KVM: x86/mmu: Relocate kvm_mmu_page.tdp_mmu_page for better cache locality Sean Christopherson
2021-09-01 22:10 ` [PATCH 3/3] KVM: x86/mmu: Move lpage_disallowed_link further "down" in kvm_mmu_page Sean Christopherson
2021-09-06 10:20 ` 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=6636f9c9-96e9-40bf-e344-c0b3f6ed7bed@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=justin.he@arm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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).