From: kernel test robot <lkp@intel.com>
To: Mukul Joshi <mukul.joshi@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alex Deucher <alexander.deucher@amd.com>,
Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>
Subject: [linux-next:master 753/2369] drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:834:5: error: stack frame size (1124) exceeds limit (1024) in 'amdgpu_amdkfd_unmap_hiq'
Date: Thu, 13 Jul 2023 22:57:08 +0800 [thread overview]
Message-ID: <202307132214.zi4xL3jo-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e3262265625831348cfb3128d35907ead75d8bf7
commit: 9041b53a59d77039c69fa61be8575fa232cd3bcd [753/2369] drm/amdkfd: Use KIQ to unmap HIQ
config: i386-buildonly-randconfig-r004-20230713 (https://download.01.org/0day-ci/archive/20230713/202307132214.zi4xL3jo-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230713/202307132214.zi4xL3jo-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/202307132214.zi4xL3jo-lkp@intel.com/
Note: the linux-next/master HEAD e3262265625831348cfb3128d35907ead75d8bf7 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:834:5: error: stack frame size (1124) exceeds limit (1024) in 'amdgpu_amdkfd_unmap_hiq' [-Werror,-Wframe-larger-than]
int amdgpu_amdkfd_unmap_hiq(struct amdgpu_device *adev, u32 doorbell_off,
^
1 error generated.
vim +/amdgpu_amdkfd_unmap_hiq +834 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
833
> 834 int amdgpu_amdkfd_unmap_hiq(struct amdgpu_device *adev, u32 doorbell_off,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-13 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202307132214.zi4xL3jo-lkp@intel.com \
--to=lkp@intel.com \
--cc=Harish.Kasiviswanathan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=mukul.joshi@amd.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