From: Gautham R Shenoy <ego@linux.vnet.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org,
"Shreyas B. Prabhu" <shreyasbp@gmail.com>,
Li Zhong <zhong@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] powerpc/64: Fix race condition in setting lock bit in idle/wakeup code
Date: Tue, 25 Oct 2016 17:16:44 +0530 [thread overview]
Message-ID: <20161025114644.GC3244@in.ibm.com> (raw)
In-Reply-To: <20161021090417.GB3809@fergus.ozlabs.ibm.com>
Hi Paul,
On Fri, Oct 21, 2016 at 08:04:17PM +1100, Paul Mackerras wrote:
> This fixes a race condition where one thread that is entering or
> leaving a power-saving state can inadvertently ignore the lock bit
> that was set by another thread, and potentially also clear it.
> The core_idle_lock_held function is called when the lock bit is
> seen to be set. It polls the lock bit until it is clear, then
> does a lwarx to load the word containing the lock bit and thread
> idle bits so it can be updated. However, it is possible that the
> value loaded with the lwarx has the lock bit set, even though an
> immediately preceding lwz loaded a value with the lock bit clear.
> If this happens then we go ahead and update the word despite the
> lock bit being set, and when called from pnv_enter_arch207_idle_mode,
> we will subsequently clear the lock bit.
>
> No identifiable misbehaviour has been attributed to this race.
>
> This fixes it by checking the lock bit in the value loaded by the
> lwarx. If it is set then we just go back and keep on polling.
>
> Fixes: b32aadc1a8ed
This fixes the code which has been around since 4.2 kernel. Should
this be marked to stable as well ?
> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
> ---
> arch/powerpc/kernel/idle_book3s.S | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/powerpc/kernel/idle_book3s.S b/arch/powerpc/kernel/idle_book3s.S
> index 0d8712a..72dac0b 100644
> --- a/arch/powerpc/kernel/idle_book3s.S
> +++ b/arch/powerpc/kernel/idle_book3s.S
> @@ -90,6 +90,7 @@ ALT_FTR_SECTION_END_IFSET(CPU_FTR_ARCH_300)
> * Threads will spin in HMT_LOW until the lock bit is cleared.
> * r14 - pointer to core_idle_state
> * r15 - used to load contents of core_idle_state
> + * r9 - used as a temporary variable
> */
>
> core_idle_lock_held:
> @@ -99,6 +100,8 @@ core_idle_lock_held:
> bne 3b
> HMT_MEDIUM
> lwarx r15,0,r14
> + andi. r9,r15,PNV_CORE_IDLE_LOCK_BIT
> + bne core_idle_lock_held
> blr
>
> /*
> --
> 2.7.4
>
--
Thanks and Regards
gautham.
next prev parent reply other threads:[~2016-10-25 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 9:03 [PATCH 1/2] powerpc/64: Re-fix race condition between going idle and entering guest Paul Mackerras
2016-10-21 9:04 ` [PATCH 2/2] powerpc/64: Fix race condition in setting lock bit in idle/wakeup code Paul Mackerras
2016-10-25 11:46 ` Gautham R Shenoy [this message]
2016-10-26 10:21 ` [2/2] " Michael Ellerman
2016-10-21 12:32 ` [PATCH 1/2] powerpc/64: Re-fix race condition between going idle and entering guest Shreyas B. Prabhu
2016-10-25 10:24 ` Gautham R Shenoy
2016-10-26 10:21 ` [1/2] " Michael Ellerman
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=20161025114644.GC3244@in.ibm.com \
--to=ego@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@ozlabs.org \
--cc=shreyasbp@gmail.com \
--cc=zhong@linux.vnet.ibm.com \
/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).