mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "John Hubbard" <jhubbard@nvidia.com>
Cc: "Gary Guo" <gary@garyguo.net>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Timur Tabi" <ttabi@nvidia.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"Eliot Courtney" <ecourtney@nvidia.com>,
	"Zhi Wang" <zhiw@nvidia.com>, "David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	nova-gpu@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>,
	"Joel Fernandes" <joelagnelf@nvidia.com>
Subject: Re: [PATCH v5 02/15] rust: sync: completion: add wait_for_completion_timeout()
Date: Fri, 02 Oct 2026 21:12:31 +0900	[thread overview]
Message-ID: <DLUCD1R3Y143.3BVXITEPZYCPR@nvidia.com> (raw)
In-Reply-To: <59900705-fadd-46bb-93eb-8f6d8e7be551@nvidia.com>

On Fri Oct 2, 2026 at 8:13 PM JST, John Hubbard wrote:
> On 10/2/26 12:55 PM, Alexandre Courbot wrote:
>> On Fri Oct 2, 2026 at 6:50 PM JST, Gary Guo wrote:
>>> On Wed Sep 30, 2026 at 4:41 AM BST, John Hubbard wrote:
>>>> From: Joel Fernandes <joelagnelf@nvidia.com>
>>>>
>>>> A driver that runs an interrupt self-test during probe waits for the
>>>> handler to fire. wait_for_completion() has no timeout, so a broken
>>>> interrupt path stalls probe indefinitely. Add a timeout variant of
>>>> wait_for_completion().
>>>>
>>>> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
>>>> Signed-off-by: Joel Fernandes <joelagnelf@nvidia.com>
>>>> [jhubbard: return the remaining jiffies]
>>>> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
>>>
>>> This email should have RfL list CC'ed.
>
> Hi Gary! Apologies, my send-email scripts had drifted into a
> nova-centric direction. Will fix.
>
>
>>>
>>>> ---
>>>>  rust/kernel/sync/completion.rs | 23 ++++++++++++++++++++++-
>>>>  1 file changed, 22 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/rust/kernel/sync/completion.rs b/rust/kernel/sync/completion.rs
>>>> index 35ff049ff078..7e8b3c1c880e 100644
>>>> --- a/rust/kernel/sync/completion.rs
>>>> +++ b/rust/kernel/sync/completion.rs
>>>> @@ -6,7 +6,12 @@
>>>>  //!
>>>>  //! C header: [`include/linux/completion.h`](srctree/include/linux/completion.h)
>>>>  
>>>> -use crate::{bindings, prelude::*, types::Opaque};
>>>> +use crate::{
>>>> +    bindings,
>>>> +    prelude::*,
>>>> +    time::Jiffies,
>>>> +    types::Opaque, //
>>>> +};
>>>>  
>>>>  /// Synchronization primitive to signal when a certain task has been completed.
>>>>  ///
>>>> @@ -111,4 +116,20 @@ pub fn wait_for_completion(&self) {
>>>>          // SAFETY: `self.as_raw()` is a pointer to a valid `struct completion`.
>>>>          unsafe { bindings::wait_for_completion(self.as_raw()) };
>>>>      }
>>>> +
>>>> +    /// Wait for completion of a task, with a timeout.
>>>> +    ///
>>>> +    /// This method waits for the completion of a task, or until `timeout` elapses. It is not
>>>> +    /// interruptible. Returns the number of jiffies left when the task completed, or [`None`] if
>>>> +    /// `timeout` elapsed first.
>>>> +    ///
>>>> +    /// See also [`Completion::complete_all`].
>>>> +    #[inline]
>>>> +    pub fn wait_for_completion_timeout(&self, timeout: Jiffies) -> Option<Jiffies> {
>>>
>>> NACK. Please use the typed `Delta<Jiffy>`, not this old type alias for c_ulong.
>>> I asked Miguel to take that late last cycle because I know there'll be new users
>>> that want to use Jiffies this cycle!
>>>
>>> This would avoid you having to do clamping on the max side (but you still need
>>> to clamp the value to be at least 0). There'll be a helper method for this, but
>>> it isn't available yet.
>>> https://lore.kernel.org/rust-for-linux/20261002050428.2746277-3-tomo@flapping.org/
>> 
>> I will drop this patch and replace the code using this new method (which
>> is just an optional probe-time self-test) by a polling loop on an
>> atomic. That way we can wait for the helper method to be available and
>> revisit this with the proper type.
>
> OK, whatever works best. Just in case, I did stage a fixed-up version
> of the patch locally (in case I need to send a v6), as per Gary's
> recommended Delta approach. It looks like this:

It's your series so your call, but since the elegant solution will
involve using [1] which is still under review, I would suggest waiting
for it to introduce `wait_for_completion_timeout`, moving forward with
the rest of the series, and revisit using completions once the base code
is ready to limit churn.

Otherwise we are at risk of missing the -rc6 cutoff for this series and
that means an even busier next cycle. The polling code is also simpler
overall than using completions, and for a probe-time selftest polling is
really not a problem. Nova is not losing anything by not using
completions for this.

[1] https://lore.kernel.org/rust-for-linux/20261002050428.2746277-3-tomo@flapping.org/

  reply	other threads:[~2026-10-02 12:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  3:41 [PATCH v5 00/15] nova-core: GPU interrupt support and GSP event delivery John Hubbard
2026-09-30  3:41 ` [PATCH v5 01/15] rust: pci: declare IrqType and IrqTypes with impl_flags John Hubbard
2026-10-01 14:06   ` Alexandre Courbot
2026-09-30  3:41 ` [PATCH v5 02/15] rust: sync: completion: add wait_for_completion_timeout() John Hubbard
2026-09-30  3:59   ` sashiko-bot
2026-10-01 14:06   ` Alexandre Courbot
2026-10-02  8:21   ` Alice Ryhl
2026-10-02  9:11     ` John Hubbard
2026-10-02  9:50   ` Gary Guo
2026-10-02 10:55     ` Alexandre Courbot
2026-10-02 11:13       ` John Hubbard
2026-10-02 12:12         ` Alexandre Courbot [this message]
2026-10-02 13:01           ` Gary Guo
2026-10-02 12:20       ` Danilo Krummrich
2026-09-30  3:41 ` [PATCH v5 03/15] gpu: nova-core: add the GIN vector, leaf and subtree types John Hubbard
2026-09-30  3:41 ` [PATCH v5 04/15] gpu: nova-core: add the GIN CPU interrupt tree and MSI EOI registers John Hubbard
2026-09-30  3:41 ` [PATCH v5 05/15] gpu: nova-core: add the per-architecture GIN CPU interrupt HAL John Hubbard
2026-09-30  3:41 ` [PATCH v5 06/15] gpu: nova-core: add the GIN interrupt tree and allocate its vectors John Hubbard
2026-09-30  3:41 ` [PATCH v5 07/15] gpu: nova-core: wait for GFW boot in probe, not in the Gpu constructor John Hubbard
2026-09-30 12:51   ` Danilo Krummrich
2026-10-01 14:07     ` Alexandre Courbot
2026-09-30  3:41 ` [PATCH v5 08/15] gpu: nova-core: add an interrupt delivery self-test John Hubbard
2026-09-30  3:41 ` [PATCH v5 09/15] gpu: nova-core: log GSP events instead of discarding them John Hubbard
2026-09-30  3:41 ` [PATCH v5 10/15] gpu: nova-core: return ENOMSG for an unmatched GSP message John Hubbard
2026-09-30  3:41 ` [PATCH v5 11/15] gpu: nova-core: bound a GSP wait by a single deadline John Hubbard
2026-09-30  3:41 ` [PATCH v5 12/15] gpu: nova-core: add the falcon interrupt registers and HAL methods John Hubbard
2026-09-30  3:41 ` [PATCH v5 13/15] gpu: nova-core: service GSP events from the SWGEN0 interrupt John Hubbard
2026-09-30  3:41 ` [PATCH v5 14/15] gpu: nova-core: add KUnit tests for the interrupt tree John Hubbard
2026-09-30  3:41 ` [PATCH v5 15/15] gpu: nova-core: document the GIN interrupt controller and GSP events John Hubbard
2026-10-02 13:33   ` Alexandre Courbot
2026-10-01 14:09 ` [PATCH v5 00/15] nova-core: GPU interrupt support and GSP event delivery Danilo Krummrich
2026-10-01 14:10 ` Alexandre Courbot
2026-10-02 13:19 ` Alexandre Courbot

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=DLUCD1R3Y143.3BVXITEPZYCPR@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=apopple@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=ecourtney@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=jhubbard@nvidia.com \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nova-gpu@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    --cc=ttabi@nvidia.com \
    --cc=zhiw@nvidia.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

all inboxes | Powered by JetHome®