Re: [kvmarm] [PATCH] bootwrapper: CPU hotplug aware boot protocol

2012-12-14 Thread Jon Medhurst (Tixy)
On Thu, 2012-12-13 at 13:52 -0800, Christoffer Dall wrote: > On Friday, December 7, 2012, Jon Medhurst (Tixy) wrote: > > > To enable CPU hotplug the need to provide some boot code at the > reset > > vector and which survives after the kernel has booted without being > > overwritten. We achieve thi

Re: [RFC PATCH v2 3/6] sched: pack small tasks

2012-12-14 Thread Vincent Guittot
On 14 December 2012 02:46, Alex Shi wrote: > On 12/13/2012 11:48 PM, Vincent Guittot wrote: >> On 13 December 2012 15:53, Vincent Guittot >> wrote: >>> On 13 December 2012 15:25, Alex Shi wrote: On 12/13/2012 06:11 PM, Vincent Guittot wrote: > On 13 December 2012 03:17, Alex Shi wrote

Re: [RFC PATCH v2 3/6] sched: pack small tasks

2012-12-14 Thread Vincent Guittot
On 14 December 2012 08:45, Mike Galbraith wrote: > On Fri, 2012-12-14 at 14:36 +0800, Alex Shi wrote: >> On 12/14/2012 12:45 PM, Mike Galbraith wrote: >> >> > Do you have further ideas for buddy cpu on such example? >> >>> > > >> >>> > > Which kind of sched_domain configuration have you for such s

Re: [RFC PATCH v2 3/6] sched: pack small tasks

2012-12-14 Thread Mike Galbraith
On Fri, 2012-12-14 at 14:36 +0800, Alex Shi wrote: > On 12/14/2012 12:45 PM, Mike Galbraith wrote: > >> > Do you have further ideas for buddy cpu on such example? > >>> > > > >>> > > Which kind of sched_domain configuration have you for such system ? > >>> > > and how many sched_domain level have

Re: [RFC PATCH v2 3/6] sched: pack small tasks

2012-12-14 Thread Mike Galbraith
On Thu, 2012-12-13 at 22:25 +0800, Alex Shi wrote: > On 12/13/2012 06:11 PM, Vincent Guittot wrote: > > On 13 December 2012 03:17, Alex Shi wrote: > >> On 12/12/2012 09:31 PM, Vincent Guittot wrote: > >>> During the creation of sched_domain, we define a pack buddy CPU for each > >>> CPU > >>> wh

Re: [kvmarm] [PATCH] bootwrapper: CPU hotplug aware boot protocol

2012-12-14 Thread Christoffer Dall
On Friday, December 7, 2012, Jon Medhurst (Tixy) wrote: > To enable CPU hotplug the need to provide some boot code at the reset > vector and which survives after the kernel has booted without being > overwritten. We achieve this by the getting the linker script to place > the code in boot.S at add

[PATCH 0/2][V2] cpuidle - remove power from the select equation

2012-12-14 Thread Daniel Lezcano
The states could be sorted in the power backward order, we get rid of some lines of code and by this way that fixes also a bug in the dynamic c-states. Changelog: V2: * added the optimization in the select menu governor Daniel Lezcano (2): cpuidle - remove the power_specified field in the dri

[PATCH 1/2][V2] cpuidle - remove the power_specified field in the driver

2012-12-14 Thread Daniel Lezcano
This patch follows the discussion about reinitializing the power usage when a C-state is added/removed. https://lkml.org/lkml/2012/10/16/518 We realized the power usage field is never filled and when it is filled for tegra, the power_specified flag is not set making all these values to be resett

[PATCH 2/2][V2] cpuidle - optimize the select function for the 'menu' governor

2012-12-14 Thread Daniel Lezcano
As the power is backward sorted in the states array and we are looking for the state consuming the little power as possible, instead of looking from the beginning of the array, we look from the end. That should save us some iterations in the loop each time we select a state at idle time. Signed-of

Re: [kvmarm] [PATCH] bootwrapper: CPU hotplug aware boot protocol

2012-12-14 Thread Jon Medhurst (Tixy)
On Fri, 2012-12-14 at 10:10 -0500, Christoffer Dall wrote: > On Fri, Dec 14, 2012 at 3:49 AM, Jon Medhurst (Tixy) wrote: > > On Thu, 2012-12-13 at 13:52 -0800, Christoffer Dall wrote: > >> On Friday, December 7, 2012, Jon Medhurst (Tixy) wrote: > >> > >> > To enable CPU hotplug the need to provide

Re: [kvmarm] [PATCH] bootwrapper: CPU hotplug aware boot protocol

2012-12-14 Thread Alexander Spyridakis
On 14 December 2012 16:10, Christoffer Dall wrote: > What I was trying to figure out was why you can get rid of the "a > location less likely to be overridden" and why you're sure this memory > stays unmodified - I thought that was because you were loading the > code in the beginning of the physic

Re: [kvmarm] [PATCH] bootwrapper: CPU hotplug aware boot protocol

2012-12-14 Thread Marc Zyngier
On 14/12/12 15:54, Jon Medhurst (Tixy) wrote: > On Fri, 2012-12-14 at 10:10 -0500, Christoffer Dall wrote: >> On Fri, Dec 14, 2012 at 3:49 AM, Jon Medhurst (Tixy) wrote: >>> On Thu, 2012-12-13 at 13:52 -0800, Christoffer Dall wrote: On Friday, December 7, 2012, Jon Medhurst (Tixy) wrote:

Re: [kvmarm] [PATCH] bootwrapper: CPU hotplug aware boot protocol

2012-12-14 Thread Jon Medhurst (Tixy)
On Fri, 2012-12-14 at 16:00 +, Marc Zyngier wrote: > On 14/12/12 15:54, Jon Medhurst (Tixy) wrote: > > On Fri, 2012-12-14 at 10:10 -0500, Christoffer Dall wrote: > >> On Fri, Dec 14, 2012 at 3:49 AM, Jon Medhurst (Tixy) > >> wrote: > >>> On Thu, 2012-12-13 at 13:52 -0800, Christoffer Dall wro

Re: [kvmarm] [PATCH] bootwrapper: CPU hotplug aware boot protocol

2012-12-14 Thread Nicolas Pitre
On Fri, 14 Dec 2012, Marc Zyngier wrote: > On 14/12/12 15:54, Jon Medhurst (Tixy) wrote: > > I must admit, my patch is based on someone elses work, and I've not seen > > documentation which says that NOR flash can be written to simply by the > > application being loaded by the models having code l