qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Konrad <fred.konrad@greensocs.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, quintela@redhat.com,
	mark.burton@greensocs.com, dgilbert@redhat.com,
	Pavel.Dovgaluk@ispras.ru, amit.shah@redhat.com,
	sebastian.tanase@openwide.fr, vilanova@ac.upc.edu
Subject: Re: [Qemu-devel] [RFC PATCH v6 00/14] Reverse execution.
Date: Mon, 08 Sep 2014 10:09:45 +0200	[thread overview]
Message-ID: <540D6449.6000602@greensocs.com> (raw)
In-Reply-To: <540D614C.9080801@greensocs.com>

On 08/09/2014 09:57, Frederic Konrad wrote:
> On 01/09/2014 18:22, Paolo Bonzini wrote:
>> Il 03/07/2014 16:33, fred.konrad@greensocs.com ha scritto:
>>> From: KONRAD Frederic <fred.konrad@greensocs.com>
>>>
>>> Hi everybody,
>>>
>>> This is the sixth version of this RFC (see the changes below).
>>>
>>> Those are the two first patch-set we have been worked on for reverse 
>>> execution.
>>>
>>> The first part is fully reviewed except the "icount: introduce 
>>> icount timer"
>>> patch maybe we can merge them?
>>>
>>> The first series:
>>>    icount: put icount variables into TimerState.
>>>    migration: migrate icount fields.
>>>    migration: make qemu_savevm_state public.
>>>    icount: introduce icount timer.
>>>    icount: check for icount clock deadline when cpu loop exits.
>>>    icount: make icount extra computed on icount clock as well.
>>>    timer: add cpu_icount_to_ns function.
>>>
>>> are various preparation patches for reverse execution.
>>>
>>> The last patches:
>>>    trace-events: add reverse-execution events.
>>>    introduce reverse execution mechanism.
>>>    gdbstub: allow reverse execution in gdb stub.
>>>    cpu-exec: trigger a debug request when rexec stops.
>>>    rexec: synchronize icount on the next event.
>>>    rexec: allow to enable reverse execution.
>>>
>>> are reverse execution introduction.
>>>
>>> They can be clone at: git://git.greensocs.com/qemu_cexe.git:cexe_2_3_v6
>>>
>>> The third series will be sent as soon as possible and have some 
>>> issues with
>>> QEMU's thread as it use fork.
>>>
>>> This implementation of reverse execution works with instruction 
>>> counting:
>>>
>>> A new clock is implemented which is icount clock. It grows each time an
>>> instruction is executed and is totally independant of host clock.
>>>
>>> Snapshots are taken regularly (based on icount clock) with help of 
>>> migration
>>> code and written on the disk.
>>>
>>> When user wants to use reverse-stepi:
>>>   * Last snapshot is reloaded.
>>>   * A stop callback is created to be triggered at the previous 
>>> instruction.
>>>
>>> This stop callback generates a debug exception so QEMU stops in 
>>> debug mode.
>>>
>>> Command line:
>>>   * rexec suboption is added to icount to enable reverse execution, 
>>> it needs
>>>     icount=N and doesn't support auto mode.
>>>
>>> About non determinism in QEMU:
>>>   * This implementation doesn't take IO in account so any IO will 
>>> cause non
>>>     determinism and break reverse execution.
>>>
>>>   * The icount warp mechanism have been disabled when reverse 
>>> execution is
>>>     enabled so the time grow differently inside the VM.
>>>
>>> Testing:
>>>   * It has been tested on ARM without any IO such as network or 
>>> asynchronous file
>>>     access to keep the deterministic behaviour of icount.
>>>
>>> Known issues:
>>>   * On ARM stepi seems to do some additional steps which are added 
>>> to icount
>>>     counter so reverse-stepi just after stepi is broken.
>>>
>>>   * The IO replay explained above.
>> Hi, can you rebase and repost these patches?  It would be nice to have a
>> discussion of the different approaches to record/replay in your patches
>> and Pavel's (perhaps before Pavel presents at KVM Forum).
>>
>> Paolo
> Hi Paolo,
>
> Sorry for the delay.
> I'll rebase and resend these patches this week.
>
> Thanks,
> Fred
>
By the way how do you want to have this discussion?

At the KVM forum? Or by phone on KVM phone call?

Fred

  reply	other threads:[~2014-09-08  8:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 14:33 [Qemu-devel] [RFC PATCH v6 00/14] Reverse execution fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 01/14] icount: put icount variables into TimerState fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 02/14] migration: migrate icount fields fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 03/14] migration: make qemu_savevm_state public fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 04/14] icount: introduce icount timer fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 05/14] icount: check for icount clock deadline when cpu loop exits fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 06/14] icount: make icount extra computed on icount clock as well fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 07/14] timer: add cpu_icount_to_ns function fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 08/14] icount: Add QemuOpts for icount fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 09/14] trace-events: add reverse-execution events fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 10/14] introduce reverse execution mechanism fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 11/14] gdbstub: allow reverse execution in gdb stub fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 12/14] cpu-exec: trigger a debug request when rexec stops fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 13/14] rexec: synchronize icount on the next event fred.konrad
2014-07-03 14:33 ` [Qemu-devel] [RFC PATCH v6 14/14] rexec: allow to enable reverse execution fred.konrad
2014-09-01 16:22 ` [Qemu-devel] [RFC PATCH v6 00/14] Reverse execution Paolo Bonzini
2014-09-08  7:57   ` Frederic Konrad
2014-09-08  8:09     ` Frederic Konrad [this message]
2014-09-08  8:29       ` Paolo Bonzini
2014-09-08  8:43         ` Frederic Konrad
2014-09-09  6:30           ` Pavel Dovgaluk
2014-09-10 12:29             ` Frederic 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=540D6449.6000602@greensocs.com \
    --to=fred.konrad@greensocs.com \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=mark.burton@greensocs.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=sebastian.tanase@openwide.fr \
    --cc=vilanova@ac.upc.edu \
    /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).