From: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, quintela@redhat.com,
jasowang@redhat.com, mst@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH v6 1/9] icount: update instruction counter on apic patching
Date: Mon, 19 Dec 2016 16:21:11 +0300 [thread overview]
Message-ID: <20161219132111.3016.50241.stgit@PASHA-ISP> (raw)
In-Reply-To: <20161219132102.3016.46687.stgit@PASHA-ISP>
kvmvapic patches the code when some instructions are executed.
E.g. mov 0xff, 0xfffe0080 is interpreted as push 0xff/call ...
This patching is also followed by some side effects (changing apic
and guest memory state). Therefore deterministic execution should take
this operation into account. This patch decreases icount when original
mov instruction is trying to execute. Therefore patching becomes
deterministic and can be replayed correctly.
Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
---
hw/i386/kvmvapic.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/hw/i386/kvmvapic.c b/hw/i386/kvmvapic.c
index b30d1b9..146d47c 100644
--- a/hw/i386/kvmvapic.c
+++ b/hw/i386/kvmvapic.c
@@ -412,6 +412,12 @@ static void patch_instruction(VAPICROMState *s, X86CPU *cpu, target_ulong ip)
if (!kvm_enabled()) {
cpu_get_tb_cpu_state(env, ¤t_pc, ¤t_cs_base,
¤t_flags);
+ /* Account this instruction, because we will exit the tb.
+ This is the first instruction in the block. Therefore
+ there is no need in restoring CPU state. */
+ if (use_icount) {
+ --cs->icount_decr.u16.low;
+ }
}
pause_all_vcpus();
next prev parent reply other threads:[~2016-12-19 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 13:21 [Qemu-devel] [PATCH v6 0/9] replay additions Pavel Dovgalyuk
2016-12-19 13:21 ` Pavel Dovgalyuk [this message]
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 2/9] replay: improve interrupt handling Pavel Dovgalyuk
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 3/9] apic: save apic_delivered flag Pavel Dovgalyuk
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 4/9] replay: don't use rtc clock on loadvm phase Pavel Dovgalyuk
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 5/9] integratorcp: adding vmstate for save/restore Pavel Dovgalyuk
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 6/9] savevm: add public save_vmstate function Pavel Dovgalyuk
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 7/9] replay: save/load initial state Pavel Dovgalyuk
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 8/9] block: implement bdrv_snapshot_goto for blkreplay Pavel Dovgalyuk
2016-12-19 13:21 ` [Qemu-devel] [PATCH v6 9/9] blkreplay: create temporary overlay for underlaying devices Pavel Dovgalyuk
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=20161219132111.3016.50241.stgit@PASHA-ISP \
--to=pavel.dovgaluk@ispras.ru \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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).