lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DFOD9BX2FHP2.X5ST15IMUR1G@nvidia.com>
Date: Wed, 14 Jan 2026 23:02:51 +0900
From: "Alexandre Courbot" <acourbot@...dia.com>
To: "Timur Tabi" <ttabi@...dia.com>
Cc: "Joel Fernandes" <joelagnelf@...dia.com>, "gary@...yguo.net"
 <gary@...yguo.net>, "lossin@...nel.org" <lossin@...nel.org>,
 "ojeda@...nel.org" <ojeda@...nel.org>, "boqun.feng@...il.com"
 <boqun.feng@...il.com>, "a.hindborg@...nel.org" <a.hindborg@...nel.org>,
 "simona@...ll.ch" <simona@...ll.ch>, "tmgross@...ch.edu"
 <tmgross@...ch.edu>, "nouveau@...ts.freedesktop.org"
 <nouveau@...ts.freedesktop.org>, "dri-devel@...ts.freedesktop.org"
 <dri-devel@...ts.freedesktop.org>, "linux-kernel@...r.kernel.org"
 <linux-kernel@...r.kernel.org>, "rust-for-linux@...r.kernel.org"
 <rust-for-linux@...r.kernel.org>, "bjorn3_gh@...tonmail.com"
 <bjorn3_gh@...tonmail.com>, "Eliot Courtney" <ecourtney@...dia.com>,
 "aliceryhl@...gle.com" <aliceryhl@...gle.com>, "kwilczynski@...nel.org"
 <kwilczynski@...nel.org>, "linux-pci@...r.kernel.org"
 <linux-pci@...r.kernel.org>, "dakr@...nel.org" <dakr@...nel.org>,
 "bhelgaas@...gle.com" <bhelgaas@...gle.com>, "Alistair Popple"
 <apopple@...dia.com>
Subject: Re: [PATCH 6/7] gpu: nova-core: send UNLOADING_GUEST_DRIVER GSP
 command GSP upon unloading

On Sun Dec 21, 2025 at 6:30 AM JST, Timur Tabi wrote:
> On Fri, 2025-12-19 at 12:39 +0900, Alexandre Courbot wrote:
>
>
>
>> Does Nouveau really handle all messages asynchronously? Just taking a
>> look at `r535_gsp_rpc_send` I see:
>> 
>> * A potential busy-loop with `r535_gsp_rpc_handle_reply`, An argument to
>> * define whether we should wait for a reply (`policy`).
>> 
>> So it seems like each GSP command expecting a reply is effectively
>> looping until it arrives, with some messages (LIBOS_PRINT, SEQUENCER,
>> etc.) being managed by a notifier registered with the command queue. But
>> messages sent explicitly by the driver don't seem to make use of it and
>> instead process messages until they find their reply.
>
> Yes, you're right.  But the difference is that in Nouveau, all message processing is handled by
> r535_gsp_msg_recv(), which always also handles all of the asynchronous "other" messages.
>
> The above `loop` expression in Nova doesn't do that.  It's missing the asynchronous handler. 
> This is the crux of my concern.

I agree with you that this is something we want to improve (either by
adding a handler to the loop, or some other way). It should be its own
patch series once we have better visibility about how we want to handle
message, as the current implementation is still very crude and ad-hoc.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ