From: Danilo Krummrich <dakr@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org
Subject: Re: [PATCH 2/2] nouveau: Membar before between semaphore writes and the interrupt
Date: Fri, 29 Aug 2025 20:21:07 +0200 [thread overview]
Message-ID: <825bb276-3421-4697-86fa-ba231cd799a7@kernel.org> (raw)
In-Reply-To: <20250829021633.1674524-2-airlied@gmail.com>
On 8/29/25 4:16 AM, Dave Airlie wrote:
> From: Faith Ekstrand <faith.ekstrand@collabora.com>
>
> This ensures that the memory write and the interrupt are properly
> ordered and we won't wake up the kernel before the semaphore write has
> hit memory.
>
> Fixes: b1ca384772b6 ("drm/nouveau/gv100-: switch to volta semaphore methods")
> Cc: stable@vger.kernel.org
> Signed-off-by: Faith Ekstrand <faith.ekstrand@collabora.com>
> Signed-off-by: Dave Airlie <airlied@redhat.com>
Applied to drm-misc-fixes, thanks!
next prev parent reply other threads:[~2025-08-29 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 2:16 [PATCH 1/2] nouveau: fix disabling the nonstall irq due to storm code. (v2) Dave Airlie
2025-08-29 2:16 ` [PATCH 2/2] nouveau: Membar before between semaphore writes and the interrupt Dave Airlie
2025-08-29 18:21 ` Danilo Krummrich [this message]
2025-08-29 23:09 ` James Jones
2025-08-29 14:49 ` [PATCH 1/2] nouveau: fix disabling the nonstall irq due to storm code. (v2) Faith Ekstrand
2025-08-29 18:21 ` Danilo Krummrich
2025-09-01 18:17 ` M Henning
2025-09-01 20:52 ` Dave Airlie
2025-09-08 21:21 ` M Henning
-- strict thread matches above, loose matches on Subject: below --
2025-08-28 20:55 [PATCH 1/2] nouveau: fix disabling the nonstall irq due to storm code Dave Airlie
2025-08-28 20:55 ` [PATCH 2/2] nouveau: Membar before between semaphore writes and the interrupt Dave Airlie
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=825bb276-3421-4697-86fa-ba231cd799a7@kernel.org \
--to=dakr@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
/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.