From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
bsingharora@gmail.com, npiggin@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] powerpc/mm: handle VM_FAULT_RETRY earlier
Date: Tue, 21 Mar 2017 10:57:26 +0100 [thread overview]
Message-ID: <04f09a0d-146c-93da-0879-249e212a23f2@linux.vnet.ibm.com> (raw)
In-Reply-To: <877f3jouxq.fsf@skywalker.in.ibm.com>
On 21/03/2017 10:12, Aneesh Kumar K.V wrote:
> Laurent Dufour <ldufour@linux.vnet.ibm.com> writes:
>
>> In do_page_fault() if handle_mm_fault() returns VM_FAULT_RETRY, retry
>> the page fault handling before anything else.
>>
>> This would simplify the handling of the mmap_sem lock in this part of
>> the code.
>>
>> Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
>> ---
>> arch/powerpc/mm/fault.c | 67 ++++++++++++++++++++++++++++---------------------
>> 1 file changed, 38 insertions(+), 29 deletions(-)
>>
>> diff --git a/arch/powerpc/mm/fault.c b/arch/powerpc/mm/fault.c
>> index ee09604bbe12..2a6bc7e6e69a 100644
>> --- a/arch/powerpc/mm/fault.c
>> +++ b/arch/powerpc/mm/fault.c
>> @@ -434,6 +434,26 @@ int do_page_fault(struct pt_regs *regs, unsigned long address,
>> * the fault.
>> */
>> fault = handle_mm_fault(vma, address, flags);
>> +
>> + /*
>> + * Handle the retry right now, the mmap_sem has been released in that
>> + * case.
>> + */
>> + if (unlikely(fault & VM_FAULT_RETRY)) {
>> + /* We retry only once */
>> + if (flags & FAULT_FLAG_ALLOW_RETRY) {
>> + /*
>> + * Clear FAULT_FLAG_ALLOW_RETRY to avoid any risk
>> + * of starvation.
>> + */
>> + flags &= ~FAULT_FLAG_ALLOW_RETRY;
>> + flags |= FAULT_FLAG_TRIED;
>> + if (!fatal_signal_pending(current))
>> + goto retry;
>> + }
>> + /* We will enter mm_fault_error() below */
>> + }
>> +
>> if (unlikely(fault & (VM_FAULT_RETRY|VM_FAULT_ERROR))) {
>> if (fault & VM_FAULT_SIGSEGV)
>> goto bad_area;
>> @@ -445,38 +465,27 @@ int do_page_fault(struct pt_regs *regs, unsigned long address,
>> }
>
> We could make it further simpler, by handling the FAULT_RETRY without
> FLAG_ALLOW_RETRY set earlier. But i guess that can be done later ?
Thanks for the review,
I agree that double checking against VM_FAULT_RETRY is confusing here.
But handling all the retry path in the first if() statement means that
we'll have to handle part of the mm_fault_error() code and segv here...
Unless we can't identify what is really relevant in that retry path.
It would take time to review all that tricky part, but I agree it should
be simplified later.
>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>
>
>>
>> /*
>> - * Major/minor page fault accounting is only done on the
>> - * initial attempt. If we go through a retry, it is extremely
>> - * likely that the page will be found in page cache at that point.
>> + * Major/minor page fault accounting.
>> */
>> - if (flags & FAULT_FLAG_ALLOW_RETRY) {
>> - if (fault & VM_FAULT_MAJOR) {
>> - current->maj_flt++;
>> - perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS_MAJ, 1,
>> - regs, address);
>> + if (fault & VM_FAULT_MAJOR) {
>> + current->maj_flt++;
>> + perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS_MAJ, 1,
>> + regs, address);
>> #ifdef CONFIG_PPC_SMLPAR
>> - if (firmware_has_feature(FW_FEATURE_CMO)) {
>> - u32 page_ins;
>> -
>> - preempt_disable();
>> - page_ins = be32_to_cpu(get_lppaca()->page_ins);
>> - page_ins += 1 << PAGE_FACTOR;
>> - get_lppaca()->page_ins = cpu_to_be32(page_ins);
>> - preempt_enable();
>> - }
>> -#endif /* CONFIG_PPC_SMLPAR */
>> - } else {
>> - current->min_flt++;
>> - perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS_MIN, 1,
>> - regs, address);
>> - }
>> - if (fault & VM_FAULT_RETRY) {
>> - /* Clear FAULT_FLAG_ALLOW_RETRY to avoid any risk
>> - * of starvation. */
>> - flags &= ~FAULT_FLAG_ALLOW_RETRY;
>> - flags |= FAULT_FLAG_TRIED;
>> - goto retry;
>> + if (firmware_has_feature(FW_FEATURE_CMO)) {
>> + u32 page_ins;
>> +
>> + preempt_disable();
>> + page_ins = be32_to_cpu(get_lppaca()->page_ins);
>> + page_ins += 1 << PAGE_FACTOR;
>> + get_lppaca()->page_ins = cpu_to_be32(page_ins);
>> + preempt_enable();
>> }
>> +#endif /* CONFIG_PPC_SMLPAR */
>> + } else {
>> + current->min_flt++;
>> + perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS_MIN, 1,
>> + regs, address);
>> }
>>
>> up_read(&mm->mmap_sem);
>> --
>> 2.7.4
next prev parent reply other threads:[~2017-03-21 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 16:45 [PATCH 0/3] powerpc/mm: page fault handler cleaning Laurent Dufour
2017-02-14 16:45 ` [PATCH 1/3] powerpc/mm: move mmap_sem unlock up from do_sigbus Laurent Dufour
2017-03-21 8:39 ` Aneesh Kumar K.V
2017-03-21 11:36 ` [1/3] " Michael Ellerman
2017-02-14 16:45 ` [PATCH 2/3] powerpc/mm: handle VM_FAULT_RETRY earlier Laurent Dufour
2017-03-21 9:12 ` Aneesh Kumar K.V
2017-03-21 9:57 ` Laurent Dufour [this message]
2017-02-14 16:45 ` [PATCH 3/3] powerpc/mm: move mmap_sem unlocking in do_page_fault() Laurent Dufour
2017-03-21 9:12 ` Aneesh Kumar K.V
2017-03-02 12:30 ` [PATCH 0/3] powerpc/mm: page fault handler cleaning Laurent Dufour
2017-03-03 12:17 ` 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=04f09a0d-146c-93da-0879-249e212a23f2@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--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®