All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "ospk-vm@lab.ntt.co.jp" <ospk-vm@lab.ntt.co.jp>,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari
Date: Sat, 07 Mar 2009 01:20:27 +0900	[thread overview]
Message-ID: <49B14D4B.7090300@lab.ntt.co.jp> (raw)
In-Reply-To: <49B10B8D.6090505@eu.citrix.com>

Stefano Stabellini wrote:
> Yoshiaki Tamura wrote:
> 
>> This patch implements signal handler for saving QEMU status quickly.  It also
>> includes a feature borrowed from KVM-17, which saves QEMU status quickly
>> without repositioning file offset by fseek.
> 
> We got rid of the signal interface not so long ago because it doesn't
> work for stubdoms.
> 
> The new way of asking qemu to save the VM state is writing a command on
> xenstore (look at xenstore.c:xenstore_process_dm_command_event).
> Would that work for you?
> 
> 
> 

xenstore is attractive because it can send more information between components 
than signals.

However, we used the signal handler to avoid the latency of xenstore.  Although 
we haven't measured the latency, we need a simple and quick interface to save 
the QEMU state because Kemari transfers the saved state on every synchronization 
which happens quite often.

Have you measured, or any thoughts on the latency of xenstore compared to signals?

  reply	other threads:[~2009-03-06 16:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  5:47 [RFC][PATCH 00/13] Kemari: VM synchronization mechanism for fault tolerance Yoshiaki Tamura
2009-03-06  5:50 ` [RFC][PATCH 01/13] Kemari: add ECS_TAP state to event channel Yoshiaki Tamura
2009-03-06  5:53 ` [RFC][PATCH 02/13] Kemari: core kemari code Yoshiaki Tamura
2009-03-06  5:54 ` [RFC][PATCH 03/13] Kemari: change parameter type of xc_{set, get}_hvm_param Yoshiaki Tamura
2009-03-06  5:56 ` [RFC][PATCH 04/13] Kemari: Kemari controller interface in libxc Yoshiaki Tamura
2009-03-06  6:26 ` [RFC][PATCH 05/13] Kemari: Kemari sender Yoshiaki Tamura
2009-03-06  6:46 ` [RFC][PATCH 06/13] Kemari: Kemari receiver Yoshiaki Tamura
2009-03-06  6:46 ` [RFC][PATCH 07/13] Kemari: add Kemari support to python Yoshiaki Tamura
2009-03-06  6:46 ` [RFC][PATCH 08/13] Kemari: add dev state "Attached" " Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 09/13] Kemari: add XenbusStateAttached to xenbus Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 10/13] Kemari: XenbusStateAttached handler for blkback Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 11/13] Kemari: XenbusStateAttached handler for netback Yoshiaki Tamura
2009-03-06  6:47 ` [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari Yoshiaki Tamura
2009-03-06 11:39   ` Stefano Stabellini
2009-03-06 16:20     ` Yoshiaki Tamura [this message]
2009-03-17 17:55       ` Stefano Stabellini
2009-03-17 18:21         ` Ian Jackson
2009-03-17 18:35           ` Stefano Stabellini
2009-03-18  9:11             ` Yoshiaki Tamura
2009-03-18  9:34               ` Keir Fraser
2009-03-18 12:45                 ` Yoshiaki Tamura
2009-03-18 12:46               ` Stefano Stabellini
2009-03-18 13:06                 ` Keir Fraser
2009-03-19  5:54                   ` Yoshiaki Tamura
2009-03-18 17:37               ` Christopher Head
2009-03-19  6:07                 ` Yoshiaki Tamura
2009-03-16 18:05     ` Ian Jackson
2009-03-06  6:47 ` [RFC][PATCH 13/13] Kemari: use shared region with to flip logdirty_bitmap Yoshiaki Tamura
  -- strict thread matches above, loose matches on Subject: below --
2009-03-12  1:22 [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari Yoshiaki Tamura
2009-03-24  6:59 ` Yoshiaki Tamura

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=49B14D4B.7090300@lab.ntt.co.jp \
    --to=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=ospk-vm@lab.ntt.co.jp \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.