From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] Re: [PATCH] qemu-kvm: introduce cpu_start/cpu_stop commands Date: Tue, 23 Nov 2010 08:35:03 +0200 Message-ID: <4CEB6097.2030203@redhat.com> References: <1290466818-5230-1-git-send-email-aliguori@us.ibm.com> <20101122230405.GB10050@sequoia.sous-sol.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Chris Wright Return-path: Received: from mx1.redhat.com ([209.132.183.28]:33509 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460Ab0KWGfP (ORCPT ); Tue, 23 Nov 2010 01:35:15 -0500 In-Reply-To: <20101122230405.GB10050@sequoia.sous-sol.org> Sender: kvm-owner@vger.kernel.org List-ID: On 11/23/2010 01:04 AM, 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. Wouldn't we have the same problems with kernel cpu limits? I'd say it only depends on the period of the controller, not on how it's implemented. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.