kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 213257] KVM-PR: FPU is broken when single-stepping
Date: Tue, 01 Jun 2021 12:34:08 +0000	[thread overview]
Message-ID: <bug-213257-28872-U5TLIcEUPx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213257-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=213257

--- Comment #4 from Luke Kenneth Casson Leighton (lkcl@lkcl.net) ---
(In reply to Lauri Kasanen from comment #3)
> That's probably not worth trying, since the computation results were
> also wrong.

ok. and the initial setup starts from a blank FPU, no host modification of FPRs
needed

> The computation does not rely on register setting, it
> loads, computes and saves entirely in code.

i realised i just said this exact thing, above, in a different way.

and is it the case that the minippc kvm host program is not attempting to read
(or write) the FPR regfile after each guest singlestep?

not that i would expect reading of the FPR regfile from the host to affect the
guest, but it's worth confirming.

trying to think, how else can this be debugged, to find out what's going on?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2021-06-01 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 11:20 [Bug 213257] New: KVM-PR: FPU is broken when single-stepping bugzilla-daemon
2021-05-31 10:28 ` [Bug 213257] " bugzilla-daemon
2021-06-01  0:12 ` bugzilla-daemon
2021-06-01  7:35 ` bugzilla-daemon
2021-06-01 12:34 ` bugzilla-daemon [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=bug-213257-28872-U5TLIcEUPx@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 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).