qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Arnabjyoti Kalita <akalita@cs.stonybrook.edu>,
	qemu-discuss <qemu-discuss@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>
Subject: Re: QEMU Clock record and replay
Date: Thu, 25 Feb 2021 16:43:36 +0100	[thread overview]
Message-ID: <e4677d3d-b221-3bba-185c-5a43faf6aab7@redhat.com> (raw)
In-Reply-To: <CAJGDS+F0Mtv+XFXeR4wOP35UjmfKt+fiMAfraT7mg9J-4t+SiA@mail.gmail.com>

Cc'ing Pavel/Alex.

On 2/25/21 4:09 PM, Arnabjyoti Kalita wrote:
> Hello all,
> 
> I am trying to understand how the clock values are recorded and replayed
> in QEMU (when it runs in TCG mode). I have been specifically following
> the document that has been provided here -
> https://github.com/qemu/qemu/blob/master/docs/replay.txt
> <https://github.com/qemu/qemu/blob/master/docs/replay.txt>
> 
> I have the following 4 questions to ask-
> 
> - Why are clock values being replayed off a cache and not directly off
> the file as seen here -
> https://github.com/qemu/qemu/blob/stable-5.0/replay/replay-time.c#L45?
> <https://github.com/qemu/qemu/blob/stable-5.0/replay/replay-time.c#L45?>?
> 
> - I have a requirement to record and replay host clock values. Can it so
> happen that if incorrect values of the host clock are replayed, then the
> timers in the guest start expiring incorrectly, during replay?
> 
> - Let's say we record the clock values when the guest starts in KVM
> mode, and we replay the clock values when the guest starts in TCG mode.
> Does the record-replay functionality change a lot?
> 
> - Also, I couldn't understand the specific purpose of replaying the
> 'virtual real time clock' ? Do I still need to record and replay the
> 'virtual real time clock' if we record the clock values in KVM mode, and
> replay the clock values in TCG mode?
> 
> Thank you very much.
> 
> Best Regards,
> Arnab
> 
> 



       reply	other threads:[~2021-02-25 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJGDS+F0Mtv+XFXeR4wOP35UjmfKt+fiMAfraT7mg9J-4t+SiA@mail.gmail.com>
2021-02-25 15:43 ` Philippe Mathieu-Daudé [this message]
2021-02-26  6:24   ` QEMU Clock record and replay Pavel Dovgalyuk
2021-02-26  9:54     ` Alex Bennée
2021-02-27 16:31       ` Arnabjyoti Kalita
2021-02-27 16:13     ` Arnabjyoti Kalita

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=e4677d3d-b221-3bba-185c-5a43faf6aab7@redhat.com \
    --to=philmd@redhat.com \
    --cc=akalita@cs.stonybrook.edu \
    --cc=alex.bennee@linaro.org \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@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).