Thanks, I'll merge this to android-3.4 soon.
Todd
On Thu, Dec 13, 2012 at 9:47 AM, Viresh Kumar wrote:
> From: Nicolas Pitre
>
> Relying on pcpu->governor_enabled alone to ensure proper shutdown
> of the governor activities is flawed. The following race is perfectly
> possible:
>
> CPU0
- A new output binary (board.axf) has been added exclusively for
board usage, which uses a different linker script (board.lds.S).
- BootMonitor has already placed secondary CPUs in wfi state,
generate a software interrupt first and point other cores to
jump to the right location by writing th
>> The scheme below tries to summaries the idea:
>>
>> Socket | socket 0 | socket 1 | socket 2 | socket 3 |
>> LCPU| 0 | 1-15 | 16 | 17-31 | 32 | 33-47 | 48 | 49-63 |
>> buddy conf0 | 0 | 0| 1 | 16| 2 | 32| 3 | 48|
>> buddy conf1 | 0 | 0
On Fri, 2012-12-14 at 11:43 +0100, Vincent Guittot wrote:
> 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?
> >> >>> > >
>
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 some boot code at the
>> reset
>> > vector and which survives after
On 16 December 2012 08:12, Alex Shi wrote:
> On 12/14/2012 05:33 PM, Vincent Guittot wrote:
>> 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 wro
