From: Ian Jackson Subject: Re: [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari Date: Mon, 16 Mar 2009 18:05:20 +0000 Message-ID: <18878.38112.486019.336529@mariner.uk.xensource.com> References: <49B0B8DC.5000606@lab.ntt.co.jp> <49B0C6FF.8090903@lab.ntt.co.jp> <49B10B8D.6090505@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49B10B8D.6090505@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: "ospk-vm@lab.ntt.co.jp" , Ian Pratt , xen-devel , Yoshiaki Tamura , Keir Fraser List-Id: xen-devel@lists.xenproject.org Stefano Stabellini writes ("Re: [Xen-devel] [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari"): > 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? I think that in this case a signal-based interface is probably fine, because it does indeed need very good performance which is difficult to do with xenstore. Ian.