From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright Subject: Re: [PATCH] qemu-kvm: introduce cpu_start/cpu_stop commands Date: Mon, 22 Nov 2010 15:56:51 -0800 Message-ID: <20101122235651.GD10050@sequoia.sous-sol.org> References: <1290466818-5230-1-git-send-email-aliguori@us.ibm.com> <20101122230405.GB10050@sequoia.sous-sol.org> <4CEB006C.8010407@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Chris Wright , Anthony Liguori , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Anthony Liguori Return-path: Received: from sous-sol.org ([216.99.217.87]:54044 "EHLO sequoia.sous-sol.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932393Ab0KVX5G (ORCPT ); Mon, 22 Nov 2010 18:57:06 -0500 Content-Disposition: inline In-Reply-To: <4CEB006C.8010407@linux.vnet.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: * Anthony Liguori (aliguori@linux.vnet.ibm.com) wrote: > On 11/22/2010 05:04 PM, Chris Wright wrote: > >* Anthony Liguori (aliguori@us.ibm.com) wrote: > >>qemu-kvm vcpu threads don't response to SIGSTOP/SIGCONT. Instead of teaching > >>them to respond to these signals, introduce monitor commands that stop and start > >>individual vcpus. > >In the past SIGSTOP has introduced time skew. Have you verified this > >isn't an issue. > > Time skew is a big topic. Are you talking about TSC drift, > pit/rtc/hpet drift, etc? Sorry to be vague, but it's been long enough that I don't recall the details. The guest kernel's clocksource effected how timekeeping progressed across STOP/CONT (was probably missing qemu based timer ticks). While this is not the same, made me wonder if you'd tested against that. > It's certainly going to stress periodic interrupt catch up code. Heh, call it a feature for autotest ;) thanks, -chris