From: Paolo Bonzini <pbonzini@redhat.com>
To: 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
Subject: Re: [Qemu-devel] [PATCH 0/7] icount migration and clock.
Date: Fri, 01 Aug 2014 09:40:44 +0200 [thread overview]
Message-ID: <53DB447C.6040304@redhat.com> (raw)
In-Reply-To: <1406849835-4288-1-git-send-email-fred.konrad@greensocs.com>
Il 01/08/2014 01:37, fred.konrad@greensocs.com ha scritto:
> From: KONRAD Frederic <fred.konrad@greensocs.com>
>
> Those are some icount patches required for reverse execution.
>
> It introduces an icount clock which is only growing with icount.
> It allows QEMU to migrate icount so virtual clock is kept if the VM is migrated
> in icount mode (which is mandatory for migration based snapshot).
>
> They are rebased on uq/master of
> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
>
> And can be cloned here:
> git://git.greensocs.com/qemu_cexe.git:cexe_1_3_v6_rebased
>
> Thanks,
> Fred
>
> KONRAD Frederic (7):
> 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.
>
> cpus.c | 95 ++++++++++++++++++++++++++++++++++++++-----------
> include/qemu/timer.h | 10 +++++-
> include/sysemu/sysemu.h | 1
> qemu-timer.c | 8 ++++-
> savevm.c | 2 +-
> stubs/cpu-get-icount.c | 2 +-
> 6 files changed, 94 insertions(+), 24 deletions(-)
>
Thanks, I applied all patches and pushed everything to icount on
git://github.com/bonzini/qemu.git. I've also dropped Sebastian's
"icount: Make icount_time_shift available everywhere" and adjusted his
stuff to use cpu_icount_to_ns instead.
I'm planning to send out patches 1/2/7 in my first 2.2 pull request,
together with Sebastian's host clock alignment feature. The others will
have to wait for the reverse execution patches which actually use it.
Paolo
prev parent reply other threads:[~2014-08-01 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 23:37 [Qemu-devel] [PATCH 0/7] icount migration and clock fred.konrad
2014-07-31 23:37 ` [Qemu-devel] [PATCH 1/7] icount: put icount variables into TimerState fred.konrad
2014-07-31 23:37 ` [Qemu-devel] [PATCH 2/7] migration: migrate icount fields fred.konrad
2014-07-31 23:37 ` [Qemu-devel] [PATCH 3/7] migration: make qemu_savevm_state public fred.konrad
2014-07-31 23:37 ` [Qemu-devel] [PATCH 4/7] icount: introduce icount timer fred.konrad
2014-07-31 23:37 ` [Qemu-devel] [PATCH 5/7] icount: check for icount clock deadline when cpu loop exits fred.konrad
2014-07-31 23:37 ` [Qemu-devel] [PATCH 6/7] icount: make icount extra computed on icount clock as well fred.konrad
2014-07-31 23:37 ` [Qemu-devel] [PATCH 7/7] timer: add cpu_icount_to_ns function fred.konrad
2014-08-01 7:40 ` Paolo Bonzini [this message]
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=53DB447C.6040304@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 \
/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).