From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bmailout3.hostsharing.net (bmailout3.hostsharing.net [176.9.242.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8E25B2D060B for ; Fri, 31 Oct 2025 05:39:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=176.9.242.62 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761889144; cv=none; b=flvrDC6I8UAOk9V+tEAX0k/TO/stnGJECKPuOq2J0028PcHnXHbf90kx/X+stj4T/uoRS6yBOEkRfVUSplGn4O5lZParV/fKKn/R5MVADrIbjvwIWeCK1QSeMGehPG1fK2XgTsq8rvup7ZjKHXAK2fRbpBIT8LW1z8CTPlD96U8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761889144; c=relaxed/simple; bh=9B4PxnWoGNaVpGuDpPXyKPVllYYYGF3TeYjrkV2rP/o=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=gEl0z1flfNTVb0vXxhnNLLy3jrUBoCphx1FsnIDE8zpM1alDvu7oEhU5cfYh3yx1P6NIA2RlcmWnrLwxgVv3GnBObwnzIFQWZvZ2vBPNoB37ERIAHi6DwHU3u+XhGJNzgDWViSRNjDL6pc7E743szpynvRRoK9kNhmFz88yTX5Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=wunner.de; spf=none smtp.mailfrom=h08.hostsharing.net; arc=none smtp.client-ip=176.9.242.62 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=wunner.de Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=h08.hostsharing.net Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.hostsharing.net", Issuer "RapidSSL TLS RSA CA G1" (verified OK)) by bmailout3.hostsharing.net (Postfix) with ESMTPS id 0C2912C0009F; Fri, 31 Oct 2025 06:38:57 +0100 (CET) Received: by h08.hostsharing.net (Postfix, from userid 100393) id C5D9E5B97; Fri, 31 Oct 2025 06:38:57 +0100 (CET) Date: Fri, 31 Oct 2025 06:38:57 +0100 From: Lukas Wunner To: Rodrigo Vivi Cc: dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org, Dave Airlie , Joonas Lahtinen , Simona Vetter , Hawking Zhang , Alex Deucher , Zack McKevitt , Aravind Iddamsetty , netdev@vger.kernel.org, "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Simon Horman Subject: Re: DRM_RAS for CPER Error logging?! Message-ID: References: <20250929214415.326414-4-rodrigo.vivi@intel.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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