mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alexey Makhalov <alexey.makhalov@broadcom.com>,
	linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
	bp@alien8.de, hpa@zytor.com, dave.hansen@linux.intel.com,
	mingo@redhat.com, tglx@linutronix.de
Cc: oe-kbuild-all@lists.linux.dev, x86@kernel.org,
	ajay.kaher@broadcom.com, bo.gan@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com,
	Alexey Makhalov <alexey.makhalov@broadcom.com>
Subject: Re: [PATCH 2/2] x86/vmware: Fix steal time clock under SEV
Date: Thu, 15 Aug 2024 20:51:22 +0800	[thread overview]
Message-ID: <202408152054.7LIuKvYe-lkp@intel.com> (raw)
In-Reply-To: <20240814210731.761010-2-alexey.makhalov@broadcom.com>

Hi Alexey,

kernel test robot noticed the following build errors:

[auto build test ERROR on tip/x86/vmware]
[also build test ERROR on linus/master v6.11-rc3 next-20240815]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Alexey-Makhalov/x86-vmware-Fix-steal-time-clock-under-SEV/20240815-050918
base:   tip/x86/vmware
patch link:    https://lore.kernel.org/r/20240814210731.761010-2-alexey.makhalov%40broadcom.com
patch subject: [PATCH 2/2] x86/vmware: Fix steal time clock under SEV
config: i386-randconfig-001-20240815 (https://download.01.org/0day-ci/archive/20240815/202408152054.7LIuKvYe-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240815/202408152054.7LIuKvYe-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/202408152054.7LIuKvYe-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/x86/kernel/cpu/vmware.c: In function 'sev_map_percpu_data':
>> arch/x86/kernel/cpu/vmware.c:313:13: error: 'cc_vendor' undeclared (first use in this function)
     313 |         if (cc_vendor != CC_VENDOR_AMD ||
         |             ^~~~~~~~~
   arch/x86/kernel/cpu/vmware.c:313:13: note: each undeclared identifier is reported only once for each function it appears in
>> arch/x86/kernel/cpu/vmware.c:313:26: error: 'CC_VENDOR_AMD' undeclared (first use in this function); did you mean 'X86_VENDOR_AMD'?
     313 |         if (cc_vendor != CC_VENDOR_AMD ||
         |                          ^~~~~~~~~~~~~
         |                          X86_VENDOR_AMD


vim +/cc_vendor +313 arch/x86/kernel/cpu/vmware.c

   308	
   309	static void __init sev_map_percpu_data(void)
   310	{
   311		int cpu;
   312	
 > 313		if (cc_vendor != CC_VENDOR_AMD ||
   314		    !cc_platform_has(CC_ATTR_GUEST_MEM_ENCRYPT))
   315			return;
   316	
   317		for_each_possible_cpu(cpu) {
   318			early_set_memory_decrypted(
   319				(unsigned long)&per_cpu(vmw_steal_time, cpu),
   320				sizeof(vmw_steal_time));
   321		}
   322	}
   323	

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

  parent reply	other threads:[~2024-08-15 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 21:07 [PATCH 1/2] x86/vmware: Log kmsg dump on panic Alexey Makhalov
2024-08-14 21:07 ` [PATCH 2/2] x86/vmware: Fix steal time clock under SEV Alexey Makhalov
2024-08-15 10:58   ` kernel test robot
2024-08-15 12:51   ` kernel test robot [this message]
2024-08-15 23:52   ` [PATCH v2 " Alexey Makhalov

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=202408152054.7LIuKvYe-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ajay.kaher@broadcom.com \
    --cc=alexey.makhalov@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bo.gan@broadcom.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=virtualization@lists.linux.dev \
    --cc=x86@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

all inboxes | Powered by JetHome®