On 10/11/16 10:28, Vincent Guittot wrote:
On 9 November 2016 at 19:48, Sudeep Holla wrote:
On 09/11/16 18:39, Lorenzo Pieralisi wrote:
[..]
I would just init the enter_freeze() pointer and be done with that,
adding code to check whether the idle back-end enables
On 10/11/16 10:28, Vincent Guittot wrote:
On 9 November 2016 at 19:48, Sudeep Holla wrote:
On 09/11/16 18:39, Lorenzo Pieralisi wrote:
[..]
I would just init the enter_freeze() pointer and be done with that,
adding code to check whether the idle back-end enables IRQs when it
enters
On 9 November 2016 at 19:48, Sudeep Holla wrote:
>
>
> On 09/11/16 18:39, Lorenzo Pieralisi wrote:
>>
>> On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
>>>
>>> enter_freeze() callback is expected atleast to do the same as enter()
>>> but it has to guarantee
On 9 November 2016 at 19:48, Sudeep Holla wrote:
>
>
> On 09/11/16 18:39, Lorenzo Pieralisi wrote:
>>
>> On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
>>>
>>> enter_freeze() callback is expected atleast to do the same as enter()
>>> but it has to guarantee that interrupts aren't
On 09/11/16 18:39, Lorenzo Pieralisi wrote:
On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
enter_freeze() callback is expected atleast to do the same as enter()
but it has to guarantee that interrupts aren't enabled at any point
in its execution, as the tick is frozen.
CPUs
On 09/11/16 18:39, Lorenzo Pieralisi wrote:
On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
enter_freeze() callback is expected atleast to do the same as enter()
but it has to guarantee that interrupts aren't enabled at any point
in its execution, as the tick is frozen.
CPUs
On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
> enter_freeze() callback is expected atleast to do the same as enter()
> but it has to guarantee that interrupts aren't enabled at any point
> in its execution, as the tick is frozen.
>
> CPUs execute ->enter_freeze with the local
On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
> enter_freeze() callback is expected atleast to do the same as enter()
> but it has to guarantee that interrupts aren't enabled at any point
> in its execution, as the tick is frozen.
>
> CPUs execute ->enter_freeze with the local
enter_freeze() callback is expected atleast to do the same as enter()
but it has to guarantee that interrupts aren't enabled at any point
in its execution, as the tick is frozen.
CPUs execute ->enter_freeze with the local tick or entire timekeeping
suspended, so it must not re-enable interrupts
enter_freeze() callback is expected atleast to do the same as enter()
but it has to guarantee that interrupts aren't enabled at any point
in its execution, as the tick is frozen.
CPUs execute ->enter_freeze with the local tick or entire timekeeping
suspended, so it must not re-enable interrupts
10 matches
Mail list logo