All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC v2 4/4] X86: Use KVM CR pin MSRs
Date: Thu, 20 Feb 2020 17:10:23 +0800	[thread overview]
Message-ID: <202002201747.aUnCJ8u5%lkp@intel.com> (raw)
In-Reply-To: <20200218215902.5655-5-john.s.andersen@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2132 bytes --]

Hi John,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on kvm/linux-next]
[also build test ERROR on v5.6-rc2 next-20200219]
[cannot apply to tip/x86/core tip/auto-latest]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/John-Andersen/Paravirtualized-Control-Register-pinning/20200220-155307
base:   https://git.kernel.org/pub/scm/virt/kvm/kvm.git linux-next
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/x86/kernel/cpu/common.c: In function 'setup_cr_pinning':
>> arch/x86/kernel/cpu/common.c:421:2: error: implicit declaration of function 'kvm_setup_paravirt_cr_pinning'; did you mean 'setup_cr_pinning'? [-Werror=implicit-function-declaration]
     kvm_setup_paravirt_cr_pinning(X86_CR0_WP, cr4_pinned_bits);
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     setup_cr_pinning
   cc1: some warnings being treated as errors

vim +421 arch/x86/kernel/cpu/common.c

   407	
   408	/*
   409	 * Once CPU feature detection is finished (and boot params have been
   410	 * parsed), record any of the sensitive CR bits that are set, and
   411	 * enable CR pinning.
   412	 */
   413	static void __init setup_cr_pinning(void)
   414	{
   415		unsigned long mask;
   416	
   417		mask = (X86_CR4_SMEP | X86_CR4_SMAP | X86_CR4_UMIP);
   418		cr4_pinned_bits = this_cpu_read(cpu_tlbstate.cr4) & mask;
   419		static_key_enable(&cr_pinning.key);
   420	
 > 421		kvm_setup_paravirt_cr_pinning(X86_CR0_WP, cr4_pinned_bits);
   422	}
   423	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 7238 bytes --]

  reply	other threads:[~2020-02-20  9:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 21:58 [RFC v2 0/4] Paravirtualized Control Register pinning John Andersen
2020-02-18 21:58 ` [RFC v2 1/4] X86: Update mmu_cr4_features during identification John Andersen
2020-02-18 21:59 ` [RFC v2 2/4] KVM: X86: Add CR pin MSRs John Andersen
2020-03-03 21:35   ` Sean Christopherson
2020-02-18 21:59 ` [RFC v2 3/4] selftests: kvm: add test for CR pinning with SMM John Andersen
2020-02-24 15:50   ` Andrew Jones
2020-02-27  1:04     ` Andersen, John S
2020-02-18 21:59 ` [RFC v2 4/4] X86: Use KVM CR pin MSRs John Andersen
2020-02-20  9:10   ` kbuild test robot [this message]
2020-02-20 20:36   ` kbuild test robot

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=202002201747.aUnCJ8u5%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.