Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751641AbZIPPdQ (ORCPT ); Wed, 16 Sep 2009 11:33:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750868AbZIPPdP (ORCPT ); Wed, 16 Sep 2009 11:33:15 -0400 Received: from casper.infradead.org ([85.118.1.10]:59373 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750793AbZIPPdO (ORCPT ); Wed, 16 Sep 2009 11:33:14 -0400 Subject: Re: [PATCH v3 0/3] cpu: pseries: Cpu offline states framework From: Peter Zijlstra To: dipankar@in.ibm.com Cc: Gautham R Shenoy , Joel Schopp , Benjamin Herrenschmidt , Balbir Singh , Venkatesh Pallipadi , Vaidyanathan Srinivasan , Arun R Bharadwaj , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, "Darrick J. Wong" In-Reply-To: <20090916152820.GA12571@in.ibm.com> References: <20090915120629.20523.79019.stgit@sofia.in.ibm.com> <1253016701.5506.73.camel@laptop> <20090916152820.GA12571@in.ibm.com> Content-Type: text/plain Date: Wed, 16 Sep 2009 17:32:51 +0200 Message-Id: <1253115171.7180.1.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1401 Lines: 30 On Wed, 2009-09-16 at 20:58 +0530, Dipankar Sarma wrote: > On Tue, Sep 15, 2009 at 02:11:41PM +0200, Peter Zijlstra wrote: > > On Tue, 2009-09-15 at 17:36 +0530, Gautham R Shenoy wrote: > > > This patchset contains the offline state driver implemented for > > > pSeries. For pSeries, we define three available_hotplug_states. They are: > > > > > > online: The processor is online. > > > > > > offline: This is the the default behaviour when the cpu is offlined > > > > > > inactive: This cedes the vCPU to the hypervisor with a cede latency > > > > > > Any feedback on the patchset will be immensely valuable. > > > > I still think its a layering violation... its the hypervisor manager > > that should be bothered in what state an off-lined cpu is in. > > The problem is that all hypervisor managers cannot figure out what sort > of latency guest OS can tolerate under the situation. They wouldn't know > from what context guest OS has ceded the vcpu. It has to have > some sort of hint, which is what the guest OS provides. I'm missing something here, hot-unplug is a slow path and should not ever be latency critical..? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/