[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH v7 15/21] replay: checkpoints
From: |
Pavel Dovgaluk |
Subject: |
Re: [Qemu-devel] [RFC PATCH v7 15/21] replay: checkpoints |
Date: |
Tue, 13 Jan 2015 17:26:54 +0300 |
> From: Paolo Bonzini [mailto:address@hidden
> On 13/01/2015 10:15, Pavel Dovgaluk wrote:
> > The numbers have no meaning. They just have to be distinct in different
> > places.
>
> This is easier to achieve if you give a name to each place.
>
> > Sorry, missed one thing.
> > run_all is used to distinguish timers processed in AIO by calling of
> timerlistgroup_run_timers function
> > and in main loop by calling qemu_clock_run_all_timers.
>
> Should you instead distinguish which TimerListGroup is being run? Then
> main loop would checkpoint once for every TimerListGroup (which means
> twice).
Then I'll have to introduce some kind of deterministic ID for them
and new asynchronous event to be saved instead of common checkpoints.
Because these calls can be invoked in any order.
But I have no idea of how to make such a deterministic ID.
Pavel Dovgalyuk
- Re: [Qemu-devel] [RFC PATCH v7 12/21] replay: recording and replaying clock ticks, (continued)
[Qemu-devel] [RFC PATCH v7 16/21] replay: bottom halves, Pavel Dovgalyuk, 2015/01/12
[Qemu-devel] [RFC PATCH v7 17/21] replay: replay aio requests, Pavel Dovgalyuk, 2015/01/12
[Qemu-devel] [RFC PATCH v7 18/21] replay: thread pool, Pavel Dovgalyuk, 2015/01/12
[Qemu-devel] [RFC PATCH v7 19/21] replay: initialization and deinitialization, Pavel Dovgalyuk, 2015/01/12
[Qemu-devel] [RFC PATCH v7 20/21] replay: command line options, Pavel Dovgalyuk, 2015/01/12