From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
Cc: "Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Arnabjyoti Kalita" <akalita@cs.stonybrook.edu>,
qemu-discuss <qemu-discuss@nongnu.org>
Subject: Re: QEMU Clock record and replay
Date: Fri, 26 Feb 2021 09:54:25 +0000 [thread overview]
Message-ID: <87pn0n9mru.fsf@linaro.org> (raw)
In-Reply-To: <ffdcad8a-389a-ed22-0991-940ddeb3c8ed@ispras.ru>
Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru> writes:
> On 25.02.2021 18:43, Philippe Mathieu-Daudé wrote:
>> 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?>?
>
> The cache was needed when replay does not follow the record behavior.
> E.g., included additional deadline calculations or timer checks.
> I'm not sure, that it is still needed, and I'll check it during future
> refactoring session.
>
>>> - 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?
>
> This is a bug, when the host clock is replayed incorrectly.
When you say host clock what do you mean? Surely all the cycle counters
are VIRTUAL? Or do you mean things like the RTC?
--
Alex Bennée
next prev parent reply other threads:[~2021-02-26 10:06 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 ` QEMU Clock record and replay Philippe Mathieu-Daudé
2021-02-26 6:24 ` Pavel Dovgalyuk
2021-02-26 9:54 ` Alex Bennée [this message]
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=87pn0n9mru.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=akalita@cs.stonybrook.edu \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pavel.dovgalyuk@ispras.ru \
--cc=philmd@redhat.com \
--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).