All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 218168] amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes
Date: Tue, 21 Nov 2023 16:41:35 +0000	[thread overview]
Message-ID: <bug-218168-2300-JqmZfiejHf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218168-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218168

--- Comment #5 from Felix Kuehling (felix.kuehling@amd.com) ---
There are two patches that didn't make it into Linux 6.6 that reduce the 
stack size in kfd_topology_add_device. Can you check if those fix the 
problem?

commit aa5a9b2ccda2fa834fddb4bd30a2ab831598f551
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Tue Sep 26 12:00:23 2023 -0400

     drm/amdkfd: drop struct kfd_cu_info

     I think this was an abstraction back from when
     kfd supported both radeon and amdgpu.  Since we just
     support amdgpu now, there is no more need for this and
     we can use the amdgpu structures directly.

     This also avoids having the kfd_cu_info structures on
     the stack when inlining which can blow up the stack.

     Cc: Arnd Bergmann <arnd@kernel.org>
     Acked-by: Arnd Bergmann <arnd@arndb.de>
     Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
     Acked-by: Christian König <christian.koenig@amd.com>
     Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 1f3b515578a1d73926993629a06a7f3b60535b59
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Thu Sep 21 10:32:09 2023 -0400

     drm/amdkfd: reduce stack size in kfd_topology_add_device()

     kfd_topology.c:2082:1: warning: the frame size of 1440 bytes is larger
than 1024 bytes

     Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2866
     Cc: Arnd Bergmann <arnd@kernel.org>
     Acked-by: Arnd Bergmann <arnd@arndb.de>
     Acked-by: Christian König <christian.koenig@amd.com>
     Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
     Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

Regards,
   Felix


On 2023-11-20 10:36, Hamza Mahfooz wrote:
> + amd-gfx
> + Felix
>
> On 11/20/23 10:16, bugzilla-daemon@kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=218168
>>
>>              Bug ID: 218168
>>             Summary: amdgpu: kfd_topology.c warning: the frame size 
>> of 1408
>>                      bytes is larger than 1024 bytes
>>             Product: Drivers
>>             Version: 2.5
>>            Hardware: All
>>                  OS: Linux
>>              Status: NEW
>>            Severity: normal
>>            Priority: P3
>>           Component: Video(DRI - non Intel)
>>            Assignee: drivers_video-dri@kernel-bugs.osdl.org
>>            Reporter: bluesun654@gmail.com
>>          Regression: No
>>
>> Trying to compile Linux 6.6.2 with GCC 13.2.1 and CONFIG_WERROR=y:
>>
>> [...]
>> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: In function
>> 'kfd_topology_add_device':
>> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c:2082:1: error: 
>> the frame
>> size of 1408 bytes is larger than 1024 bytes 
>> [-Werror=frame-larger-than=]
>>   2082 | }
>>        | ^
>> cc1: all warnings being treated as errors
>> [...]
>>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2023-11-21 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 15:16 [Bug 218168] New: amdgpu: kfd_topology.c warning: the frame size of 1408 bytes is larger than 1024 bytes bugzilla-daemon
2023-11-20 15:36 ` Hamza Mahfooz
2023-11-21 16:41   ` Felix Kuehling
2023-11-20 15:36 ` [Bug 218168] " bugzilla-daemon
2023-11-20 18:01 ` bugzilla-daemon
2023-11-20 19:50 ` bugzilla-daemon
2023-11-21 13:50 ` bugzilla-daemon
2023-11-21 13:50 ` bugzilla-daemon
2023-11-21 16:41 ` bugzilla-daemon [this message]

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=bug-218168-2300-JqmZfiejHf@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.