[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <286D4C7E-EB26-4BBD-8E8A-F638E201983A@zytor.com>
Date: Fri, 6 Feb 2026 01:34:08 -0800
From: Xin Li <xin@...or.com>
To: "Nikunj A. Dadhania" <nikunj@....com>
Cc: kernel test robot <lkp@...el.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, bp@...en8.de, thomas.lendacky@....com,
llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev, tglx@...nel.org,
mingo@...hat.com, dave.hansen@...ux.intel.com, hpa@...or.com,
seanjc@...gle.com, pbonzini@...hat.com, x86@...nel.org,
jon.grimm@....com, stable@...r.kernel.org
Subject: Re: [PATCH] x86/fred: Fix early boot failures on SEV-ES/SNP guests
> On Feb 5, 2026, at 7:31 PM, Nikunj A. Dadhania <nikunj@....com> wrote:
>
> if (user_mode(regs))
> return user_exc_vmm_communication(regs, error_code);
> else
> return kernel_exc_vmm_communication(regs, error_code);
Please rewrite this piece of code, like how X86_TRAP_DB is handled today.
Should kernel #VC be handled at a higher level RSP? You can check FRED #DB settings.
Powered by blists - more mailing lists