From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: "Gautham R . Shenoy" <ego@linux.vnet.ibm.com>,
linux-pm@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [1/3] cpuidle: powerpc: cpuidle set polling before enabling irqs
Date: Thu, 29 Jun 2017 22:21:10 +1000 (AEST) [thread overview]
Message-ID: <3wyzKL1g2Vz9s65@ozlabs.org> (raw)
In-Reply-To: <20170614130241.19865-2-npiggin@gmail.com>
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 send an IPI.
>
> Expand the TIF_POLLING_NRFLAG coverage to as large as possible.
>
> Reviewed-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/3fc5ee927ff4ffed6aa2fcd44d2fbf
cheers
next prev parent reply other threads:[~2017-06-29 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:02 [PATCH 0/3] powerpc (powernv and pseries) cpuidle driver improvmeents Nicholas Piggin
2017-06-14 13:02 ` [PATCH 1/3] cpuidle: powerpc: cpuidle set polling before enabling irqs Nicholas Piggin
2017-06-29 12:21 ` Michael Ellerman [this message]
2017-06-29 20:38 ` [1/3] " Rafael J. Wysocki
2017-06-30 3:45 ` Michael Ellerman
2017-06-30 12:51 ` Rafael J. Wysocki
2017-07-04 2:59 ` Michael Ellerman
2017-06-14 13:02 ` [PATCH 2/3] cpuidle: powerpc: read mostly for common globals Nicholas Piggin
2017-06-14 13:02 ` [PATCH 3/3] cpuidle: powerpc: no memory barrier after break from idle Nicholas Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3wyzKL1g2Vz9s65@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=daniel.lezcano@linaro.org \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).