All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Frederic Konrad <fred.konrad@greensocs.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:29:21 +0200	[thread overview]
Message-ID: <540D68E1.5080204@redhat.com> (raw)
In-Reply-To: <540D6449.6000602@greensocs.com>

Il 08/09/2014 10:09, Frederic Konrad ha scritto:
>>
> By the way how do you want to have this discussion?
> 
> At the KVM forum? Or by phone on KVM phone call?

Or both. :)

Seriously, Pavel is presenting on record/replay at KVM Forum.  I guess
there will be some discussion after his presentation, but anything that
happens _before_ could make the presentation more interesting.

Paolo

  reply	other threads:[~2014-09-08  8:29 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
2014-09-08  8:29       ` Paolo Bonzini [this message]
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=540D68E1.5080204@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=fred.konrad@greensocs.com \
    --cc=mark.burton@greensocs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.