From: Alexandre Courbot <acourbot@nvidia.com>
To: dakr@kernel.org, Matteo Kloiber <kernel@matt3o12.de>
Cc: aliceryhl@google.com, ojeda@kernel.org, airlied@gmail.com,
simona@ffwll.ch, abdiel.janulgue@gmail.com,
daniel.almeida@collabora.com, robin.murphy@arm.com,
a.hindborg@kernel.org, nova-gpu@lists.linux.dev,
dri-devel@lists.freedesktop.org, driver-core@lists.linux.dev,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] gpu: nova-core: declare unlimited DMA max segment size
Date: Mon, 21 Sep 2026 12:44:43 +0900 [thread overview]
Message-ID: <178996228310.999062.10377951387828615492.b4-ty@b4> (raw)
In-Reply-To: <20260913210828.125655-2-kernel@matt3o12.de>
On Sun, 13 Sep 2026 23:08:27 +0200, Matteo Kloiber wrote:
> The PCI default max_seg_size is 64 KiB. nova-core never raises it, so
> mapping the GSP firmware image (~60 MiB) as a scatter-gather table
> triggers a DMA-API debug warning when contiguous pages coalesce into
> segments that exceed the default:
>
> DMA-API: nova-core 0000:00:03.0: mapping sg segment longer than
> device claims to support [len=62914560] [max=65536]
>
> [...]
Applied to drm-rust-next, thanks and congrats on your first kernel patch! :)
[1/2] gpu: nova-core: declare unlimited DMA max segment size
commit: 6bd5eaeb9827ca7ba953b68fb27948fdb3e40630
Patch 2 has triggered more discussion as hoped, so let's see where this goes
first.
next prev parent reply other threads:[~2026-09-21 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 21:08 [PATCH v2 0/2] rust: honor the maximum DMA segment size Matteo Kloiber
2026-09-13 21:08 ` [PATCH v2 1/2] gpu: nova-core: declare unlimited DMA max " Matteo Kloiber
2026-09-21 3:44 ` Alexandre Courbot [this message]
2026-09-13 21:08 ` [PATCH v2 2/2] rust: scatterlist: honor the device's maximum " Matteo Kloiber
2026-09-24 15:51 ` (subset) [PATCH v2 0/2] rust: honor the maximum DMA " Danilo Krummrich
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=178996228310.999062.10377951387828615492.b4-ty@b4 \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=driver-core@lists.linux.dev \
--cc=kernel@matt3o12.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--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