From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: mjc@sifive.com, patches@groups.riscv.org, palmer@sifive.com
Subject: [Qemu-devel] [PATCH for-2.12 0/2] RISC-V: Mark FP status dirty
Date: Wed, 28 Mar 2018 10:22:31 +0800 [thread overview]
Message-ID: <20180328022233.13400-1-richard.henderson@linaro.org> (raw)
Since it was my patch that broke FP state tracking in the
first place, I feel obligated to fix it again.
Mark mstatus[fs] as dirty whenever we write to the file.
This can be optimized by only doing so once within a TB
which initially began with a clean file.
I have not yet put together an environment that can test
this, so I'll need someone else to give it a go.
r~
Richard Henderson (2):
target/riscv: Split out mstatus_fs from tb_flags during translation
target/riscv: Mark MSTATUS_FS dirty
target/riscv/cpu.h | 6 +++---
target/riscv/op_helper.c | 25 ++++++++++++++++--------
target/riscv/translate.c | 50 ++++++++++++++++++++++++++++++++++++++++++------
3 files changed, 64 insertions(+), 17 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-28 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 2:22 Richard Henderson [this message]
2018-03-28 2:22 ` [Qemu-devel] [PATCH 1/2] target/riscv: Split out mstatus_fs from tb_flags during translation Richard Henderson
2018-03-28 20:48 ` Michael Clark
2018-03-28 2:22 ` [Qemu-devel] [PATCH 2/2] target/riscv: Mark MSTATUS_FS dirty Richard Henderson
2018-03-28 4:58 ` Richard Henderson
2018-03-28 17:36 ` Michael Clark
2018-03-28 17:47 ` Michael Clark
2018-03-28 20:50 ` Michael Clark
2018-03-28 4:54 ` [Qemu-devel] [PATCH for-2.12 0/2] RISC-V: Mark FP status dirty Michael Clark
2018-03-28 17:58 ` Michael Clark
2018-04-03 7:46 ` Richard W.M. Jones
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=20180328022233.13400-1-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
--cc=qemu-devel@nongnu.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).