From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>, linuxppc-dev@lists•ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail•com>
Subject: Re: [1/4] powerpc/64s: context switch leave interrupts hard enabled for radix
Date: Mon, 19 Jun 2017 22:25:37 +1000 (AEST) [thread overview]
Message-ID: <3wrqv60vpXz9sBR@ozlabs.org> (raw)
In-Reply-To: <20170608153609.19217-1-npiggin@gmail.com>
On Thu, 2017-06-08 at 15:36:06 UTC, Nicholas Piggin wrote:
> Commit 4387e9ff25 ("[POWERPC] Fix PMU + soft interrupt disable bug")
> hard disabled interrupts over the low level context switch, because
> the SLB management can't cope with a PMU interrupt accesing the stack
> in that window.
>
> Radix based kernel mapping does not use the SLB so it does not require
> interrupts hard disabled here.
>
> This is worth 1-2% in context switch performance on POWER9.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/e4c0fc5f72bca11432297168338aef
cheers
prev parent reply other threads:[~2017-06-19 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 15:36 [PATCH 1/4] powerpc/64s: context switch leave interrupts hard enabled for radix Nicholas Piggin
2017-06-08 15:36 ` [PATCH 2/4] powerpc/64: context switch avoid reservation-clearing instruction Nicholas Piggin
2017-06-14 13:07 ` Michael Ellerman
2017-06-08 15:36 ` [PATCH 3/4] powerpc/64: context switch an hwsync instruction can be avoided Nicholas Piggin
2017-06-08 20:12 ` Peter Zijlstra
2017-06-08 15:36 ` [PATCH 4/4] powerpc/64s: context switch avoid cpabort Nicholas Piggin
2017-06-19 12:25 ` Michael Ellerman [this message]
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=3wrqv60vpXz9sBR@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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