From mboxrd@z Thu Jan 1 00:00:00 1970 From: Srivatsa Vaddagiri Subject: Re: [PATCH] qemu-kvm: response to SIGUSR1 to start/stop a VCPU (v2) Date: Thu, 2 Dec 2010 21:14:38 +0530 Message-ID: <20101202154437.GD16411@linux.vnet.ibm.com> References: <1291225502.32004.1787.camel@laptop> <20101201180040.GH8073@linux.vnet.ibm.com> <1291230582.32004.1927.camel@laptop> <4CF76440.30500@redhat.com> <20101202114700.GA18445@linux.vnet.ibm.com> <4CF793FF.4010504@redhat.com> <20101202131312.GC18445@linux.vnet.ibm.com> <4CF7A3F8.1010802@redhat.com> <20101202152716.GA16411@linux.vnet.ibm.com> <4CF7BC54.2080909@redhat.com> Reply-To: vatsa@linux.vnet.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Peter Zijlstra , Anthony Liguori , qemu-devel@nongnu.org, kvm@vger.kernel.org, Chris Wright , Ingo Molnar , Mike Galbraith , Rik van Riel To: Avi Kivity Return-path: Received: from e38.co.us.ibm.com ([32.97.110.159]:58165 "EHLO e38.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754622Ab0LBPos (ORCPT ); Thu, 2 Dec 2010 10:44:48 -0500 Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id oB2GaLxi005702 for ; Thu, 2 Dec 2010 09:36:21 -0700 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id oB2Fifq2179862 for ; Thu, 2 Dec 2010 08:44:42 -0700 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id oB2FieLW020038 for ; Thu, 2 Dec 2010 08:44:41 -0700 Content-Disposition: inline In-Reply-To: <4CF7BC54.2080909@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Dec 02, 2010 at 05:33:40PM +0200, Avi Kivity wrote: > A0 and A1's vruntime will keep growing, eventually B will become > leftmost and become runnable (assuming leftmost == min vruntime, not > sure what the terminology is). Donation (in directed yield) will cause vruntime to drop as well (thats the only way target can get to run ahead of its scheduled time), so I still think there are nasty issues involved here. Anyway, I am curious to see the directed yield implementation that Rik has - I can comment more after I have seen that! - vatsa