From: Lukas Wunner <lukas@wunner•de>
To: Rodrigo Vivi <rodrigo.vivi@intel•com>
Cc: dri-devel@lists•freedesktop.org, intel-xe@lists•freedesktop.org,
Dave Airlie <airlied@gmail•com>,
Joonas Lahtinen <joonas.lahtinen@linux•intel.com>,
Simona Vetter <simona.vetter@ffwll•ch>,
Hawking Zhang <Hawking.Zhang@amd•com>,
Alex Deucher <alexander.deucher@amd•com>,
Zack McKevitt <zachary.mckevitt@oss•qualcomm.com>,
Aravind Iddamsetty <aravind.iddamsetty@linux•intel.com>,
netdev@vger•kernel.org, "David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Simon Horman <horms@kernel•org>
Subject: Re: DRM_RAS for CPER Error logging?!
Date: Fri, 31 Oct 2025 06:38:57 +0100 [thread overview]
Message-ID: <aQRLccLXfgfoWaIP@wunner.de> (raw)
In-Reply-To: <aQN6dqFdrXxLKWlI@intel.com>
On Thu, Oct 30, 2025 at 10:47:18AM -0400, Rodrigo Vivi wrote:
> On Tue, Oct 28, 2025 at 03:13:15PM -0400, Rodrigo Vivi wrote:
> > On Mon, Sep 29, 2025 at 05:44:12PM -0400, Rodrigo Vivi wrote:
> >
> > Hey Dave, Sima, AMD folks, Qualcomm folks,
>
> + Netlink list and maintainers to get some feedback on the netlink usage
> proposed here.
>
> Specially to check if there's any concern with CPER blob going through
> netlink or if there's any size limitation or concern.
How large are those blobs? If the netlink message exceeds PAGE_SIZE
because of the CPER blob, a workaround might be to attach it to the
skb as fragments with skb_add_rx_frag().
Thanks,
Lukas
next prev parent reply other threads:[~2025-10-31 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250929214415.326414-4-rodrigo.vivi@intel.com>
[not found] ` <aQEVy1qjaDCwL_cc@intel.com>
2025-10-30 14:47 ` DRM_RAS for CPER Error logging?! Rodrigo Vivi
2025-10-30 15:37 ` DRM_RAS (netlink genl family) " Rodrigo Vivi
2025-10-31 5:38 ` Lukas Wunner [this message]
2025-11-06 13:08 ` DRM_RAS " Rodrigo Vivi
[not found] ` <c8caad3b-d7b9-4e0c-8d90-5b2bc576cabf@oss.qualcomm.com>
2025-11-06 13:42 ` [PATCH 0/2] Introduce DRM_RAS using generic netlink for RAS Rodrigo Vivi
2025-11-07 20:20 ` Zack McKevitt
2025-11-08 3:01 ` Rodrigo Vivi
2025-12-09 21:40 ` Rodrigo Vivi
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=aQRLccLXfgfoWaIP@wunner.de \
--to=lukas@wunner$(echo .)de \
--cc=Hawking.Zhang@amd$(echo .)com \
--cc=airlied@gmail$(echo .)com \
--cc=alexander.deucher@amd$(echo .)com \
--cc=aravind.iddamsetty@linux$(echo .)intel.com \
--cc=davem@davemloft$(echo .)net \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=intel-xe@lists$(echo .)freedesktop.org \
--cc=joonas.lahtinen@linux$(echo .)intel.com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=rodrigo.vivi@intel$(echo .)com \
--cc=simona.vetter@ffwll$(echo .)ch \
--cc=zachary.mckevitt@oss$(echo .)qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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