From: Keir Fraser Subject: Re: [RFC][PATCH 12/13] Kemari: use signal to save qemu state for Kemari Date: Wed, 18 Mar 2009 09:34:18 +0000 Message-ID: References: <49C0BAC6.7070103@lab.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49C0BAC6.7070103@lab.ntt.co.jp> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Yoshiaki Tamura , Stefano Stabellini Cc: "ospk-vm@lab.ntt.co.jp" , Ian Pratt , xen-devel , Ian Jackson List-Id: xen-devel@lists.xenproject.org On 18/03/2009 09:11, "Yoshiaki Tamura" wrote: > Thanks for measuring the numbers. It made things clear. > I think we need a signal-based interface as Ian said previously. > > On our test environment, AMD Barcelona 2.3GHz, the total cpu cycles of Kemari > in > userland when running I/O intensive applications is around 3000000. > Although Xen transferring code and QEMU saving code is processed concurrently, > using xenstored for staring QEMU portion would lower the performance. > Especially if the xenstored gets slower when items are loaded. Using signals won't work with qemu-dm in a stub domain. -- Keir