From: kernel test robot <lkp@intel.com>
To: Mukul Joshi <mukul.joshi@amd.com>
Cc: 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 698/1391] drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:868:1: error: the frame size of 1168 bytes is larger than 1024 bytes
Date: Tue, 11 Jul 2023 12:22:18 +0800 [thread overview]
Message-ID: <202307111250.GzpYxUtH-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: fe57d0d86f03a8b2afe2869a95477d0ed1824c96
commit: 9041b53a59d77039c69fa61be8575fa232cd3bcd [698/1391] drm/amdkfd: Use KIQ to unmap HIQ
config: microblaze-randconfig-r003-20230710 (https://download.01.org/0day-ci/archive/20230711/202307111250.GzpYxUtH-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230711/202307111250.GzpYxUtH-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/202307111250.GzpYxUtH-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c: In function 'amdgpu_amdkfd_unmap_hiq':
>> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:868:1: error: the frame size of 1168 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
868 | }
| ^
cc1: all warnings being treated as errors
vim +868 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
833
834 int amdgpu_amdkfd_unmap_hiq(struct amdgpu_device *adev, u32 doorbell_off,
835 u32 inst)
836 {
837 struct amdgpu_kiq *kiq = &adev->gfx.kiq[inst];
838 struct amdgpu_ring *kiq_ring = &kiq->ring;
839 struct amdgpu_ring_funcs ring_funcs;
840 struct amdgpu_ring ring;
841 int r = 0;
842
843 if (!kiq->pmf || !kiq->pmf->kiq_unmap_queues)
844 return -EINVAL;
845
846 memset(&ring, 0x0, sizeof(struct amdgpu_ring));
847 memset(&ring_funcs, 0x0, sizeof(struct amdgpu_ring_funcs));
848
849 ring_funcs.type = AMDGPU_RING_TYPE_COMPUTE;
850 ring.doorbell_index = doorbell_off;
851 ring.funcs = &ring_funcs;
852
853 spin_lock(&kiq->ring_lock);
854
855 if (amdgpu_ring_alloc(kiq_ring, kiq->pmf->unmap_queues_size)) {
856 spin_unlock(&kiq->ring_lock);
857 return -ENOMEM;
858 }
859
860 kiq->pmf->kiq_unmap_queues(kiq_ring, &ring, RESET_QUEUES, 0, 0);
861
862 if (kiq_ring->sched.ready && !adev->job_hang)
863 r = amdgpu_ring_test_helper(kiq_ring);
864
865 spin_unlock(&kiq->ring_lock);
866
867 return r;
> 868 }
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-11 4:22 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=202307111250.GzpYxUtH-lkp@intel.com \
--to=lkp@intel.com \
--cc=Harish.Kasiviswanathan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=linux-mm@kvack.org \
--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