From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 213257] New: KVM-PR: FPU is broken when single-stepping
Date: Fri, 28 May 2021 11:20:22 +0000 [thread overview]
Message-ID: <bug-213257-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213257
Bug ID: 213257
Summary: KVM-PR: FPU is broken when single-stepping
Product: Virtualization
Version: unspecified
Kernel Version: 5.6
Hardware: PPC-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: cand@gmx.com
Regression: No
The FPU is completely broken when single-stepping on KVM-PR. Registers stay
zeroes, computation results are zeroes. If I disable single-stepping,
computation results are correct, but of course then I cannot dump FPRs between
every instruction.
HW is POWER9, 18-core Talos II.
5.6 is slightly old, but there are no commits under arch/powerpc/kvm since that
mention single stepping.
Program:
https://git.libre-soc.org/?p=kvm-minippc.git;a=summary
Test file:
https://ftp.libre-soc.org/mini-float-test-kvm.bin
Repro instructions:
git clone https://git.libre-soc.org/git/kvm-minippc.git
cd kvm-minippc
make
wget https://ftp.libre-soc.org/mini-float-test-kvm.bin
./kvm-minippc -i mini-float-test-kvm.bin -t trace
less trace
# you will see FPRs stay zeroes. In larger test programs that dump the computed
memory, that is wrong too (all zero).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-05-28 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 11:20 bugzilla-daemon [this message]
2021-05-31 10:28 ` [Bug 213257] KVM-PR: FPU is broken when single-stepping bugzilla-daemon
2021-06-01 0:12 ` bugzilla-daemon
2021-06-01 7:35 ` bugzilla-daemon
2021-06-01 12:34 ` bugzilla-daemon
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=bug-213257-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.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 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.