"Rafael J. Wysocki" writes:
> On Fri, Jun 30, 2017 at 5:45 AM, Michael Ellerman wrote:
>> "Rafael J. Wysocki" writes:
>>
>>> On Thu, Jun 29, 2017 at 2:21 PM, Michael Ellerman
>>> wrote:
On Wed, 2017-06-14 at 13:02:39 UTC, Nicholas Piggin wrote:
> local_irq_enable can cause interrupts
On Fri, Jun 30, 2017 at 5:45 AM, Michael Ellerman wrote:
> "Rafael J. Wysocki" writes:
>
>> On Thu, Jun 29, 2017 at 2:21 PM, Michael Ellerman
>> wrote:
>>> On Wed, 2017-06-14 at 13:02:39 UTC, Nicholas Piggin wrote:
local_irq_enable can cause interrupts to be taken which could
take sign
"Rafael J. Wysocki" writes:
> On Thu, Jun 29, 2017 at 2:21 PM, Michael Ellerman
> wrote:
>> On Wed, 2017-06-14 at 13:02:39 UTC, Nicholas Piggin wrote:
>>> local_irq_enable can cause interrupts to be taken which could
>>> take significant amount of processing time. The idle process
>>> should set
On Thu, Jun 29, 2017 at 2:21 PM, Michael Ellerman
wrote:
> On Wed, 2017-06-14 at 13:02:39 UTC, Nicholas Piggin wrote:
>> local_irq_enable can cause interrupts to be taken which could
>> take significant amount of processing time. The idle process
>> should set its polling flag before this, so anot
On Wed, 2017-06-14 at 13:02:39 UTC, Nicholas Piggin wrote:
> local_irq_enable can cause interrupts to be taken which could
> take significant amount of processing time. The idle process
> should set its polling flag before this, so another process that
> wakes it during this time will not have to s
local_irq_enable can cause interrupts to be taken which could
take significant amount of processing time. The idle process
should set its polling flag before this, so another process that
wakes it during this time will not have to send an IPI.
Expand the TIF_POLLING_NRFLAG coverage to as large as
