Re: [PATCH v2 0/2] Fix a bunch of allmodconfig errors

2022-11-27 Thread Lee Jones
On Fri, 25 Nov 2022, Andrew Morton wrote: > On Fri, 25 Nov 2022 12:07:48 + Lee Jones wrote: > > > Since b339ec9c229aa ("kbuild: Only default to -Werror if COMPILE_TEST") > > WERROR > > now defaults to COMPILE_TEST meaning that it's enabled for allmodconfig > > > > builds. This le

[PATCH v3] drm: Optimise for continuous memory allocation

2022-11-27 Thread xinhui pan
Currently drm-buddy does not have full knowledge of continuous memory. Lets consider scenario below. order 1:L R order 0: LL LR RL RR for order 1 allocation, it can offer L or R or LR+RL. For now, we only implement L or R case for continuous memory allocation. So t

Re: [PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

2022-11-27 Thread Arunpravin Paneer Selvam
Hi Christian, Looks good to me. Reviewed-by: Arunpravin Paneer Selvam for the series. Regards, Arun. On 11/25/2022 3:51 PM, Christian König wrote: We already fallback to a dummy BO with no backing store when we allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. Drop all thos

Re: [PATCH v2 2/2] Kconfig.debug: Provide a little extra FRAME_WARN leeway when KASAN is enabled

2022-11-27 Thread Nathan Chancellor
On Fri, Nov 25, 2022 at 12:07:50PM +, Lee Jones wrote: > When enabled, KASAN enlarges function's stack-frames. Pushing quite a > few over the current threshold. This can mainly be seen on 32-bit > architectures where the present limit (when !GCC) is a lowly > 1024-Bytes. > > Signed-off-by: L

Re: [PATCH v2 1/2] drm/amdgpu: Temporarily disable broken Clang builds due to blown stack-frame

2022-11-27 Thread Nathan Chancellor
On Fri, Nov 25, 2022 at 12:07:49PM +, Lee Jones wrote: > calculate_bandwidth() is presently broken on all !(X86_64 || SPARC64 || ARM64) > architectures built with Clang (all released versions), whereby the stack > frame gets blown up to well over 5k. This would cause an immediate kernel > pani