From: Keith Busch <kbusch@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.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: Mon, 27 Jan 2025 11:22:29 -0700 [thread overview]
Message-ID: <Z5fO5bac8ohqUH1D@kbusch-mbp> (raw)
In-Reply-To: <Z5e4w7IlEEk2cpH-@google.com>
On Mon, Jan 27, 2025 at 08:48:03AM -0800, Sean Christopherson wrote:
> > > - vhost_task_start(kvm->arch.nx_huge_page_recovery_thread);
> > > + if (!nx_thread)
> > > + return;
> > > +
> > > + vhost_task_start(nx_thread);
> > > +
> > > + /* Make the task visible only once it is fully started. */
> > > + WRITE_ONCE(kvm->arch.nx_huge_page_recovery_thread, nx_thread);
> >
> > I believe the WRITE_ONCE needs to happen before the vhost_task_start to
> > ensure the parameter update callback can see it before it's started.
>
> It's not clear to me that calling vhost_task_wake() before vhost_task_start() is
> allowed, which is why I deliberately waited until the task was started to make it
> visible. Though FWIW, doing "vhost_task_wake(nx_thread)" before vhost_task_start()
> doesn't explode.
Hm, it does look questionable to try to wake a process that hadn't been
started yet, but I think it may be okay: task state will be TASK_NEW
before vhost_task_start(), which looks like will cause wake_up_process()
to do nothing.
next prev parent reply other threads:[~2025-01-27 18:22 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 [this message]
2025-01-28 15:41 ` Paolo Bonzini
2025-01-28 15:44 ` Keith Busch
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=Z5fO5bac8ohqUH1D@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