From: Sean Christopherson <seanjc@google.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>
Cc: mlevitsk@redhat.com
Subject: Re: [PATCH v2 0/4] KVM: x86/mmu: small locking cleanups
Date: Fri, 1 Dec 2023 08:00:16 -0800 [thread overview]
Message-ID: <ZWoDEIJHD7cv-LU9@google.com> (raw)
In-Reply-To: <170137684485.660161.8230111667906795222.b4-ty@google.com>
On Thu, Nov 30, 2023, Sean Christopherson wrote:
> On Sat, 25 Nov 2023 03:33:56 -0500, Paolo Bonzini wrote:
> > Remove "bool shared" argument from functions and iterators that need
> > not know if the lock is taken for read or write. This is common because
> > protection is achieved via RCU and tdp_mmu_pages_lock or because the
> > argument is only used for assertions that can be written by hand.
> >
> > Also always take tdp_mmu_pages_lock even if mmu_lock is currently taken
> > for write.
> >
> > [...]
>
> Applied to kvm-x86 mmu, thanks!
>
> [1/4] KVM: x86/mmu: remove unnecessary "bool shared" argument from functions
> https://github.com/kvm-x86/linux/commit/2d30059d38e6
> [2/4] KVM: x86/mmu: remove unnecessary "bool shared" argument from iterators
> https://github.com/kvm-x86/linux/commit/59b93e634b40
> [3/4] KVM: x86/mmu: always take tdp_mmu_pages_lock
> https://github.com/kvm-x86/linux/commit/4072c73104f2
> [4/4] KVM: x86/mmu: fix comment about mmu_unsync_pages_lock
> https://github.com/kvm-x86/linux/commit/9dc2973a3b20
FYI, I had to force push to mmu to fixup an unrelated Fixes: issue, new hashes:
[1/4] KVM: x86/mmu: remove unnecessary "bool shared" argument from functions
https://github.com/kvm-x86/linux/commit/5f3c8c9187b6
[2/4] KVM: x86/mmu: remove unnecessary "bool shared" argument from iterators
https://github.com/kvm-x86/linux/commit/484dd27c0602
[3/4] KVM: x86/mmu: always take tdp_mmu_pages_lock
https://github.com/kvm-x86/linux/commit/250ce1b4d21a
[4/4] KVM: x86/mmu: fix comment about mmu_unsync_pages_lock
https://github.com/kvm-x86/linux/commit/e59f75de4e50
prev parent reply other threads:[~2023-12-01 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 8:33 [PATCH v2 0/4] KVM: x86/mmu: small locking cleanups Paolo Bonzini
2023-11-25 8:33 ` [PATCH v2 1/4] KVM: x86/mmu: remove unnecessary "bool shared" argument from functions Paolo Bonzini
2023-11-25 8:33 ` [PATCH v2 2/4] KVM: x86/mmu: remove unnecessary "bool shared" argument from iterators Paolo Bonzini
2023-11-25 8:33 ` [PATCH v2 3/4] KVM: x86/mmu: always take tdp_mmu_pages_lock Paolo Bonzini
2023-11-25 8:34 ` [PATCH v2 4/4] KVM: x86/mmu: fix comment about mmu_unsync_pages_lock Paolo Bonzini
2023-12-01 1:52 ` [PATCH v2 0/4] KVM: x86/mmu: small locking cleanups Sean Christopherson
2023-12-01 16:00 ` Sean Christopherson [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=ZWoDEIJHD7cv-LU9@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.