mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe LEROY <christophe.leroy@c-s.fr>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Scott Wood <oss@buserror.net>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] powerpc/mm: Only read faulting instruction when necessary in do_page_fault()
Date: Tue, 2 May 2017 14:01:08 +0200	[thread overview]
Message-ID: <3955deea-141f-cbc9-2180-918ef165b823@c-s.fr> (raw)
In-Reply-To: <20170501130023.3c10e00d@roar.ozlabs.ibm.com>



Le 01/05/2017 à 05:00, Nicholas Piggin a écrit :
> On Fri, 28 Apr 2017 08:13:01 +0200 (CEST)
> Christophe Leroy <christophe.leroy@c-s.fr> wrote:
>
>> Commit a7a9dcd882a67 ("powerpc: Avoid taking a data miss on every
>> userspace instruction miss") has shown that limiting the read of
>> faulting instruction to likely cases improves performance.
>>
>> This patch goes further into this direction by limiting the read
>> of the faulting instruction to the only cases where it is definitly
>> needed.
>>
>> On an MPC885, with the same benchmark app as in the commit referred
>> above, we see a reduction of 4000 dTLB misses (approx 3%):
>>
>> Before the patch:
>>  Performance counter stats for './fault 500' (10 runs):
>>
>>          720495838      cpu-cycles                                                    ( +-  0.04% )
>>             141769      dTLB-load-misses                                              ( +-  0.02% )
>>              52722      iTLB-load-misses                                              ( +-  0.01% )
>>              19611      faults                                                        ( +-  0.02% )
>>
>>        5.750535176 seconds time elapsed                                          ( +-  0.16% )
>>
>> With the patch:
>>  Performance counter stats for './fault 500' (10 runs):
>>
>>          717669123      cpu-cycles                                                    ( +-  0.02% )
>>             137344      dTLB-load-misses                                              ( +-  0.03% )
>>              52731      iTLB-load-misses                                              ( +-  0.01% )
>>              19614      faults                                                        ( +-  0.03% )
>>
>>        5.728423115 seconds time elapsed                                          ( +-  0.14% )
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>> ---
>>  v2: Changes 'if (cond1) if (cond2)' by 'if (cond1 && cond2)'
>>
>>  In case the instruction we read has value 0, store_update_sp() will
>>  return false, so it will bail out.
>>
>>  This patch applies after the serie "powerpc/mm: some cleanup of do_page_fault()"
>>
>>  arch/powerpc/mm/fault.c | 22 ++++++++++++----------
>>  1 file changed, 12 insertions(+), 10 deletions(-)
>>
>> diff --git a/arch/powerpc/mm/fault.c b/arch/powerpc/mm/fault.c
>> index 400f2d0d42f8..2ec82a279d28 100644
>> --- a/arch/powerpc/mm/fault.c
>> +++ b/arch/powerpc/mm/fault.c
>> @@ -280,14 +280,6 @@ int do_page_fault(struct pt_regs *regs, unsigned long address,
>>
>>  	perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS, 1, regs, address);
>>
>> -	/*
>> -	 * We want to do this outside mmap_sem, because reading code around nip
>> -	 * can result in fault, which will cause a deadlock when called with
>> -	 * mmap_sem held
>> -	 */
>> -	if (is_write && is_user)
>> -		__get_user(inst, (unsigned int __user *)regs->nip);
>> -
>>  	if (is_user)
>>  		flags |= FAULT_FLAG_USER;
>>
>> @@ -356,8 +348,18 @@ int do_page_fault(struct pt_regs *regs, unsigned long address,
>>  		 * between the last mapped region and the stack will
>>  		 * expand the stack rather than segfaulting.
>>  		 */
>> -		if (address + 2048 < uregs->gpr[1] && !store_updates_sp(inst))
>> -			goto bad_area;
>> +		if (address + 2048 < uregs->gpr[1] && !inst) {
>> +			/*
>> +			 * We want to do this outside mmap_sem, because reading
>> +			 * code around nip can result in fault, which will cause
>> +			 * a deadlock when called with mmap_sem held
>> +			 */
>> +			up_read(&mm->mmap_sem);
>> +			__get_user(inst, (unsigned int __user *)regs->nip);
>> +			if (!store_updates_sp(inst))
>> +				goto bad_area_nosemaphore;
>> +			goto retry;
>> +		}
>
> Yes, nice patch. I wonder if you can do __get_user first as non-faulting to
> avoid retaking the mmap_sem and retrying? Along the lines of:
>
> +               nip = (unsigned int __user *)regs->nip;
> +               pagefault_disable();
> +               if (unlikely(__get_user_inatomic(inst, nip))) {
> +                       pagefault_enable();
> +                       up_read(&mm->mmap_sem);
> +                       if (get_user(inst, nip)) {
>                            ...
>                            goto retry;
>
> The user instruction should practically always have a Linux pte, so a
> fault there should be exceedingly rare, I think?

Thanks Nick.
I have submitted a new version of the patch taking your suggestion into 
accout.

Christophe

      reply	other threads:[~2017-05-02 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  6:13 Christophe Leroy
2017-05-01  3:00 ` Nicholas Piggin
2017-05-02 12:01   ` Christophe LEROY [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=3955deea-141f-cbc9-2180-918ef165b823@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=oss@buserror.net \
    --cc=paulus@samba.org \
    /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

all inboxes | Powered by JetHome®