From: Sean Christopherson <seanjc@google.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: Hang when booting guest kernels compiled with clang after SRSO mitigations
Date: Fri, 11 Aug 2023 09:03:18 -0700 [thread overview]
Message-ID: <ZNZbxhL5ZJD1Sd9P@google.com> (raw)
In-Reply-To: <20230811140941.GB193223@dev-arch.thelio-3990X>
On Fri, Aug 11, 2023, Nathan Chancellor wrote:
> On Fri, Aug 11, 2023 at 12:14:56PM +0200, Borislav Petkov wrote:
> > On Thu, Aug 10, 2023 at 09:14:14AM -0700, Nathan Chancellor wrote:
> > > Not sure how helpful that will be...
> >
> > Yeah, not really. More wild guesses: if you uncomment the UNTRAIN_RET in
> > __svm_vcpu_run() on the host, does that have any effect? Diff below.
>
> Unfortunately, that seems to make no difference...
>
> I did have to switch to the Ryzen 3 box for testing, as I am not at home
> for a couple of days and I did not want to lose access to my workstation
> if I took a bad update since it has no remote management capabilities.
> Something I noticed in doing so is that the VM boot on that machine
> appears to get farther along than on my Threadripper 3990X, but I still
> see a hang with a stack trace similar to the one that I reported in the
> initial post with '-smp 2', so I think it is the same problem but
> perhaps the more cores the VM has, the more likely it is to appear
> totally hung? Might be a red herring but I figured I would mention it in
> case it is relevant.
Might be the flags bug that borks KVM's fastop() emulation. If that fixes things,
my guess is that bringing APs out of WFS somehow triggers emulation.
https://lore.kernel.org/all/20230811155255.250835-1-seanjc@google.com
next prev parent reply other threads:[~2023-08-11 16:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 1:33 Hang when booting guest kernels compiled with clang after SRSO mitigations Nathan Chancellor
2023-08-10 8:10 ` Borislav Petkov
2023-08-10 9:08 ` Borislav Petkov
2023-08-10 9:15 ` Borislav Petkov
2023-08-10 10:16 ` Nathan Chancellor
2023-08-10 12:51 ` Borislav Petkov
2023-08-10 13:27 ` Nathan Chancellor
2023-08-10 13:32 ` Borislav Petkov
2023-08-10 13:40 ` Nathan Chancellor
2023-08-10 14:43 ` Borislav Petkov
2023-08-10 15:07 ` Nathan Chancellor
2023-08-10 15:14 ` Borislav Petkov
2023-08-10 15:48 ` Nathan Chancellor
2023-08-10 16:14 ` Nathan Chancellor
2023-08-11 10:14 ` Borislav Petkov
2023-08-11 14:09 ` Nathan Chancellor
2023-08-11 16:03 ` Sean Christopherson [this message]
2023-08-11 16:12 ` Borislav Petkov
2023-08-12 0:42 ` Nick Desaulniers
2023-08-12 13:46 ` Borislav Petkov
2023-08-12 14:31 ` Nathan Chancellor
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=ZNZbxhL5ZJD1Sd9P@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox