From: Leon Alrae <leon.alrae@imgtec.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, aurelien@aurel32.net, macro@linux-mips.org,
quintela@redhat.com
Subject: [Qemu-devel] [PATCH 2/2] target-mips: add missing MSA and correct FP in VMState
Date: Wed, 18 Feb 2015 14:51:55 +0000 [thread overview]
Message-ID: <1424271115-7885-3-git-send-email-leon.alrae@imgtec.com> (raw)
In-Reply-To: <1424271115-7885-1-git-send-email-leon.alrae@imgtec.com>
Correct the structure and store MSA and FP flush_to_zero.
Signed-off-by: Leon Alrae <leon.alrae@imgtec.com>
---
target-mips/machine.c | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/target-mips/machine.c b/target-mips/machine.c
index 8d75962..c08e593 100644
--- a/target-mips/machine.c
+++ b/target-mips/machine.c
@@ -6,15 +6,23 @@
static int get_fpr(QEMUFile *f, void *pv, size_t size)
{
+ int i;
fpr_t *v = pv;
- qemu_get_be64s(f, &v->d);
+ /* Restore entire MSA vector register */
+ for (i = 0; i < MSA_WRLEN/64; i++) {
+ qemu_get_sbe64s(f, &v->wr.d[i]);
+ }
return 0;
}
static void put_fpr(QEMUFile *f, void *pv, size_t size)
{
+ int i;
fpr_t *v = pv;
- qemu_put_be64s(f, &v->d);
+ /* Save entire MSA vector register */
+ for (i = 0; i < MSA_WRLEN/64; i++) {
+ qemu_put_sbe64s(f, &v->wr.d[i]);
+ }
}
const VMStateInfo vmstate_info_fpr = {
@@ -31,7 +39,7 @@ const VMStateInfo vmstate_info_fpr = {
static VMStateField vmstate_fpu_fields[] = {
VMSTATE_FPR_ARRAY(fpr, CPUMIPSFPUContext, 32),
- VMSTATE_INT8(fp_status.float_detect_tininess, CPUMIPSFPUContext),
+ VMSTATE_UINT8(fp_status.flush_to_zero, CPUMIPSFPUContext),
VMSTATE_INT8(fp_status.float_rounding_mode, CPUMIPSFPUContext),
VMSTATE_INT8(fp_status.float_exception_flags, CPUMIPSFPUContext),
VMSTATE_UINT32(fcr0, CPUMIPSFPUContext),
@@ -70,6 +78,11 @@ static VMStateField vmstate_tc_fields[] = {
VMSTATE_UINTTL(CP0_TCScheFBack, TCState),
VMSTATE_INT32(CP0_Debug_tcstatus, TCState),
VMSTATE_UINTTL(CP0_UserLocal, TCState),
+ VMSTATE_INT32(msacsr, TCState),
+ VMSTATE_INT8(msa_fp_status.float_rounding_mode, TCState),
+ VMSTATE_INT8(msa_fp_status.float_exception_flags, TCState),
+ VMSTATE_UINT8(msa_fp_status.flush_to_zero, TCState),
+ VMSTATE_UINT8(msa_fp_status.flush_inputs_to_zero, TCState),
VMSTATE_END_OF_LIST()
};
@@ -183,8 +196,8 @@ const VMStateDescription vmstate_tlb = {
const VMStateDescription vmstate_mips_cpu = {
.name = "cpu",
- .version_id = 5,
- .minimum_version_id = 5,
+ .version_id = 6,
+ .minimum_version_id = 6,
.fields = (VMStateField[]) {
/* active TC */
VMSTATE_STRUCT(env.active_tc, MIPSCPU, 1, vmstate_tc, TCState),
--
2.1.0
next prev parent reply other threads:[~2015-02-18 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 14:51 [Qemu-devel] [PATCH 0/2] target-mips: port MIPS CPU to VMState Leon Alrae
2015-02-18 14:51 ` [Qemu-devel] [PATCH 1/2] target-mips: replace cpu_save/cpu_load with VMStateDescription Leon Alrae
2015-02-18 16:59 ` Andreas Färber
2015-02-19 10:23 ` Leon Alrae
2015-02-18 14:51 ` Leon Alrae [this message]
2015-02-19 15:43 ` [Qemu-devel] [PATCH 2/2] target-mips: add missing MSA and correct FP in VMState Richard Henderson
2015-02-19 16:43 ` Leon Alrae
2015-02-20 13:12 ` Maciej W. Rozycki
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=1424271115-7885-3-git-send-email-leon.alrae@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=amit.shah@redhat.com \
--cc=aurelien@aurel32.net \
--cc=macro@linux-mips.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).