From: eady <eady@wisc.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Saving and restoring CPU state
Date: Thu, 12 Apr 2007 11:16:35 -0500 [thread overview]
Message-ID: <461E5B63.8040906@wisc.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
I'm still looking for any suggestions on how to save and restore the
target cpu state from within a custom instruction in op.c. I basically
want a custom instruction to save the cpu state to a data structure and
then continue on normally, a second custom instruction would then be
used to restore the cpu state from the saved data structure at a later
time thereby rolling back the execution of the cpu. I've tried saving
and restoring env->eip within my custom instructions but this has no effect.
Thanks,
Nuri
[-- Attachment #2: [Qemu-devel] Saving and restoring CPU state --]
[-- Type: message/rfc822, Size: 4385 bytes --]
From: eady <eady@wisc.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Saving and restoring CPU state
Date: Sun, 08 Apr 2007 16:38:14 -0500
Message-ID: <461960C6.8010904@wisc.edu>
I'm experimenting a bit with QEMU and am in need of a way to save and
restore X86 CPU state including the pc so that the processor state can
be rolled back to re execute from the previous point. I've found the
functions "cpu_x86_fsave" and "cpu_restore_state" but do not understand
them well enough to use them. Does anyone have tips on how to store the
processor state in an auxiliary data structure and then restore it at a
later point?
Thanks
Nuri
next reply other threads:[~2007-04-12 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 16:16 eady [this message]
2007-04-18 21:11 ` [Qemu-devel] Saving and restoring CPU state Rob Landley
2007-04-18 22:12 ` andrzej zaborowski
-- strict thread matches above, loose matches on Subject: below --
2007-04-08 21:38 eady
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=461E5B63.8040906@wisc.edu \
--to=eady@wisc.edu \
--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).