From: Danilo Krummrich <dakr@kernel.org>
To: Gary Guo <gary@garyguo.net>
Cc: Eliot Courtney <ecourtney@nvidia.com>,
Alice Ryhl <aliceryhl@google.com>,
Alexandre Courbot <acourbot@nvidia.com>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
dri-devel <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH v3 1/2] gpu: nova-core: fix barrier usage in CPU->GSP messaging path
Date: Tue, 1 Sep 2026 16:45:56 +0200 [thread overview]
Message-ID: <b36db634-725b-44f7-bd8c-813d13e9bc81@kernel.org> (raw)
In-Reply-To: <DL3YBS0UXYMC.1KJEZ9KWV52O8@garyguo.net>
On 9/1/26 1:43 PM, Gary Guo wrote:
> So unless there's an objection, I'll take the second approach by moving barrrier
> to pointer accessors/updaters and mark these methods to have acq/rel semantics.
Much in favor of that.
Thanks,
Danilo
next prev parent reply other threads:[~2026-09-01 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 17:28 [PATCH v3 0/2] gpu: nova: fix incorrect GSP barrier usage Gary Guo
2026-08-19 17:28 ` [PATCH v3 1/2] gpu: nova-core: fix barrier usage in CPU->GSP messaging path Gary Guo
2026-08-19 17:39 ` sashiko-bot
2026-08-24 12:50 ` Eliot Courtney
2026-08-24 12:56 ` Gary Guo
2026-08-24 13:03 ` Eliot Courtney
2026-08-24 13:07 ` Gary Guo
2026-08-25 0:38 ` Eliot Courtney
2026-08-31 17:25 ` Gary Guo
2026-09-01 2:47 ` Eliot Courtney
2026-09-01 11:43 ` Gary Guo
2026-09-01 14:45 ` Danilo Krummrich [this message]
2026-08-19 17:28 ` [PATCH v3 2/2] gpu: nova-core: fix barrier usage in GSP->CPU " Gary Guo
2026-08-19 17:39 ` sashiko-bot
2026-08-24 12:51 ` Eliot Courtney
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=b36db634-725b-44f7-bd8c-813d13e9bc81@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=simona@ffwll.ch \
/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