mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: "Pillai, Aurabindo" <Aurabindo.Pillai@amd.com>
Cc: "Zhuo, Lillian" <Qingqing.Zhuo@amd.com>,
	Alexander Lobakin <aleksander.lobakin@intel.com>,
	kernel test robot <lkp@intel.com>,
	"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Siqueira, Rodrigo" <Rodrigo.Siqueira@amd.com>,
	"Li, Roman" <Roman.Li@amd.com>
Subject: Re: drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6193:12: warning: stack frame size (3368) exceeds limit (2048) in 'dml_core_mode_support'
Date: Wed, 7 Feb 2024 11:09:36 +0800	[thread overview]
Message-ID: <ZcL0cH1LZteapnTG@yujie-X299> (raw)
In-Reply-To: <CH0PR12MB52845186C7D747A4547DA99A8B462@CH0PR12MB5284.namprd12.prod.outlook.com>

On Tue, Feb 06, 2024 at 04:18:55PM +0000, Pillai, Aurabindo wrote:
> [AMD Official Use Only - General]
> 
> Hi,
> 
> I tried with LLVM16 (from Manjaro) and couldnt repro the issue on both mainline and amd-staging-drm-next. Could someone share the config used for this build ?

Hi,

There is a "reproduce" link in the original report. Hope it would be
helpful:

reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231120/202311200955.pmjdQEM1-lkp@intel.com/reproduce)

For a quick check, please kindly try the following steps to reproduce
the issue:

$ git checkout v6.8-rc3
$ wget https://download.01.org/0day-ci/archive/20231120/202311200955.pmjdQEM1-lkp@intel.com/config -O .config
$ make W=1 LLVM=1 ARCH=x86_64 olddefconfig
$ make -j$(nproc) W=1 LLVM=1 ARCH=x86_64 drivers/gpu/drm/amd/amdgpu/
...
drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6710:12: warning: stack frame size (3368) exceeds limit (3072) in 'dml_core_mode_support' [-Wframe-larger-than]
dml_bool_t dml_core_mode_support(struct display_mode_lib_st *mode_lib)
           ^

Best Regards,
Yujie

> 
> --
> 
> Regards,
> Jay
> ________________________________
> From: Zhuo, Lillian <Qingqing.Zhuo@amd.com>
> Sent: Tuesday, February 6, 2024 11:06 AM
> To: Alexander Lobakin <aleksander.lobakin@intel.com>; Pillai, Aurabindo <Aurabindo.Pillai@amd.com>
> Cc: kernel test robot <lkp@intel.com>; oe-kbuild-all@lists.linux.dev <oe-kbuild-all@lists.linux.dev>; linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>; Deucher, Alexander <Alexander.Deucher@amd.com>; Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com>; Li, Roman <Roman.Li@amd.com>
> Subject: RE: drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6193:12: warning: stack frame size (3368) exceeds limit (2048) in 'dml_core_mode_support'
> 
> [AMD Official Use Only - General]
> 
> + Jay, who is looking into the issue
> 
> -----Original Message-----
> From: Alexander Lobakin <aleksander.lobakin@intel.com>
> Sent: Tuesday, February 6, 2024 8:20 AM
> To: Zhuo, Lillian <Qingqing.Zhuo@amd.com>
> Cc: kernel test robot <lkp@intel.com>; oe-kbuild-all@lists.linux.dev; linux-kernel@vger.kernel.org; Deucher, Alexander <Alexander.Deucher@amd.com>; Siqueira, Rodrigo <Rodrigo.Siqueira@amd.com>; Li, Roman <Roman.Li@amd.com>
> Subject: Re: drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:6193:12: warning: stack frame size (3368) exceeds limit (2048) in 'dml_core_mode_support'
> 
> From: Kernel Test Robot <lkp@intel.com>
> Date: Mon, 20 Nov 2023 10:01:21 +0800
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   037266a5f7239ead1530266f7d7af153d2a867fa
> > commit: 7966f319c66d9468623c6a6a017ecbc0dd79be75 drm/amd/display: Introduce DML2
> > date:   6 weeks ago
> > config: x86_64-randconfig-121-20231119
> > (https://download.01.org/0day-ci/archive/20231120/202311200955.pmjdQEM
> > 1-lkp@intel.com/config)
> > compiler: clang version 16.0.4
> > (https://github.com/llvm/llvm-project.git
> > ae42196bc493ffe877a7e3dff8be32035dea4d07)
> > reproduce (this is a W=1 build):
> > (https://download.01.org/0day-ci/archive/20231120/202311200955.pmjdQEM
> > 1-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/202311200955.pmjdQEM1-lkp@inte
> > | l.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> >    warning: unknown warning option '-Wstringop-truncation'; did you mean '-Wstring-concatenation'? [-Wunknown-warning-option]
> >    warning: unknown warning option '-Wpacked-not-aligned'; did you
> > mean '-Wpacked-non-pod'? [-Wunknown-warning-option]
> >>> drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:61
> >>> 93:12: warning: stack frame size (3368) exceeds limit (2048) in
> >>> 'dml_core_mode_support' [-Wframe-larger-than]
> >    dml_bool_t dml_core_mode_support(struct display_mode_lib_st
> > *mode_lib)
> 
> Ping? This still happens on the latest RC and linux-next on LLVM 19 at least (-O2) and breaks CONFIG_WERROR builds.
> 
> >               ^
> >    2183/3368 (64.82%) spills, 1185/3368 (35.18%) variables
> >    drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.c:8241:6: warning: stack frame size (2232) exceeds limit (2048) in 'dml_core_mode_programming' [-Wframe-larger-than]
> >    void dml_core_mode_programming(struct display_mode_lib_st *mode_lib, const struct dml_clk_cfg_st *clk_cfg)
> >         ^
> >    1441/2232 (64.56%) spills, 791/2232 (35.44%) variables
> >    4 warnings generated.
> Thanks,
> Olek

  parent reply	other threads:[~2024-02-07  3:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  2:01 kernel test robot
2024-02-06 13:20 ` Alexander Lobakin
2024-02-06 16:06   ` Zhuo, Lillian
     [not found]     ` <CH0PR12MB52845186C7D747A4547DA99A8B462@CH0PR12MB5284.namprd12.prod.outlook.com>
2024-02-07  3:09       ` Yujie Liu [this message]
2024-02-07 12:18         ` Alexander Lobakin
     [not found]           ` <CH0PR12MB5284F7B96B16E8F86E4740CD8B452@CH0PR12MB5284.namprd12.prod.outlook.com>
2024-04-17 11:15             ` Alexander Lobakin

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=ZcL0cH1LZteapnTG@yujie-X299 \
    --to=yujie.liu@intel.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Aurabindo.Pillai@amd.com \
    --cc=Qingqing.Zhuo@amd.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=Roman.Li@amd.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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®