From: Sang, Oliver <oliver.sang@intel.com>
To: lkp@lists.01.org
Subject: Re: [KVM] a5202946dc: kernel-selftests.kvm.make_fail
Date: Mon, 13 Jun 2022 07:26:51 +0000 [thread overview]
Message-ID: <d16188160405497a9ea9b206e4178730@intel.com> (raw)
In-Reply-To: <SA2PR11MB50525D04633E934148F8132781AB9@SA2PR11MB5052.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3926 bytes --]
Hi Chenyi,
> From: Qiang, Chenyi <chenyi.qiang@intel.com>
> Sent: Monday, June 13, 2022 12:02 PM
>
> Hi Oliver
>
> I found this issue is already fixed by Sean in queue branch. Thanks for your
> testing and report.
Thanks a lot for information!
>
> Thanks
> Chenyi
>
> -----Original Message-----
> From: Sang, Oliver <oliver.sang@intel.com>
> Sent: Monday, June 13, 2022 9:27 AM
> To: Qiang, Chenyi <chenyi.qiang@intel.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>; Christopherson,, Sean
> <seanjc@google.com>; LKML <linux-kernel@vger.kernel.org>;
> kvm(a)vger.kernel.org; Hu, Robert <robert.hu@intel.com>; Chen, Farrah
> <farrah.chen@intel.com>; Wei, Danmei <danmei.wei@intel.com>;
> lkp(a)lists.01.org; lkp <lkp@intel.com>; Hao, Xudong <xudong.hao@intel.com>
> Subject: [KVM] a5202946dc: kernel-selftests.kvm.make_fail
>
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: a5202946dc7b20bf2abe1bd35adf2f46aa155ac0 ("KVM: selftests: Add a
> test to get/set triple fault event") https://git.kernel.org/cgit/virt/kvm/kvm.git
> lbr-for-weijiang
>
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-d889b151-1_20220608
> with following parameters:
>
> group: kvm
> ucode: 0xec
>
> test-description: The kernel contains a set of "self tests" under the
> tools/testing/selftests/ directory. These are intended to be small unit tests to
> exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz with 28G
> memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire
> log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
>
>
>
> gcc -Wall -Wstrict-prototypes -Wuninitialized -O2 -g -std=gnu99 -fno-stack-
> protector -fno-PIE -I../../../../tools/include -I../../../../tools/arch/x86/include -
> I../../../../usr/include/ -Iinclude -Ix86_64 -Iinclude/x86_64 -I.. -pthread -no-pie
> x86_64/triple_fault_event_test.c /usr/src/perf_selftests-x86_64-rhel-8.3-
> kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm/libk
> vm.a -o /usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm/x86
> _64/triple_fault_event_test
> x86_64/triple_fault_event_test.c: In function ‘main’:
> x86_64/triple_fault_event_test.c:50:10: error:
> ‘KVM_CAP_TRIPLE_FAULT_EVENT’ undeclared (first use in this function); did you
> mean ‘KVM_CAP_X86_TRIPLE_FAULT_EVENT’?
> 50 | .cap = KVM_CAP_TRIPLE_FAULT_EVENT,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> | KVM_CAP_X86_TRIPLE_FAULT_EVENT
> x86_64/triple_fault_event_test.c:50:10: note: each undeclared identifier is
> reported only once for each function it appears in
> make: *** [../lib.mk:152: /usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm/x86
> _64/triple_fault_event_test] Error 1
> make: Leaving directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm'
>
>
>
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> sudo bin/lkp install job.yaml # job file is attached in this email
> bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
> sudo bin/lkp run generated-yaml-file
>
> # if come across any failure that blocks the test,
> # please remove ~/.lkp and /lkp dir to run from a clean state.
>
>
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Sang, Oliver" <oliver.sang@intel.com>
To: "Qiang, Chenyi" <chenyi.qiang@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, "Christopherson,,
Sean" <seanjc@google.com>, LKML <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Hu, Robert" <robert.hu@intel.com>,
"Chen, Farrah" <farrah.chen@intel.com>,
"Wei, Danmei" <danmei.wei@intel.com>,
"lkp@lists.01.org" <lkp@lists.01.org>, lkp <lkp@intel.com>,
"Hao, Xudong" <xudong.hao@intel.com>
Subject: RE: [KVM] a5202946dc: kernel-selftests.kvm.make_fail
Date: Mon, 13 Jun 2022 07:26:51 +0000 [thread overview]
Message-ID: <d16188160405497a9ea9b206e4178730@intel.com> (raw)
In-Reply-To: <SA2PR11MB50525D04633E934148F8132781AB9@SA2PR11MB5052.namprd11.prod.outlook.com>
Hi Chenyi,
> From: Qiang, Chenyi <chenyi.qiang@intel.com>
> Sent: Monday, June 13, 2022 12:02 PM
>
> Hi Oliver
>
> I found this issue is already fixed by Sean in queue branch. Thanks for your
> testing and report.
Thanks a lot for information!
>
> Thanks
> Chenyi
>
> -----Original Message-----
> From: Sang, Oliver <oliver.sang@intel.com>
> Sent: Monday, June 13, 2022 9:27 AM
> To: Qiang, Chenyi <chenyi.qiang@intel.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>; Christopherson,, Sean
> <seanjc@google.com>; LKML <linux-kernel@vger.kernel.org>;
> kvm@vger.kernel.org; Hu, Robert <robert.hu@intel.com>; Chen, Farrah
> <farrah.chen@intel.com>; Wei, Danmei <danmei.wei@intel.com>;
> lkp@lists.01.org; lkp <lkp@intel.com>; Hao, Xudong <xudong.hao@intel.com>
> Subject: [KVM] a5202946dc: kernel-selftests.kvm.make_fail
>
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: a5202946dc7b20bf2abe1bd35adf2f46aa155ac0 ("KVM: selftests: Add a
> test to get/set triple fault event") https://git.kernel.org/cgit/virt/kvm/kvm.git
> lbr-for-weijiang
>
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-d889b151-1_20220608
> with following parameters:
>
> group: kvm
> ucode: 0xec
>
> test-description: The kernel contains a set of "self tests" under the
> tools/testing/selftests/ directory. These are intended to be small unit tests to
> exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz with 28G
> memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire
> log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
>
>
>
> gcc -Wall -Wstrict-prototypes -Wuninitialized -O2 -g -std=gnu99 -fno-stack-
> protector -fno-PIE -I../../../../tools/include -I../../../../tools/arch/x86/include -
> I../../../../usr/include/ -Iinclude -Ix86_64 -Iinclude/x86_64 -I.. -pthread -no-pie
> x86_64/triple_fault_event_test.c /usr/src/perf_selftests-x86_64-rhel-8.3-
> kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm/libk
> vm.a -o /usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm/x86
> _64/triple_fault_event_test
> x86_64/triple_fault_event_test.c: In function ‘main’:
> x86_64/triple_fault_event_test.c:50:10: error:
> ‘KVM_CAP_TRIPLE_FAULT_EVENT’ undeclared (first use in this function); did you
> mean ‘KVM_CAP_X86_TRIPLE_FAULT_EVENT’?
> 50 | .cap = KVM_CAP_TRIPLE_FAULT_EVENT,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> | KVM_CAP_X86_TRIPLE_FAULT_EVENT
> x86_64/triple_fault_event_test.c:50:10: note: each undeclared identifier is
> reported only once for each function it appears in
> make: *** [../lib.mk:152: /usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm/x86
> _64/triple_fault_event_test] Error 1
> make: Leaving directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-
> a5202946dc7b20bf2abe1bd35adf2f46aa155ac0/tools/testing/selftests/kvm'
>
>
>
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> sudo bin/lkp install job.yaml # job file is attached in this email
> bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
> sudo bin/lkp run generated-yaml-file
>
> # if come across any failure that blocks the test,
> # please remove ~/.lkp and /lkp dir to run from a clean state.
>
>
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
>
next prev parent reply other threads:[~2022-06-13 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 1:26 [KVM] a5202946dc: kernel-selftests.kvm.make_fail kernel test robot
2022-06-13 1:26 ` kernel test robot
2022-06-13 4:02 ` Qiang, Chenyi
2022-06-13 4:02 ` Qiang, Chenyi
2022-06-13 7:26 ` Sang, Oliver [this message]
2022-06-13 7:26 ` Sang, Oliver
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=d16188160405497a9ea9b206e4178730@intel.com \
--to=oliver.sang@intel.com \
--cc=lkp@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.