From: "Pavel Dovgaluk" <Pavel.Dovgaluk@ispras.ru>
To: 'Frederic Konrad' <fred.konrad@greensocs.com>,
'Paolo Bonzini' <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, peter.crosthwaite@xilinx.com,
alex.bennee@linaro.org, mark.burton@greensocs.com,
real@ispras.ru, batuzovk@ispras.ru,
maria.klimushenkova@ispras.ru, afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH v4 07/25] icount: implement icount requesting
Date: Tue, 11 Nov 2014 12:41:40 +0300 [thread overview]
Message-ID: <000c01cffd93$b2225cd0$16671670$@Dovgaluk@ispras.ru> (raw)
In-Reply-To: <545CB0C5.5080107@greensocs.com>
> From: Frederic Konrad [mailto:fred.konrad@greensocs.com]
> On 07/11/2014 12:36, Pavel Dovgaluk wrote:
> >> From: Paolo Bonzini [mailto:pbonzini@redhat.com]
> >> On 07/11/2014 11:32, Pavel Dovgalyuk wrote:
> >>> Replay uses number of executed instructions to determine corrent events
> >>> injection moments. This patch introduces new function for querying the
> >>> instructions counter.
> >>>
> >>> Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
> >>> ---
> >>> cpus.c | 26 +++++++++++++++++++++++---
> >>> include/qemu/timer.h | 1 +
> >>> 2 files changed, 24 insertions(+), 3 deletions(-)
> >>>
> >>> diff --git a/cpus.c b/cpus.c
> >>> index 7e8c507..2ec6d75 100644
> >>> --- a/cpus.c
> >>> +++ b/cpus.c
> >>> @@ -136,8 +136,7 @@ typedef struct TimersState {
> >>>
> >>> static TimersState timers_state;
> >>>
> >>> -/* Return the virtual CPU time, based on the instruction counter. */
> >>> -static int64_t cpu_get_icount_locked(void)
> >>> +static int64_t cpu_get_instructions_counter_locked(void)
> >>> {
> >>> int64_t icount;
> >>> CPUState *cpu = current_cpu;
> >>> @@ -145,10 +144,31 @@ static int64_t cpu_get_icount_locked(void)
> >>> icount = timers_state.qemu_icount;
> >>> if (cpu) {
> >>> if (!cpu_can_do_io(cpu)) {
> >>> - fprintf(stderr, "Bad clock read\n");
> >>> + fprintf(stderr, "Bad icount read\n");
> >>> + exit(1);
> >>> }
> >>> icount -= (cpu->icount_decr.u16.low + cpu->icount_extra);
> >>> }
> >>> + return icount;
> >>> +}
> >>> +
> >>> +int64_t cpu_get_instructions_counter(void)
> >>> +{
> >>> + /* This function calls are synchnonized to timer changes,
> >>> + calling cpu_get_instructions_counter_locked without lock is safe */
> >>> + int64_t icount = timers_state.qemu_icount;
> >>> + CPUState *cpu = current_cpu;
> >>> +
> >>> + if (cpu) {
> >>> + icount -= (cpu->icount_decr.u16.low + cpu->icount_extra);
> >>> + }
> >>> + return icount;
> >>> +}
> >> This is the same as Frederic's QEMU_CLOCK_ICOUNT clock, right? Any
> >> reason why one is better than the other?
> > Not really. Frederic's QEMU_CLOCK_ICOUNT is measured in nanoseconds.
> > And this counter is measured in instructions.
> >
> So you transformed your implementation to use icount?
Right, new implementation uses icount.
> I guess you replay event's according to the current instruction?
> I implemented icount clock with the QEMUTimer API so a callback can be
> notified during the replay at the right instruction.
We cannot use timers, because there are synchronization events
(like exceptions, interrupts, timer reads) that control the execution correctness.
> By the way do you have a git tree somewhere where I can get the patches?
No, there is no public repository. There are only the patches in the mail list.
Pavel Dovgalyuk
next prev parent reply other threads:[~2014-11-11 9:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:31 [Qemu-devel] [RFC PATCH v4 00/25] Deterministic replay and reverse execution Pavel Dovgalyuk
2014-11-07 10:31 ` [Qemu-devel] [RFC PATCH v4 01/25] acpi: accurate overflow check Pavel Dovgalyuk
2014-11-07 11:16 ` Paolo Bonzini
2014-11-07 10:31 ` [Qemu-devel] [RFC PATCH v4 02/25] mc146818rtc: add missed field to vmstate Pavel Dovgalyuk
2014-11-07 11:18 ` Paolo Bonzini
2014-11-07 10:31 ` [Qemu-devel] [RFC PATCH v4 03/25] replay: global variables and function stubs Pavel Dovgalyuk
2014-11-07 10:44 ` Eric Blake
2014-11-07 10:31 ` [Qemu-devel] [RFC PATCH v4 04/25] sysemu: system functions for replay Pavel Dovgalyuk
2014-11-07 15:51 ` Alex Bennée
2014-11-07 10:31 ` [Qemu-devel] [RFC PATCH v4 05/25] replay: internal functions for replay log Pavel Dovgalyuk
2014-11-07 16:01 ` Alex Bennée
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 06/25] cpu-exec: reset exception_index correctly Pavel Dovgalyuk
2014-11-07 11:27 ` Paolo Bonzini
2014-11-12 12:02 ` Paolo Bonzini
2014-11-13 11:41 ` Pavel Dovgaluk
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 07/25] icount: implement icount requesting Pavel Dovgalyuk
2014-11-07 11:19 ` Paolo Bonzini
2014-11-07 11:36 ` Pavel Dovgaluk
2014-11-07 11:45 ` Frederic Konrad
2014-11-11 9:41 ` Pavel Dovgaluk [this message]
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 08/25] icount: improve enable/disable ticks Pavel Dovgalyuk
2014-11-07 11:20 ` Paolo Bonzini
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 09/25] replay: introduce icount event Pavel Dovgalyuk
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 10/25] i386: do not cross the pages boundaries in replay mode Pavel Dovgalyuk
2014-11-07 11:20 ` Paolo Bonzini
2014-11-07 11:39 ` Pavel Dovgaluk
2014-11-07 11:27 ` Andreas Färber
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 11/25] cpu-exec: allow temporary disabling icount Pavel Dovgalyuk
2014-11-07 11:22 ` Paolo Bonzini
2014-11-11 9:49 ` Pavel Dovgaluk
2014-11-13 14:16 ` Paolo Bonzini
2014-11-17 9:35 ` Pavel Dovgaluk
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 12/25] replay: interrupts and exceptions Pavel Dovgalyuk
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 13/25] replay: asynchronous events infrastructure Pavel Dovgalyuk
2014-11-07 10:53 ` Eric Blake
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 14/25] cpu: replay instructions sequence Pavel Dovgalyuk
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 15/25] replay: recording and replaying clock ticks Pavel Dovgalyuk
2014-11-07 10:32 ` [Qemu-devel] [RFC PATCH v4 16/25] replay: recording and replaying different timers Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 17/25] cpus: make icount warp deterministic in replay mode Pavel Dovgalyuk
2014-11-07 11:24 ` Paolo Bonzini
2014-11-07 11:45 ` Pavel Dovgaluk
2014-11-07 12:00 ` Paolo Bonzini
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 18/25] replay: shutdown event Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 19/25] replay: checkpoints Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 20/25] replay: bottom halves Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 21/25] replay: replay aio requests Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 22/25] replay: thread pool Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 23/25] replay: initialization and deinitialization Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 24/25] replay: command line options Pavel Dovgalyuk
2014-11-07 10:33 ` [Qemu-devel] [RFC PATCH v4 25/25] replay: recording of the user input 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='000c01cffd93$b2225cd0$16671670$@Dovgaluk@ispras.ru' \
--to=pavel.dovgaluk@ispras.ru \
--cc=afaerber@suse.de \
--cc=alex.bennee@linaro.org \
--cc=batuzovk@ispras.ru \
--cc=fred.konrad@greensocs.com \
--cc=maria.klimushenkova@ispras.ru \
--cc=mark.burton@greensocs.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=real@ispras.ru \
/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).