From: kernel test robot <lkp@intel.com>
To: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:61:17: error: implicit declaration of function 'enable_kernel_altivec'; did you mean 'enable_kernel_vsx'?
Date: Mon, 21 Feb 2022 00:43:51 +0800 [thread overview]
Message-ID: <202202210016.gEpMVmsL-lkp@intel.com> (raw)
Hi Rodrigo,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4f12b742eb2b3a850ac8be7dc4ed52976fc6cb0b
commit: 96ee63730fa30614e943ac352ef772be49a712d9 drm/amd/display: Add control mechanism for FPU
date: 7 months ago
config: powerpc64-randconfig-r023-20220220 (https://download.01.org/0day-ci/archive/20220221/202202210016.gEpMVmsL-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=96ee63730fa30614e943ac352ef772be49a712d9
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 96ee63730fa30614e943ac352ef772be49a712d9
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash drivers/gpu/drm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c: In function 'dc_fpu_begin':
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:61:17: error: implicit declaration of function 'enable_kernel_altivec'; did you mean 'enable_kernel_vsx'? [-Werror=implicit-function-declaration]
61 | enable_kernel_altivec();
| ^~~~~~~~~~~~~~~~~~~~~
| enable_kernel_vsx
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c: In function 'dc_fpu_end':
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:89:17: error: implicit declaration of function 'disable_kernel_altivec'; did you mean 'disable_kernel_vsx'? [-Werror=implicit-function-declaration]
89 | disable_kernel_altivec();
| ^~~~~~~~~~~~~~~~~~~~~~
| disable_kernel_vsx
cc1: some warnings being treated as errors
vim +61 drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c
35
36 /**
37 * dc_fpu_begin - Enables FPU protection
38 * @function_name: A string containing the function name for debug purposes
39 * (usually __func__)
40 *
41 * @line: A line number where DC_FP_START was invoked for debug purpose
42 * (usually __LINE__)
43 *
44 * This function is responsible for managing the use of kernel_fpu_begin() with
45 * the advantage of providing an event trace for debugging.
46 *
47 * Note: Do not call this function directly; always use DC_FP_START().
48 */
49 void dc_fpu_begin(const char *function_name, const int line)
50 {
51 TRACE_DCN_FPU(true, function_name, line);
52
53 #if defined(CONFIG_X86)
54 kernel_fpu_begin();
55 #elif defined(CONFIG_PPC64)
56 if (cpu_has_feature(CPU_FTR_VSX_COMP)) {
57 preempt_disable();
58 enable_kernel_vsx();
59 } else if (cpu_has_feature(CPU_FTR_ALTIVEC_COMP)) {
60 preempt_disable();
> 61 enable_kernel_altivec();
62 } else if (!cpu_has_feature(CPU_FTR_FPU_UNAVAILABLE)) {
63 preempt_disable();
64 enable_kernel_fp();
65 }
66 #endif
67 }
68
69 /**
70 * dc_fpu_end - Disable FPU protection
71 * @function_name: A string containing the function name for debug purposes
72 * @line: A-line number where DC_FP_END was invoked for debug purpose
73 *
74 * This function is responsible for managing the use of kernel_fpu_end() with
75 * the advantage of providing an event trace for debugging.
76 *
77 * Note: Do not call this function directly; always use DC_FP_END().
78 */
79 void dc_fpu_end(const char *function_name, const int line)
80 {
81 TRACE_DCN_FPU(false, function_name, line);
82 #if defined(CONFIG_X86)
83 kernel_fpu_end();
84 #elif defined(CONFIG_PPC64)
85 if (cpu_has_feature(CPU_FTR_VSX_COMP)) {
86 disable_kernel_vsx();
87 preempt_enable();
88 } else if (cpu_has_feature(CPU_FTR_ALTIVEC_COMP)) {
> 89 disable_kernel_altivec();
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-02-20 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 16:43 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-21 16:11 drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:61:17: error: implicit declaration of function 'enable_kernel_altivec'; did you mean 'enable_kernel_vsx'? kernel test robot
2022-04-21 18:33 kernel test robot
2022-03-31 12:39 kernel test robot
2022-03-20 8:05 kernel test robot
2022-02-11 22:04 kernel test robot
2022-02-11 22:04 ` kernel test robot
2022-01-09 0:14 kernel test robot
2022-01-09 0:14 ` kernel test robot
2021-11-15 21:15 kernel test robot
2021-11-15 21:15 ` kernel test robot
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=202202210016.gEpMVmsL-lkp@intel.com \
--to=lkp@intel.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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.