From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3] x86/speculation/l1tf: Add KConfig for setting the L1D cache flush mode
Date: Fri, 03 Jul 2020 22:14:26 +0800 [thread overview]
Message-ID: <202007032120.itetSOdJ%lkp@intel.com> (raw)
In-Reply-To: <20200702221237.2517080-1-abhishekbh@google.com>
[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]
Hi Abhishek,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/auto-latest]
[also build test WARNING on linux/master tip/x86/core kvm/linux-next linus/master v5.8-rc3 next-20200703]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Abhishek-Bhardwaj/x86-speculation-l1tf-Add-KConfig-for-setting-the-L1D-cache-flush-mode/20200703-061509
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 7e44a91e0445a854af5d34ca0f5baceccd518e73
config: i386-randconfig-a004-20200701 (attached as .config)
compiler: gcc-6 (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/cpu/bugs.c:1402:6: warning: "CONFIG_KVM_VMENTRY_L1D_FLUSH" is not defined [-Wundef]
#if (CONFIG_KVM_VMENTRY_L1D_FLUSH == 1)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kernel/cpu/bugs.c:1404:8: warning: "CONFIG_KVM_VMENTRY_L1D_FLUSH" is not defined [-Wundef]
#elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 2)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kernel/cpu/bugs.c:1406:8: warning: "CONFIG_KVM_VMENTRY_L1D_FLUSH" is not defined [-Wundef]
#elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 3)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/CONFIG_KVM_VMENTRY_L1D_FLUSH +1402 arch/x86/kernel/cpu/bugs.c
1396
1397 /* Default mitigation for L1TF-affected CPUs */
1398 enum l1tf_mitigations l1tf_mitigation __ro_after_init = L1TF_MITIGATION_FLUSH;
1399 #if IS_ENABLED(CONFIG_KVM_INTEL)
1400 EXPORT_SYMBOL_GPL(l1tf_mitigation);
1401 #endif
> 1402 #if (CONFIG_KVM_VMENTRY_L1D_FLUSH == 1)
1403 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_NEVER;
1404 #elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 2)
1405 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_COND;
1406 #elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 3)
1407 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_ALWAYS;
1408 #else
1409 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_AUTO;
1410 #endif
1411 EXPORT_SYMBOL_GPL(l1tf_vmx_mitigation);
1412
---
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: 31323 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Abhishek Bhardwaj <abhishekbh@google.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: kbuild-all@lists.01.org,
Abhishek Bhardwaj <abhishekbh@google.com>,
Anthony Steinhauser <asteinhauser@google.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@redhat.com>, Jim Mattson <jmattson@google.com>,
Joerg Roedel <joro@8bytes.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Mark Gross <mgross@linux.intel.com>
Subject: Re: [PATCH v3] x86/speculation/l1tf: Add KConfig for setting the L1D cache flush mode
Date: Fri, 3 Jul 2020 22:14:26 +0800 [thread overview]
Message-ID: <202007032120.itetSOdJ%lkp@intel.com> (raw)
In-Reply-To: <20200702221237.2517080-1-abhishekbh@google.com>
[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]
Hi Abhishek,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/auto-latest]
[also build test WARNING on linux/master tip/x86/core kvm/linux-next linus/master v5.8-rc3 next-20200703]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Abhishek-Bhardwaj/x86-speculation-l1tf-Add-KConfig-for-setting-the-L1D-cache-flush-mode/20200703-061509
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 7e44a91e0445a854af5d34ca0f5baceccd518e73
config: i386-randconfig-a004-20200701 (attached as .config)
compiler: gcc-6 (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/cpu/bugs.c:1402:6: warning: "CONFIG_KVM_VMENTRY_L1D_FLUSH" is not defined [-Wundef]
#if (CONFIG_KVM_VMENTRY_L1D_FLUSH == 1)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kernel/cpu/bugs.c:1404:8: warning: "CONFIG_KVM_VMENTRY_L1D_FLUSH" is not defined [-Wundef]
#elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 2)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kernel/cpu/bugs.c:1406:8: warning: "CONFIG_KVM_VMENTRY_L1D_FLUSH" is not defined [-Wundef]
#elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 3)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/CONFIG_KVM_VMENTRY_L1D_FLUSH +1402 arch/x86/kernel/cpu/bugs.c
1396
1397 /* Default mitigation for L1TF-affected CPUs */
1398 enum l1tf_mitigations l1tf_mitigation __ro_after_init = L1TF_MITIGATION_FLUSH;
1399 #if IS_ENABLED(CONFIG_KVM_INTEL)
1400 EXPORT_SYMBOL_GPL(l1tf_mitigation);
1401 #endif
> 1402 #if (CONFIG_KVM_VMENTRY_L1D_FLUSH == 1)
1403 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_NEVER;
1404 #elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 2)
1405 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_COND;
1406 #elif (CONFIG_KVM_VMENTRY_L1D_FLUSH == 3)
1407 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_ALWAYS;
1408 #else
1409 enum vmx_l1d_flush_state l1tf_vmx_mitigation = VMENTER_L1D_FLUSH_AUTO;
1410 #endif
1411 EXPORT_SYMBOL_GPL(l1tf_vmx_mitigation);
1412
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31323 bytes --]
next prev parent reply other threads:[~2020-07-03 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 22:12 [PATCH v3] x86/speculation/l1tf: Add KConfig for setting the L1D cache flush mode Abhishek Bhardwaj
2020-07-02 23:16 ` Randy Dunlap
2020-07-03 0:17 ` Waiman Long
2020-07-03 3:17 ` Anthony Steinhauser
2020-07-03 6:43 ` Abhishek Bhardwaj
2020-07-03 11:40 ` Mike Rapoport
2020-07-03 14:00 ` Doug Anderson
2020-07-05 15:23 ` Mike Rapoport
2020-07-05 15:56 ` Waiman Long
2020-07-05 18:22 ` Abhishek Bhardwaj
2020-07-05 18:48 ` Waiman Long
2020-07-05 21:51 ` Abhishek Bhardwaj
[not found] ` <f8e84764-1cc7-c4e5-4e4f-4b907204a374@redhat.com>
2020-07-08 19:32 ` Abhishek Bhardwaj
2020-07-05 17:33 ` Doug Anderson
2020-07-03 14:14 ` kernel test robot [this message]
2020-07-03 14:14 ` kernel 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=202007032120.itetSOdJ%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.