From: kernel test robot <lkp@intel.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v2 12/19] x86: Implement the Memory Table feature to store arbitrary per-page data
Date: Wed, 22 Nov 2023 15:19:27 +0800 [thread overview]
Message-ID: <202311221345.9sPNLiAU-lkp@intel.com> (raw)
In-Reply-To: <20231113022326.24388-13-mic@digikod.net>
Hi Mickaël,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on 881375a408c0f4ea451ff14545b59216d2923881]
url: https://github.com/intel-lab-lkp/linux/commits/Micka-l-Sala-n/virt-Introduce-Hypervisor-Enforced-Kernel-Integrity-Heki/20231113-102847
base: 881375a408c0f4ea451ff14545b59216d2923881
patch link: https://lore.kernel.org/r/20231113022326.24388-13-mic%40digikod.net
patch subject: [RFC PATCH v2 12/19] x86: Implement the Memory Table feature to store arbitrary per-page data
config: x86_64-randconfig-123-20231122 (https://download.01.org/0day-ci/archive/20231122/202311221345.9sPNLiAU-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231122/202311221345.9sPNLiAU-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/202311221345.9sPNLiAU-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/mem_table.c:47:14: sparse: sparse: symbol 'mem_table_base_level' was not declared. Should it be static?
>> kernel/mem_table.c:48:14: sparse: sparse: symbol 'mem_table_nlevels' was not declared. Should it be static?
>> kernel/mem_table.c:49:24: sparse: sparse: symbol 'mem_table_levels' was not declared. Should it be static?
vim +/mem_table_base_level +47 kernel/mem_table.c
42
43 /*
44 * Within this feature, the table levels start from 0. On X86, the base level
45 * is not 0.
46 */
> 47 unsigned int mem_table_base_level __ro_after_init;
> 48 unsigned int mem_table_nlevels __ro_after_init;
> 49 struct mem_table_level mem_table_levels[CONFIG_PGTABLE_LEVELS] __ro_after_init;
50
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2023-11-22 7:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231113022326.24388-13-mic@digikod.net>]
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=202311221345.9sPNLiAU-lkp@intel.com \
--to=lkp@intel.com \
--cc=mic@digikod.net \
--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;
as well as URLs for NNTP newsgroup(s).