Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Fu Hao <fuhao@open-hieco.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	0day robot <lkp@intel.com>
Subject: arch/x86/kernel/cpu/microcode/hygon.c:343:42: error: use of undeclared identifier 'hypervisor_present'; did you mean 'x86_hypervisor_present'?
Date: Tue, 16 Jun 2026 02:22:34 +0200	[thread overview]
Message-ID: <202606160254.dKPf3HDp-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Fu-Hao/x86-cpu-hygon-Adjust-the-die_id-and-logical_die_id-for-Hygon-models-0x4-through-0x8/20260615-203418
head:   1d23a5cab2f87c46644839ad70174c6dec28882d
commit: f0def51fc06432aa3420f72e2d81e82892868813 x86/microcode/hygon: Add microcode loading support for Hygon processors
date:   12 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260616/202606160254.dKPf3HDp-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260616/202606160254.dKPf3HDp-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/202606160254.dKPf3HDp-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/x86/kernel/cpu/microcode/hygon.c:343:42: error: use of undeclared identifier 'hypervisor_present'; did you mean 'x86_hypervisor_present'?
     343 |         if (IS_ENABLED(CONFIG_MICROCODE_DBG) && hypervisor_present)
         |                                                 ^~~~~~~~~~~~~~~~~~
         |                                                 x86_hypervisor_present
   arch/x86/include/asm/processor.h:736:13: note: 'x86_hypervisor_present' declared here
     736 | extern bool x86_hypervisor_present;
         |             ^
   1 error generated.


vim +343 arch/x86/kernel/cpu/microcode/hygon.c

   327	
   328	static bool apply_hygon_patch(struct hygon_microcode *mc, u32 *cur_rev,
   329					  unsigned int patch_size)
   330	{
   331		unsigned long patch_start = (unsigned long)&mc->header.data;
   332		unsigned long patch_end = patch_start + patch_size - 1;
   333	
   334		native_wrmsrq(HYGON_MSR_PATCH_LOADER, patch_start);
   335		invlpg(patch_start);
   336	
   337		/*
   338		 * Invalidate the next page if the patch image crosses a page boundary.
   339		 */
   340		if (hygon_pages_crossed(patch_start, patch_size))
   341			invlpg(patch_end);
   342	
 > 343		if (IS_ENABLED(CONFIG_MICROCODE_DBG) && hypervisor_present)
   344			microcode_rev[smp_processor_id()] = mc->header.patch_level;
   345	
   346		*cur_rev = get_current_patch_level();
   347	
   348		ucode_dbg("updated rev: 0x%x\n", *cur_rev);
   349	
   350		return *cur_rev == mc->header.patch_level;
   351	}
   352	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-06-16  0:22 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=202606160254.dKPf3HDp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=fuhao@open-hieco.net \
    --cc=llvm@lists.linux.dev \
    --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