From: Keith Busch <kbusch@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86/mmu: Ensure NX huge page recovery thread is alive before waking
Date: Tue, 28 Jan 2025 08:44:26 -0700 [thread overview]
Message-ID: <Z5j7Wq1E6DqUYu8D@kbusch-mbp> (raw)
In-Reply-To: <a0d9ad95-ea69-45dc-a07f-b6dc43e9731e@redhat.com>
On Tue, Jan 28, 2025 at 04:41:41PM +0100, Paolo Bonzini wrote:
> I'm queuing the patch with the store before vhost_task_start, and
> acquire/release instead of just READ_ONCE/WRITE_ONCE.
Thanks, looks good to me:
Reviewed-by: Keith Busch <kbusch@kernel.org>
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index 74c20dbb92da..6d5708146384 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -7127,7 +7127,8 @@ static void kvm_wake_nx_recovery_thread(struct kvm *kvm)
> * may not be valid even though the VM is globally visible. Do nothing,
> * as such a VM can't have any possible NX huge pages.
> */
> - struct vhost_task *nx_thread = READ_ONCE(kvm->arch.nx_huge_page_recovery_thread);
> + struct vhost_task *nx_thread =
> + smp_load_acquire(&kvm->arch.nx_huge_page_recovery_thread);
> if (nx_thread)
> vhost_task_wake(nx_thread);
> @@ -7474,10 +7475,10 @@ static void kvm_mmu_start_lpage_recovery(struct once *once)
> if (!nx_thread)
> return;
> - vhost_task_start(nx_thread);
> + /* Make the task visible only once it is fully created. */
> + smp_store_release(&kvm->arch.nx_huge_page_recovery_thread, nx_thread);
> - /* Make the task visible only once it is fully started. */
> - WRITE_ONCE(kvm->arch.nx_huge_page_recovery_thread, nx_thread);
> + vhost_task_start(nx_thread);
> }
> int kvm_mmu_post_init_vm(struct kvm *kvm)
>
next prev parent reply other threads:[~2025-01-28 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 23:46 [PATCH] KVM: x86/mmu: Ensure NX huge page recovery thread is alive before waking Sean Christopherson
2025-01-25 0:50 ` Sean Christopherson
2025-01-25 4:11 ` Keith Busch
2025-01-27 16:48 ` Sean Christopherson
2025-01-27 17:04 ` Keith Busch
2025-01-27 17:19 ` Sean Christopherson
2025-01-27 18:22 ` Keith Busch
2025-01-28 15:41 ` Paolo Bonzini
2025-01-28 15:44 ` Keith Busch [this message]
2025-02-04 16:28 ` 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=Z5j7Wq1E6DqUYu8D@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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