From: kernel test robot <lkp@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [kas:lam 10/10] arch/x86/kernel/proc.c:35:24: error: 'X86_THREAD_LAM_U48' undeclared; did you mean 'X86_CR3_LAM_U48'?
Date: Thu, 7 Apr 2022 16:54:39 +0800 [thread overview]
Message-ID: <202204071610.T6fPhCnP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git lam
head: 73447e771c55e18598a6fbf6adee1002aee18ea0
commit: 73447e771c55e18598a6fbf6adee1002aee18ea0 [10/10] x86: Expose thread features status in /proc/$PID/arch_status
config: i386-randconfig-a001 (https://download.01.org/0day-ci/archive/20220407/202204071610.T6fPhCnP-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git/commit/?id=73447e771c55e18598a6fbf6adee1002aee18ea0
git remote add kas https://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git
git fetch --no-tags kas lam
git checkout 73447e771c55e18598a6fbf6adee1002aee18ea0
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
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 >>):
arch/x86/kernel/proc.c: In function 'dump_features':
>> arch/x86/kernel/proc.c:35:24: error: 'X86_THREAD_LAM_U48' undeclared (first use in this function); did you mean 'X86_CR3_LAM_U48'?
35 | if (features & X86_THREAD_LAM_U48)
| ^~~~~~~~~~~~~~~~~~
| X86_CR3_LAM_U48
arch/x86/kernel/proc.c:35:24: note: each undeclared identifier is reported only once for each function it appears in
>> arch/x86/kernel/proc.c:37:24: error: 'X86_THREAD_LAM_U57' undeclared (first use in this function); did you mean 'X86_CR3_LAM_U57'?
37 | if (features & X86_THREAD_LAM_U57)
| ^~~~~~~~~~~~~~~~~~
| X86_CR3_LAM_U57
vim +35 arch/x86/kernel/proc.c
32
33 static void dump_features(struct seq_file *m, unsigned long features)
34 {
> 35 if (features & X86_THREAD_LAM_U48)
36 seq_puts(m, "lam_u48 ");
> 37 if (features & X86_THREAD_LAM_U57)
38 seq_puts(m, "lam_u57 ");
39 }
40
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-07 8:55 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=202204071610.T6fPhCnP-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kirill.shutemov@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox