From: Sean Christopherson <seanjc@google.com>
To: Srikanth Aithal <sraithal@amd.com>
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: KVM Unit Test Suite Regression on AMD EPYC Turin (Zen 5)
Date: Tue, 8 Jul 2025 13:57:43 -0700 [thread overview]
Message-ID: <aG2GRzQPMM3tmMZc@google.com> (raw)
In-Reply-To: <f156887a-a747-455f-a06e-9029ba58b8cc@amd.com>
On Tue, Jul 08, 2025, Srikanth Aithal wrote:
> Hello all,
> KVM unit test suite for SVM is regressing on the AMD EPYC Turin platform
> (Zen 5) for a while now, even on latest linux-next[https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tag/?h=
> next-20250704]. The same seem to work fine with linux-next tag
> next-20250505.
> The TSC delay test fails intermittently (approximately once in three runs)
> with an unexpected result (expected: 50, actual: 49). This test passed
> consistently on earlier tags (e.g., next-20250505) and on non-Turin
> platforms.
Stating the obvious to some extent, I suspect it's something to do with Turin,
not a KVM issue. This fails on our Turin hosts as far back as v6.12, i.e. long
before next-20250505 (I haven't bothered checking earlier builds), and AFAICT
the KUT test isn't doing anything to actually stress KVM itself. I.e. I would
expect KVM bugs to manifest as blatant, 100% reproducible failures, not random
TSC slop.
FAIL: tsc delay (expected: 50, actual: 49)
SUMMARY: 13 tests, 1 unexpected failures
✘ ~/build/kut/x86 # uname -r
6.12.0-smp--adc218676eef-tsc
next prev parent reply other threads:[~2025-07-08 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 5:01 KVM Unit Test Suite Regression on AMD EPYC Turin (Zen 5) Aithal, Srikanth
2025-07-08 20:57 ` Sean Christopherson [this message]
2025-07-24 3:59 ` Jim Mattson
2025-11-18 22:29 ` Sean Christopherson
2025-11-18 22:38 ` 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=aG2GRzQPMM3tmMZc@google.com \
--to=seanjc@google.com \
--cc=kvm@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 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.