From: kernel test robot <lkp@intel.com>
To: Nikunj A Dadhania <nikunj@amd.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org, bp@alien8.de,
thomas.lendacky@amd.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
tglx@kernel.org, mingo@redhat.com, dave.hansen@linux.intel.com,
hpa@zytor.com, xin@zytor.com, seanjc@google.com,
pbonzini@redhat.com, x86@kernel.org, jon.grimm@amd.com,
nikunj@amd.com, stable@vger.kernel.org
Subject: Re: [PATCH] x86/fred: Fix early boot failures on SEV-ES/SNP guests
Date: Thu, 5 Feb 2026 20:35:25 +0800 [thread overview]
Message-ID: <202602052054.J3CEkmKB-lkp@intel.com> (raw)
In-Reply-To: <20260205051030.1225975-1-nikunj@amd.com>
Hi Nikunj,
kernel test robot noticed the following build errors:
[auto build test ERROR on 3c2ca964f75460093a8aad6b314a6cd558e80e66]
url: https://github.com/intel-lab-lkp/linux/commits/Nikunj-A-Dadhania/x86-fred-Fix-early-boot-failures-on-SEV-ES-SNP-guests/20260205-131359
base: 3c2ca964f75460093a8aad6b314a6cd558e80e66
patch link: https://lore.kernel.org/r/20260205051030.1225975-1-nikunj%40amd.com
patch subject: [PATCH] x86/fred: Fix early boot failures on SEV-ES/SNP guests
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260205/202602052054.J3CEkmKB-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260205/202602052054.J3CEkmKB-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/202602052054.J3CEkmKB-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/entry/entry_fred.c:213:11: error: call to undeclared function 'user_exc_vmm_communication'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
213 | return user_exc_vmm_communication(regs, error_code);
| ^
arch/x86/entry/entry_fred.c:213:4: warning: void function 'fred_hwexc' should not return a value [-Wreturn-mismatch]
213 | return user_exc_vmm_communication(regs, error_code);
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/entry/entry_fred.c:215:11: error: call to undeclared function 'kernel_exc_vmm_communication'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
215 | return kernel_exc_vmm_communication(regs, error_code);
| ^
arch/x86/entry/entry_fred.c:215:4: warning: void function 'fred_hwexc' should not return a value [-Wreturn-mismatch]
215 | return kernel_exc_vmm_communication(regs, error_code);
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 warnings and 2 errors generated.
vim +/user_exc_vmm_communication +213 arch/x86/entry/entry_fred.c
180
181 static noinstr void fred_hwexc(struct pt_regs *regs, unsigned long error_code)
182 {
183 /* Optimize for #PF. That's the only exception which matters performance wise */
184 if (likely(regs->fred_ss.vector == X86_TRAP_PF))
185 return exc_page_fault(regs, error_code);
186
187 switch (regs->fred_ss.vector) {
188 case X86_TRAP_DE: return exc_divide_error(regs);
189 case X86_TRAP_DB: return fred_exc_debug(regs);
190 case X86_TRAP_BR: return exc_bounds(regs);
191 case X86_TRAP_UD: return exc_invalid_op(regs);
192 case X86_TRAP_NM: return exc_device_not_available(regs);
193 case X86_TRAP_DF: return exc_double_fault(regs, error_code);
194 case X86_TRAP_TS: return exc_invalid_tss(regs, error_code);
195 case X86_TRAP_NP: return exc_segment_not_present(regs, error_code);
196 case X86_TRAP_SS: return exc_stack_segment(regs, error_code);
197 case X86_TRAP_GP: return exc_general_protection(regs, error_code);
198 case X86_TRAP_MF: return exc_coprocessor_error(regs);
199 case X86_TRAP_AC: return exc_alignment_check(regs, error_code);
200 case X86_TRAP_XF: return exc_simd_coprocessor_error(regs);
201
202 #ifdef CONFIG_X86_MCE
203 case X86_TRAP_MC: return fred_exc_machine_check(regs);
204 #endif
205 #ifdef CONFIG_INTEL_TDX_GUEST
206 case X86_TRAP_VE: return exc_virtualization_exception(regs);
207 #endif
208 #ifdef CONFIG_X86_CET
209 case X86_TRAP_CP: return exc_control_protection(regs, error_code);
210 #endif
211 case X86_TRAP_VC:
212 if (user_mode(regs))
> 213 return user_exc_vmm_communication(regs, error_code);
214 else
> 215 return kernel_exc_vmm_communication(regs, error_code);
216 default: return fred_bad_type(regs, error_code);
217 }
218
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-05 12:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 5:10 [PATCH] x86/fred: Fix early boot failures on SEV-ES/SNP guests Nikunj A Dadhania
2026-02-05 5:55 ` Greg KH
2026-02-05 6:10 ` Nikunj A. Dadhania
2026-02-05 6:20 ` Greg KH
2026-02-05 15:50 ` Sean Christopherson
2026-02-05 15:58 ` Dave Hansen
2026-02-05 16:00 ` Greg KH
2026-02-05 5:56 ` Greg KH
2026-02-05 6:24 ` Nikunj A. Dadhania
2026-02-05 7:11 ` Xin Li
2026-02-05 8:54 ` Nikunj A. Dadhania
2026-02-05 14:34 ` Xin Li
2026-02-05 10:41 ` kernel test robot
2026-02-06 3:31 ` Nikunj A. Dadhania
2026-02-06 9:34 ` Xin Li
2026-02-05 12:24 ` kernel test robot
2026-02-05 12:35 ` kernel test robot [this message]
2026-02-05 16:10 ` Dave Hansen
2026-02-05 17:20 ` Dave Hansen
2026-02-05 17:39 ` Tom Lendacky
2026-02-06 12:38 ` Nikunj A. Dadhania
2026-02-16 5:16 ` Nikunj A. Dadhania
2026-02-16 17:10 ` Dave Hansen
2026-02-19 19:27 ` Sohil Mehta
2026-02-19 20:22 ` Dave Hansen
2026-02-19 20:50 ` Sohil Mehta
2026-02-05 17:39 ` H. Peter Anvin
2026-02-06 12:12 ` Nikunj A. Dadhania
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=202602052054.J3CEkmKB-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jon.grimm@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--cc=xin@zytor.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 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.