From: Timur Tabi <ttabi@nvidia.com>
To: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"lyude@redhat.com" <lyude@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "airlied@redhat.com" <airlied@redhat.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"mhenning@darkrefraction.com" <mhenning@darkrefraction.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
Zhi Wang <zhiw@nvidia.com>,
"airlied@gmail.com" <airlied@gmail.com>,
"dakr@kernel.org" <dakr@kernel.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"mripard@kernel.org" <mripard@kernel.org>,
"bskeggs@nvidia.com" <bskeggs@nvidia.com>
Subject: Re: [PATCH v2] drm/nouveau/gsp: Allocate fwsec-sb at boot
Date: Thu, 4 Dec 2025 23:10:15 +0000 [thread overview]
Message-ID: <c043bcd69d4630bfc63ea33ad927be6ea55ceac3.camel@nvidia.com> (raw)
In-Reply-To: <20251202175918.63533-1-lyude@redhat.com>
On Tue, 2025-12-02 at 12:59 -0500, Lyude Paul wrote:
> Since this firmware can't use non-contiguous allocations, the best solution
> to avoid this issue is to simply allocate the memory for fwsec-sb during
> initial driver-load, and reuse the memory allocation when fwsec-sb needs to
> be used. We then release the memory allocations on driver unload.
>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> Fixes: 594766ca3e53 ("drm/nouveau/gsp: move booter handling to GPU-specific code")
> Cc: <stable@vger.kernel.org> # v6.16+
Reviewed-by: Timur Tabi <ttabi@nvidia.com>
prev parent reply other threads:[~2025-12-04 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 17:59 [PATCH v2] drm/nouveau/gsp: Allocate fwsec-sb at boot Lyude Paul
2025-12-04 23:10 ` Timur Tabi [this message]
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=c043bcd69d4630bfc63ea33ad927be6ea55ceac3.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=bskeggs@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mhenning@darkrefraction.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--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 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.