From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Gautham R Shenoy <ego@in.ibm.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
linux-kernel@vger.kernel.org,
Arun R Bharadwaj <arun@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH v3 0/3] cpu: pseries: Cpu offline states framework
Date: Thu, 24 Sep 2009 10:52:46 +1000 [thread overview]
Message-ID: <1253753566.7103.359.camel@pasglop> (raw)
In-Reply-To: <20090916074848.GB4870@osiris.boeblingen.de.ibm.com>
On Wed, 2009-09-16 at 09:48 +0200, Heiko Carstens wrote:
> FWIW, this sounds exactly like the same we have already on s390.
> But back then I didn't consider adding a common code infrastructure
> would make sense :)
>
> Besides the "online" attribute we have an additional "configure"
> attribute to which can only be written if the cpu is offline.
> Writing a "0" to it would mean that you currently won't need the cpu
> anymore and the hypervisor is free to reassign the cpu to a different
> LPAR.
> Writing a "1" to it means you want to use it. If there are enough
> resources you will get it. If not.. bad luck.
>
Maybe we should use a common API for that then. And the right way to do
so is via a generically located attribute.
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Gautham R Shenoy <ego@in.ibm.com>,
Joel Schopp <jschopp@austin.ibm.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Arun R Bharadwaj <arun@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
"Darrick J. Wong" <djwong@us.ibm.com>
Subject: Re: [PATCH v3 0/3] cpu: pseries: Cpu offline states framework
Date: Thu, 24 Sep 2009 10:52:46 +1000 [thread overview]
Message-ID: <1253753566.7103.359.camel@pasglop> (raw)
In-Reply-To: <20090916074848.GB4870@osiris.boeblingen.de.ibm.com>
On Wed, 2009-09-16 at 09:48 +0200, Heiko Carstens wrote:
> FWIW, this sounds exactly like the same we have already on s390.
> But back then I didn't consider adding a common code infrastructure
> would make sense :)
>
> Besides the "online" attribute we have an additional "configure"
> attribute to which can only be written if the cpu is offline.
> Writing a "0" to it would mean that you currently won't need the cpu
> anymore and the hypervisor is free to reassign the cpu to a different
> LPAR.
> Writing a "1" to it means you want to use it. If there are enough
> resources you will get it. If not.. bad luck.
>
Maybe we should use a common API for that then. And the right way to do
so is via a generically located attribute.
Ben.
next prev parent reply other threads:[~2009-09-24 0:55 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 12:06 [PATCH v3 0/3] cpu: pseries: Cpu offline states framework Gautham R Shenoy
2009-09-15 12:07 ` [PATCH v3 1/3] pSeries: cede latency specifier helper function Gautham R Shenoy
2009-09-15 14:45 ` Daniel Walker
2009-09-15 14:45 ` Daniel Walker
2009-09-15 12:07 ` [PATCH v3 2/3] cpu: Offline state Framework Gautham R Shenoy
2009-09-30 17:31 ` Randy Dunlap
2009-09-30 17:31 ` Randy Dunlap
2009-09-15 12:07 ` [PATCH v3 3/3] cpu: Implement cpu-offline-state callbacks for pSeries Gautham R Shenoy
2009-09-15 12:11 ` [PATCH v3 0/3] cpu: pseries: Cpu offline states framework Peter Zijlstra
2009-09-15 12:11 ` Peter Zijlstra
2009-09-15 13:21 ` Michael Ellerman
2009-09-15 14:58 ` Balbir Singh
2009-09-15 14:58 ` Balbir Singh
2009-09-16 7:48 ` Heiko Carstens
2009-09-16 7:48 ` Heiko Carstens
2009-09-24 0:52 ` Benjamin Herrenschmidt [this message]
2009-09-24 0:52 ` Benjamin Herrenschmidt
2009-09-16 15:28 ` Dipankar Sarma
2009-09-16 15:28 ` Dipankar Sarma
2009-09-16 15:32 ` Peter Zijlstra
2009-09-16 15:32 ` Peter Zijlstra
2009-09-16 16:24 ` Dipankar Sarma
2009-09-16 16:24 ` Dipankar Sarma
2009-09-16 16:35 ` Peter Zijlstra
2009-09-16 16:35 ` Peter Zijlstra
2009-09-16 17:03 ` Vaidyanathan Srinivasan
2009-09-16 17:03 ` Vaidyanathan Srinivasan
2009-09-16 17:22 ` Peter Zijlstra
2009-09-16 17:22 ` Peter Zijlstra
2009-09-16 20:17 ` Dipankar Sarma
2009-09-16 20:17 ` Dipankar Sarma
2009-09-24 0:55 ` Benjamin Herrenschmidt
2009-09-24 0:55 ` Benjamin Herrenschmidt
2009-09-24 0:51 ` Benjamin Herrenschmidt
2009-09-24 0:51 ` Benjamin Herrenschmidt
2009-09-25 14:48 ` Peter Zijlstra
2009-09-25 14:48 ` Peter Zijlstra
2009-09-25 21:12 ` Benjamin Herrenschmidt
2009-09-25 21:12 ` Benjamin Herrenschmidt
2009-09-28 13:53 ` Vaidyanathan Srinivasan
2009-09-28 13:53 ` Vaidyanathan Srinivasan
2009-09-28 13:51 ` Vaidyanathan Srinivasan
2009-09-28 13:51 ` Vaidyanathan Srinivasan
2009-09-26 9:55 ` Pavel Machek
2009-09-26 9:55 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1253753566.7103.359.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=a.p.zijlstra@chello.nl \
--cc=arun@linux.vnet.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=djwong@us.ibm.com \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.