From: kernel test robot <lkp@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, kbusch@kernel.org,
chang.seok.bae@intel.com
Subject: Re: [PATCH 07/10] KVM: emulate: add AVX support to register fetch and writeback
Date: Sat, 15 Nov 2025 04:10:44 +0800 [thread overview]
Message-ID: <202511150213.HaLLVfkt-lkp@intel.com> (raw)
In-Reply-To: <20251114003633.60689-8-pbonzini@redhat.com>
Hi Paolo,
kernel test robot noticed the following build errors:
[auto build test ERROR on v6.18-rc5]
[also build test ERROR on linus/master next-20251114]
[cannot apply to kvm/queue kvm/next mst-vhost/linux-next kvm/linux-next]
[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/Paolo-Bonzini/KVM-emulate-add-MOVNTDQA/20251114-084216
base: v6.18-rc5
patch link: https://lore.kernel.org/r/20251114003633.60689-8-pbonzini%40redhat.com
patch subject: [PATCH 07/10] KVM: emulate: add AVX support to register fetch and writeback
config: i386-buildonly-randconfig-006-20251114 (https://download.01.org/0day-ci/archive/20251115/202511150213.HaLLVfkt-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251115/202511150213.HaLLVfkt-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/202511150213.HaLLVfkt-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/x86/kvm/fpu.h: Assembler messages:
>> arch/x86/kvm/fpu.h:37: Error: bad register name `%ymm14'
>> arch/x86/kvm/fpu.h:36: Error: bad register name `%ymm13'
>> arch/x86/kvm/fpu.h:38: Error: bad register name `%ymm15'
>> arch/x86/kvm/fpu.h:35: Error: bad register name `%ymm12'
>> arch/x86/kvm/fpu.h:34: Error: bad register name `%ymm11'
>> arch/x86/kvm/fpu.h:33: Error: bad register name `%ymm10'
>> arch/x86/kvm/fpu.h:32: Error: bad register name `%ymm9'
>> arch/x86/kvm/fpu.h:31: Error: bad register name `%ymm8'
arch/x86/kvm/fpu.h:58: Error: bad register name `%ymm12'
arch/x86/kvm/fpu.h:59: Error: bad register name `%ymm13'
arch/x86/kvm/fpu.h:54: Error: bad register name `%ymm8'
arch/x86/kvm/fpu.h:55: Error: bad register name `%ymm9'
arch/x86/kvm/fpu.h:56: Error: bad register name `%ymm10'
arch/x86/kvm/fpu.h:57: Error: bad register name `%ymm11'
arch/x86/kvm/fpu.h:61: Error: bad register name `%ymm15'
arch/x86/kvm/fpu.h:60: Error: bad register name `%ymm14'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for I2C_K1
Depends on [n]: I2C [=y] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && OF [=n]
Selected by [y]:
- MFD_SPACEMIT_P1 [=y] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && I2C [=y]
vim +37 arch/x86/kvm/fpu.h
19
20 static inline void _kvm_read_avx_reg(int reg, avx256_t *data)
21 {
22 switch (reg) {
23 case 0: asm("vmovdqa %%ymm0, %0" : "=m"(*data)); break;
24 case 1: asm("vmovdqa %%ymm1, %0" : "=m"(*data)); break;
25 case 2: asm("vmovdqa %%ymm2, %0" : "=m"(*data)); break;
26 case 3: asm("vmovdqa %%ymm3, %0" : "=m"(*data)); break;
27 case 4: asm("vmovdqa %%ymm4, %0" : "=m"(*data)); break;
28 case 5: asm("vmovdqa %%ymm5, %0" : "=m"(*data)); break;
29 case 6: asm("vmovdqa %%ymm6, %0" : "=m"(*data)); break;
30 case 7: asm("vmovdqa %%ymm7, %0" : "=m"(*data)); break;
> 31 case 8: asm("vmovdqa %%ymm8, %0" : "=m"(*data)); break;
> 32 case 9: asm("vmovdqa %%ymm9, %0" : "=m"(*data)); break;
> 33 case 10: asm("vmovdqa %%ymm10, %0" : "=m"(*data)); break;
> 34 case 11: asm("vmovdqa %%ymm11, %0" : "=m"(*data)); break;
> 35 case 12: asm("vmovdqa %%ymm12, %0" : "=m"(*data)); break;
> 36 case 13: asm("vmovdqa %%ymm13, %0" : "=m"(*data)); break;
> 37 case 14: asm("vmovdqa %%ymm14, %0" : "=m"(*data)); break;
> 38 case 15: asm("vmovdqa %%ymm15, %0" : "=m"(*data)); break;
39 default: BUG();
40 }
41 }
42
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-14 20:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 0:36 [PATCH 00/10] KVM: emulate: enable AVX moves Paolo Bonzini
2025-11-14 0:36 ` [PATCH 01/10] KVM: emulate: add MOVNTDQA Paolo Bonzini
2025-11-14 0:36 ` [PATCH 02/10] KVM: emulate: move Src2Shift up one bit Paolo Bonzini
2025-11-17 19:51 ` Chang S. Bae
2025-11-14 0:36 ` [PATCH 03/10] KVM: emulate: improve formatting of flags table Paolo Bonzini
2025-11-17 19:53 ` Chang S. Bae
2025-11-14 0:36 ` [PATCH 04/10] KVM: emulate: move op_prefix to struct x86_emulate_ctxt Paolo Bonzini
2025-11-17 19:54 ` Chang S. Bae
2025-11-14 0:36 ` [PATCH 05/10] KVM: emulate: share common register decoding code Paolo Bonzini
2025-11-17 19:55 ` Chang S. Bae
2025-11-14 0:36 ` [PATCH 06/10] KVM: emulate: add get_xcr callback Paolo Bonzini
2025-11-17 19:56 ` Chang S. Bae
2025-11-14 0:36 ` [PATCH 07/10] KVM: emulate: add AVX support to register fetch and writeback Paolo Bonzini
2025-11-14 17:06 ` kernel test robot
2025-11-14 20:10 ` kernel test robot [this message]
2025-11-14 0:36 ` [PATCH 08/10] KVM: x86: Refactor REX prefix handling in instruction emulation Paolo Bonzini
2025-11-17 19:56 ` Chang S. Bae
2025-11-14 0:36 ` [PATCH 09/10] KVM: emulate: decode VEX prefix Paolo Bonzini
2025-11-14 0:36 ` [PATCH 10/10] KVM: emulate: enable AVX moves Paolo Bonzini
2025-11-14 0:51 ` [PATCH 00/10] " Keith Busch
2025-11-17 19:57 ` Chang S. Bae
2025-11-21 18:55 ` Sean Christopherson
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=202511150213.HaLLVfkt-lkp@intel.com \
--to=lkp@intel.com \
--cc=chang.seok.bae@intel.com \
--cc=kbusch@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
/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