From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [tglx-devel:x86/topology 9/37] arch/x86/kernel/cpu/mce/inject.c:437:28: error: no member named 'topo' in 'struct cpuinfo_topology'
Date: Tue, 4 Jul 2023 21:06:47 +0800 [thread overview]
Message-ID: <202307042007.RqEO152e-lkp@intel.com> (raw)
Hi Thomas,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git x86/topology
head: 53cee0c91c9944ef2e6b784edaea5df7d6ba5648
commit: 1f177511c113ba6edd3963a1a52180f6df4845b1 [9/37] x86/cpu: Move x86_max_cores into topology info
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230704/202307042007.RqEO152e-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230704/202307042007.RqEO152e-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/202307042007.RqEO152e-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kernel/cpu/mce/inject.c:437:28: error: no member named 'topo' in 'struct cpuinfo_topology'
cores_per_node = (c->topo.topo.num_cores_per_pkg * smp_num_siblings) /
~~~~~~~ ^
1 error generated.
vim +437 arch/x86/kernel/cpu/mce/inject.c
431
432 static u32 get_nbc_for_node(int node_id)
433 {
434 struct cpuinfo_x86 *c = &boot_cpu_data;
435 u32 cores_per_node;
436
> 437 cores_per_node = (c->topo.topo.num_cores_per_pkg * smp_num_siblings) /
438 amd_get_nodes_per_socket();
439
440 return cores_per_node * node_id;
441 }
442
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-04 13:06 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=202307042007.RqEO152e-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
/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.