From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: kernel test robot <lkp@intel.com>,
Detlev Casanova <detlev.casanova@collabora.com>,
linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Heiko Stuebner <heiko@sntech.de>,
Daniel Almeida <daniel.almeida@collabora.com>,
Jonathan Corbet <corbet@lwn.net>,
Ricardo Ribalda <ribalda@chromium.org>,
Hans Verkuil <hverkuil@xs4all.nl>, Yunke Cao <yunkec@google.com>,
Hans de Goede <hansg@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Pavan Bobba <opensource206@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
James Cowgill <james.cowgill@blaize.com>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com,
Jonas Karlman <jonas@kwiboo.se>,
Diederik de Haas <didi.debian@cknow.org>
Subject: Re: [PATCH v9 15/17] media: rkvdec: Add H264 support for the VDPU383 variant
Date: Wed, 21 Jan 2026 09:46:48 -0500 [thread overview]
Message-ID: <69fda4f0136285e4d2f86e7e93d5bdd812c1d47a.camel@collabora.com> (raw)
In-Reply-To: <202601211924.rqKS2Ihm-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 4489 bytes --]
Hi,
Le mercredi 21 janvier 2026 à 22:27 +0800, kernel test robot a écrit :
> Hi Detlev,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on rockchip/for-next]
> [also build test WARNING on linuxtv-media-pending/master media-tree/master linus/master v6.19-rc6 next-20260120]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Detlev-Casanova/media-uapi-HEVC-Add-v4l2_ctrl_hevc_ext_sps_-ls-t_rps-controls/20260121-071026
> base: https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git for-next
> patch link: https://lore.kernel.org/r/20260120222018.404741-16-detlev.casanova%40collabora.com
> patch subject: [PATCH v9 15/17] media: rkvdec: Add H264 support for the VDPU383 variant
> config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20260121/202601211924.rqKS2Ihm-lkp@intel.com/config)
> compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
Modification has been done to reduce the stack utilization on clang, though we
believe we are hitting limitations/bugs on older clang. We went ahead with these
patch by updating our CI to clang 21, which allocate a lot less stack with KASAN
enabled and this code. Our general advise is to use a newer clang, or GCC for
testing with KASAN.
The stack utilization is caused by the combination of loop unrolling, agressive
inlining, and write operations to bitfield (which requires the compiler to
generate more code for memory checks, since the writes are not aligned).
cheers,
Nicolas
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260121/202601211924.rqKS2Ihm-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202601211924.rqKS2Ihm-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> > > drivers/media/platform/rockchip/rkvdec/rkvdec-vdpu383-h264.c:485:12: warning: stack frame size (2064) exceeds limit (2048) in 'rkvdec_h264_run' [-Wframe-larger-than]
> 485 | static int rkvdec_h264_run(struct rkvdec_ctx *ctx)
> | ^
> 1 warning generated.
>
>
> vim +/rkvdec_h264_run +485 drivers/media/platform/rockchip/rkvdec/rkvdec-vdpu383-h264.c
>
> 484
> > 485 static int rkvdec_h264_run(struct rkvdec_ctx *ctx)
> 486 {
> 487 struct v4l2_h264_reflist_builder reflist_builder;
> 488 struct rkvdec_dev *rkvdec = ctx->dev;
> 489 struct rkvdec_h264_ctx *h264_ctx = ctx->priv;
> 490 struct rkvdec_h264_run run;
> 491 struct rkvdec_h264_priv_tbl *tbl = h264_ctx->priv_tbl.cpu;
> 492 u32 timeout_threshold;
> 493
> 494 rkvdec_h264_run_preamble(ctx, &run);
> 495
> 496 /* Build the P/B{0,1} ref lists. */
> 497 v4l2_h264_init_reflist_builder(&reflist_builder, run.decode_params,
> 498 run.sps, run.decode_params->dpb);
> 499 v4l2_h264_build_p_ref_list(&reflist_builder, h264_ctx->reflists.p);
> 500 v4l2_h264_build_b_ref_lists(&reflist_builder, h264_ctx->reflists.b0,
> 501 h264_ctx->reflists.b1);
> 502
> 503 assemble_hw_scaling_list(&run, &tbl->scaling_list);
> 504 assemble_hw_pps(ctx, &run);
> 505 lookup_ref_buf_idx(ctx, &run);
> 506 assemble_hw_rps(&reflist_builder, &run, &h264_ctx->reflists, &tbl->rps);
> 507
> 508 config_registers(ctx, &run);
> 509
> 510 rkvdec_run_postamble(ctx, &run.base);
> 511
> 512 timeout_threshold = h264_ctx->regs.common.reg013_core_timeout_threshold;
> 513 rkvdec_schedule_watchdog(rkvdec, timeout_threshold);
> 514
> 515 /* Start decoding! */
> 516 writel(timeout_threshold, rkvdec->link + VDPU383_LINK_TIMEOUT_THRESHOLD);
> 517 writel(0, rkvdec->link + VDPU383_LINK_IP_ENABLE);
> 518 writel(VDPU383_DEC_E_BIT, rkvdec->link + VDPU383_LINK_DEC_ENABLE);
> 519
> 520 return 0;
> 521 }
> 522
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-01-21 14:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 22:20 [PATCH v9 00/17] media: rkvdec: Add support for VDPU381 and VDPU383 Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 01/17] media: uapi: HEVC: Add v4l2_ctrl_hevc_ext_sps_[ls]t_rps controls Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 02/17] media: v4l2-ctrls: Add hevc_ext_sps_[ls]t_rps controls Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 03/17] media: visl: Add HEVC short and long term RPS sets Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 04/17] media: rkvdec: Switch to using structs instead of writel Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 05/17] media: rkvdec: Move cabac tables to their own source file Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 06/17] media: rkvdec: Use structs to represent the HW RPS Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 07/17] media: rkvdec: Move h264 functions to common file Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 08/17] media: rkvdec: Move hevc " Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 09/17] media: rkvdec: Add variant specific coded formats list Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 10/17] media: rkvdec: Add RCB and SRAM support Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 11/17] media: rkvdec: Support per-variant interrupt handler Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 12/17] media: rkvdec: Enable all clocks without naming them Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 13/17] media: rkvdec: Disable multicore support Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 14/17] media: rkvdec: Add H264 support for the VDPU381 variant Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 15/17] media: rkvdec: Add H264 support for the VDPU383 variant Detlev Casanova
2026-01-21 14:27 ` kernel test robot
2026-01-21 14:46 ` Nicolas Dufresne [this message]
2026-01-21 23:04 ` Nathan Chancellor
2026-01-20 22:20 ` [PATCH v9 16/17] media: rkvdec: Add HEVC support for the VDPU381 variant Detlev Casanova
2026-01-20 22:20 ` [PATCH v9 17/17] media: rkvdec: Add HEVC support for the VDPU383 variant Detlev Casanova
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=69fda4f0136285e4d2f86e7e93d5bdd812c1d47a.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=corbet@lwn.net \
--cc=daniel.almeida@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=didi.debian@cknow.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hansg@kernel.org \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=james.cowgill@blaize.com \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=opensource206@gmail.com \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=yunkec@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®