From: Sean Christopherson <seanjc@google.com>
To: Srikanth Aithal <sraithal@amd.com>
Cc: kvm@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: next-20230809: kvm unittest fail: emulator
Date: Fri, 11 Aug 2023 07:30:25 -0700 [thread overview]
Message-ID: <ZNZGAVMYOEIlBnrv@google.com> (raw)
In-Reply-To: <fed6f74a-244a-ce07-0018-e6c26f594dd3@amd.com>
On Fri, Aug 11, 2023, Srikanth Aithal wrote:
> On 8/11/2023 4:15 AM, Sean Christopherson wrote:
> > On Thu, Aug 10, 2023, Srikanth Aithal wrote:
> > > Hello,
> > >
> > > On linux-next 20230809 build kvm emulator unittest failed.
> > >
> > > ===================
> > > Recreation steps:
> > > ===================
> > >
> > > 1. git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
> > > 2. export QEMU=<location of QEMU binary> I used v8.0.2
> > > 3. cd kvm-unit-tests/;./configure;make standalone;tests/emulator
> >
> > What hardware are you running on? I've tested on a variety of hardware, Intel
> > and AMD, and haven't observed any problems.
> I am running it on Dell PowerEdge r6515. Same tests were passing till
> next-20230808.
Ah, let me try an actual linux-next build (once I get the darn thing to compile).
I was assuming I broke something in kvm-x86/next and so was testing that. But I
haven't pushed to kvm-x86/next since 08/03, so presumably the bug came in from
somewhere else.
Ugh, it's probably one of the recent mitigations. Those things always break stuff
due to getting thrown in without going through the usual channels.
<time passes>
*sigh* Yep. Everything is hunky dory until I turn on CONFIG_CPU_SRSO. I'll dig
into it today.
prev parent reply other threads:[~2023-08-11 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 4:06 next-20230809: kvm unittest fail: emulator Aithal, Srikanth
2023-08-10 22:45 ` Sean Christopherson
2023-08-11 11:41 ` Aithal, Srikanth
2023-08-11 14:30 ` Sean Christopherson [this message]
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=ZNZGAVMYOEIlBnrv@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sraithal@amd.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;
as well as URLs for NNTP newsgroup(s).