On Mon, Jul 16, 2012 at 11:34 AM, Nicolas Pitre
wrote:
> On Mon, 16 Jul 2012, Colin Cross wrote:
>
>> vfp_pm_suspend should save the VFP state in suspend after
>> any lazy context switch. If it only saves when the VFP is enabled,
>> the state can get lost when, on a UP system:
>> Thread 1 uses
On Mon, 16 Jul 2012, Colin Cross wrote:
> vfp_pm_suspend should save the VFP state in suspend after
> any lazy context switch. If it only saves when the VFP is enabled,
> the state can get lost when, on a UP system:
> Thread 1 uses the VFP
> Context switch occurs to thread 2, VFP is disabled
vfp_pm_suspend should save the VFP state in suspend after
any lazy context switch. If it only saves when the VFP is enabled,
the state can get lost when, on a UP system:
Thread 1 uses the VFP
Context switch occurs to thread 2, VFP is disabled but the
VFP context is not saved
Thread 2
vfp_pm_suspend should save the VFP state in suspend after
any lazy context switch. If it only saves when the VFP is enabled,
the state can get lost when, on a UP system:
Thread 1 uses the VFP
Context switch occurs to thread 2, VFP is disabled but the
VFP context is not saved
Thread 2
On Mon, 16 Jul 2012, Colin Cross wrote:
vfp_pm_suspend should save the VFP state in suspend after
any lazy context switch. If it only saves when the VFP is enabled,
the state can get lost when, on a UP system:
Thread 1 uses the VFP
Context switch occurs to thread 2, VFP is disabled but
On Mon, Jul 16, 2012 at 11:34 AM, Nicolas Pitre
nicolas.pi...@linaro.org wrote:
On Mon, 16 Jul 2012, Colin Cross wrote:
vfp_pm_suspend should save the VFP state in suspend after
any lazy context switch. If it only saves when the VFP is enabled,
the state can get lost when, on a UP system:
6 matches
Mail list logo