qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: fred.konrad@greensocs.com
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, fred.konrad@greensocs.com,
	mark.burton@greensocs.com, Pavel.Dovgaluk@ispras.ru,
	peter.maydell@linaro.org
Subject: [Qemu-devel] [RFC V7 04/10] icount: make icount extra computed on icount clock as well.
Date: Wed, 17 Sep 2014 10:26:44 +0200	[thread overview]
Message-ID: <1410942410-32604-5-git-send-email-fred.konrad@greensocs.com> (raw)
In-Reply-To: <1410942410-32604-1-git-send-email-fred.konrad@greensocs.com>

From: KONRAD Frederic <fred.konrad@greensocs.com>

This takes icount clock in account for icount extra computation so icount
clock's timers will be triggered at the exact time.

Signed-off-by: KONRAD Frederic <fred.konrad@greensocs.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
---
 cpus.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/cpus.c b/cpus.c
index 2e9e2ea..834d8b9 100644
--- a/cpus.c
+++ b/cpus.c
@@ -1325,6 +1325,7 @@ static int tcg_cpu_exec(CPUArchState *env)
     if (use_icount) {
         int64_t count;
         int64_t deadline;
+        int64_t icount_deadline;
         int decr;
         timers_state.qemu_icount -= (cpu->icount_decr.u16.low
                                     + cpu->icount_extra);
@@ -1341,6 +1342,15 @@ static int tcg_cpu_exec(CPUArchState *env)
             deadline = INT32_MAX;
         }
 
+        /*
+         * Take icount clock deadline in account too, and keep the nearest
+         * deadline.
+         */
+        icount_deadline = qemu_clock_deadline_ns_all(QEMU_CLOCK_ICOUNT);
+        if ((icount_deadline >= 0) && (icount_deadline < deadline)) {
+            deadline = icount_deadline;
+        }
+
         count = qemu_icount_round(deadline);
         timers_state.qemu_icount += count;
         decr = (count > 0xffff) ? 0xffff : count;
-- 
1.9.0

  parent reply	other threads:[~2014-09-17  8:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17  8:26 [Qemu-devel] [RFC V7 00/10] Reverse execution fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 01/10] migration: make qemu_savevm_state public fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 02/10] icount: introduce icount timer fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 03/10] icount: check for icount clock deadline when cpu loop exits fred.konrad
2014-09-17  8:26 ` fred.konrad [this message]
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 05/10] trace-events: add reverse-execution events fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 06/10] introduce reverse execution mechanism fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 07/10] gdbstub: allow reverse execution in gdb stub fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 08/10] cpu-exec: trigger a debug request when rexec stops fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 09/10] rexec: synchronize icount on the next event fred.konrad
2014-09-17  8:26 ` [Qemu-devel] [RFC V7 10/10] rexec: allow to enable reverse execution fred.konrad

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=1410942410-32604-5-git-send-email-fred.konrad@greensocs.com \
    --to=fred.konrad@greensocs.com \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=mark.burton@greensocs.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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).