2017-10-24 07:25:00 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
|
|
|
// Copyright (C) 2005-2017 Andes Technology Corporation
|
|
|
|
|
|
|
|
#include <linux/extable.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/signal.h>
|
|
|
|
#include <linux/ptrace.h>
|
|
|
|
#include <linux/mm.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/hardirq.h>
|
|
|
|
#include <linux/uaccess.h>
|
nds32: Perf porting
This is the commit that porting the perf for nds32.
1.Raw event:
The raw events start with 'r'.
Usage:
perf stat -e rXYZ ./app
X: the index of performance counter.
YZ: the index(convert to hexdecimal) of events
Example:
'perf stat -e r101 ./app' means the counter 1 will count the instruction
event.
The index of counter and events can be found in
"Andes System Privilege Architecture Version 3 Manual".
Or you can perform the 'perf list' to find the symbolic name of raw events.
2.Perf mmap2:
Fix unexpected perf mmap2() page fault
When the mmap2() called by perf application,
you will encounter such condition:"failed to write."
With return value -EFAULT
This is due to the page fault caused by "reading" buffer
from the mapped legal address region to write to the descriptor.
The page_fault handler will get a VM_FAULT_SIGBUS return value,
which should not happens here.(Due to this is a read request.)
You can refer to kernel/events/core.c:perf_mmap_fault(...)
If "(vmf->pgoff && (vmf->flags & FAULT_FLAG_WRITE))" is evaluated
as true, you will get VM_FAULT_SIGBUS as return value.
However, this is not an write request. The flags which indicated
why the page fault happens is wrong.
Furthermore, NDS32 SPAv3 is not able to detect it is read or write.
It only know either it is instruction fetch or data access.
Therefore, by removing the wrong flag assignment(actually, the hardware
is not able to show the reason), we can fix this bug.
3.Perf multiple events map to same counter.
When there are multiple events map to the same counter, the counter
counts inaccurately. This is because each counter only counts one event
in the same time.
So when there are multiple events map to same counter, they have to take
turns in each context.
There are two solution:
1. Print the error message when multiple events map to the same counter.
But print the error message would let the program hang in loop. The ltp
(linux test program) would be failed when the program hang in loop.
2. Don't print the error message, the ltp would pass. But the user need to
have the knowledge that don't count the events which map to the same
counter, or the user will get the inaccurate results.
We choose method 2 for the solution
Signed-off-by: Nickhu <nickhu@andestech.com>
Acked-by: Greentime Hu <greentime@andestech.com>
Signed-off-by: Greentime Hu <greentime@andestech.com>
2018-10-25 02:24:15 +00:00
|
|
|
#include <linux/perf_event.h>
|
2017-10-24 07:25:00 +00:00
|
|
|
|
|
|
|
#include <asm/tlbflush.h>
|
|
|
|
|
|
|
|
extern void die(const char *str, struct pt_regs *regs, long err);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This is useful to dump out the page tables associated with
|
|
|
|
* 'addr' in mm 'mm'.
|
|
|
|
*/
|
|
|
|
void show_pte(struct mm_struct *mm, unsigned long addr)
|
|
|
|
{
|
|
|
|
pgd_t *pgd;
|
|
|
|
if (!mm)
|
|
|
|
mm = &init_mm;
|
|
|
|
|
|
|
|
pr_alert("pgd = %p\n", mm->pgd);
|
|
|
|
pgd = pgd_offset(mm, addr);
|
|
|
|
pr_alert("[%08lx] *pgd=%08lx", addr, pgd_val(*pgd));
|
|
|
|
|
|
|
|
do {
|
2019-12-05 00:54:08 +00:00
|
|
|
p4d_t *p4d;
|
|
|
|
pud_t *pud;
|
2017-10-24 07:25:00 +00:00
|
|
|
pmd_t *pmd;
|
|
|
|
|
|
|
|
if (pgd_none(*pgd))
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (pgd_bad(*pgd)) {
|
|
|
|
pr_alert("(bad)");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2019-12-05 00:54:08 +00:00
|
|
|
p4d = p4d_offset(pgd, addr);
|
|
|
|
pud = pud_offset(p4d, addr);
|
|
|
|
pmd = pmd_offset(pud, addr);
|
2017-10-24 07:25:00 +00:00
|
|
|
#if PTRS_PER_PMD != 1
|
|
|
|
pr_alert(", *pmd=%08lx", pmd_val(*pmd));
|
|
|
|
#endif
|
|
|
|
|
|
|
|
if (pmd_none(*pmd))
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (pmd_bad(*pmd)) {
|
|
|
|
pr_alert("(bad)");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (IS_ENABLED(CONFIG_HIGHMEM))
|
|
|
|
{
|
|
|
|
pte_t *pte;
|
|
|
|
/* We must not map this if we have highmem enabled */
|
|
|
|
pte = pte_offset_map(pmd, addr);
|
|
|
|
pr_alert(", *pte=%08lx", pte_val(*pte));
|
|
|
|
pte_unmap(pte);
|
|
|
|
}
|
|
|
|
} while (0);
|
|
|
|
|
|
|
|
pr_alert("\n");
|
|
|
|
}
|
|
|
|
|
|
|
|
void do_page_fault(unsigned long entry, unsigned long addr,
|
|
|
|
unsigned int error_code, struct pt_regs *regs)
|
|
|
|
{
|
|
|
|
struct task_struct *tsk;
|
|
|
|
struct mm_struct *mm;
|
|
|
|
struct vm_area_struct *vma;
|
2018-04-16 19:58:34 +00:00
|
|
|
int si_code;
|
2018-08-17 22:44:47 +00:00
|
|
|
vm_fault_t fault;
|
2020-04-10 21:33:09 +00:00
|
|
|
unsigned int mask = VM_ACCESS_FLAGS;
|
2020-04-02 04:08:37 +00:00
|
|
|
unsigned int flags = FAULT_FLAG_DEFAULT;
|
2017-10-24 07:25:00 +00:00
|
|
|
|
|
|
|
error_code = error_code & (ITYPE_mskINST | ITYPE_mskETYPE);
|
|
|
|
tsk = current;
|
|
|
|
mm = tsk->mm;
|
2018-04-16 19:58:34 +00:00
|
|
|
si_code = SEGV_MAPERR;
|
2017-10-24 07:25:00 +00:00
|
|
|
/*
|
|
|
|
* We fault-in kernel-space virtual memory on-demand. The
|
|
|
|
* 'reference' page table is init_mm.pgd.
|
|
|
|
*
|
|
|
|
* NOTE! We MUST NOT take any locks for this case. We may
|
|
|
|
* be in an interrupt or a critical region, and should
|
|
|
|
* only copy the information from the master page table,
|
|
|
|
* nothing more.
|
|
|
|
*/
|
|
|
|
if (addr >= TASK_SIZE) {
|
|
|
|
if (user_mode(regs))
|
|
|
|
goto bad_area_nosemaphore;
|
|
|
|
|
|
|
|
if (addr >= TASK_SIZE && addr < VMALLOC_END
|
|
|
|
&& (entry == ENTRY_PTE_NOT_PRESENT))
|
|
|
|
goto vmalloc_fault;
|
|
|
|
else
|
|
|
|
goto no_context;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Send a signal to the task for handling the unalignment access. */
|
|
|
|
if (entry == ENTRY_GENERAL_EXCPETION
|
|
|
|
&& error_code == ETYPE_ALIGNMENT_CHECK) {
|
|
|
|
if (user_mode(regs))
|
|
|
|
goto bad_area_nosemaphore;
|
|
|
|
else
|
|
|
|
goto no_context;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If we're in an interrupt or have no user
|
|
|
|
* context, we must not take the fault..
|
|
|
|
*/
|
|
|
|
if (unlikely(faulthandler_disabled() || !mm))
|
|
|
|
goto no_context;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* As per x86, we may deadlock here. However, since the kernel only
|
|
|
|
* validly references user space from well defined areas of the code,
|
|
|
|
* we can bug out early if this is from code which shouldn't.
|
|
|
|
*/
|
2020-06-09 04:33:25 +00:00
|
|
|
if (unlikely(!mmap_read_trylock(mm))) {
|
2017-10-24 07:25:00 +00:00
|
|
|
if (!user_mode(regs) &&
|
|
|
|
!search_exception_tables(instruction_pointer(regs)))
|
|
|
|
goto no_context;
|
|
|
|
retry:
|
2020-06-09 04:33:25 +00:00
|
|
|
mmap_read_lock(mm);
|
2017-10-24 07:25:00 +00:00
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* The above down_read_trylock() might have succeeded in which
|
|
|
|
* case, we'll have missed the might_sleep() from down_read().
|
|
|
|
*/
|
|
|
|
might_sleep();
|
|
|
|
if (IS_ENABLED(CONFIG_DEBUG_VM)) {
|
|
|
|
if (!user_mode(regs) &&
|
|
|
|
!search_exception_tables(instruction_pointer(regs)))
|
|
|
|
goto no_context;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
vma = find_vma(mm, addr);
|
|
|
|
|
|
|
|
if (unlikely(!vma))
|
|
|
|
goto bad_area;
|
|
|
|
|
|
|
|
if (vma->vm_start <= addr)
|
|
|
|
goto good_area;
|
|
|
|
|
|
|
|
if (unlikely(!(vma->vm_flags & VM_GROWSDOWN)))
|
|
|
|
goto bad_area;
|
|
|
|
|
|
|
|
if (unlikely(expand_stack(vma, addr)))
|
|
|
|
goto bad_area;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Ok, we have a good vm_area for this memory access, so
|
|
|
|
* we can handle it..
|
|
|
|
*/
|
|
|
|
|
|
|
|
good_area:
|
2018-04-16 19:58:34 +00:00
|
|
|
si_code = SEGV_ACCERR;
|
2017-10-24 07:25:00 +00:00
|
|
|
|
|
|
|
/* first do some preliminary protection checks */
|
|
|
|
if (entry == ENTRY_PTE_NOT_PRESENT) {
|
|
|
|
if (error_code & ITYPE_mskINST)
|
|
|
|
mask = VM_EXEC;
|
|
|
|
else {
|
|
|
|
mask = VM_READ | VM_WRITE;
|
|
|
|
}
|
|
|
|
} else if (entry == ENTRY_TLB_MISC) {
|
|
|
|
switch (error_code & ITYPE_mskETYPE) {
|
|
|
|
case RD_PROT:
|
|
|
|
mask = VM_READ;
|
|
|
|
break;
|
|
|
|
case WRT_PROT:
|
|
|
|
mask = VM_WRITE;
|
|
|
|
flags |= FAULT_FLAG_WRITE;
|
|
|
|
break;
|
|
|
|
case NOEXEC:
|
|
|
|
mask = VM_EXEC;
|
|
|
|
break;
|
|
|
|
case PAGE_MODIFY:
|
|
|
|
mask = VM_WRITE;
|
|
|
|
flags |= FAULT_FLAG_WRITE;
|
|
|
|
break;
|
|
|
|
case ACC_BIT:
|
|
|
|
BUG();
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|
|
|
|
if (!(vma->vm_flags & mask))
|
|
|
|
goto bad_area;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If for any reason at all we couldn't handle the fault,
|
|
|
|
* make sure we exit gracefully rather than endlessly redo
|
|
|
|
* the fault.
|
|
|
|
*/
|
|
|
|
|
mm: do page fault accounting in handle_mm_fault
Patch series "mm: Page fault accounting cleanups", v5.
This is v5 of the pf accounting cleanup series. It originates from Gerald
Schaefer's report on an issue a week ago regarding to incorrect page fault
accountings for retried page fault after commit 4064b9827063 ("mm: allow
VM_FAULT_RETRY for multiple times"):
https://lore.kernel.org/lkml/20200610174811.44b94525@thinkpad/
What this series did:
- Correct page fault accounting: we do accounting for a page fault
(no matter whether it's from #PF handling, or gup, or anything else)
only with the one that completed the fault. For example, page fault
retries should not be counted in page fault counters. Same to the
perf events.
- Unify definition of PERF_COUNT_SW_PAGE_FAULTS: currently this perf
event is used in an adhoc way across different archs.
Case (1): for many archs it's done at the entry of a page fault
handler, so that it will also cover e.g. errornous faults.
Case (2): for some other archs, it is only accounted when the page
fault is resolved successfully.
Case (3): there're still quite some archs that have not enabled
this perf event.
Since this series will touch merely all the archs, we unify this
perf event to always follow case (1), which is the one that makes most
sense. And since we moved the accounting into handle_mm_fault, the
other two MAJ/MIN perf events are well taken care of naturally.
- Unify definition of "major faults": the definition of "major
fault" is slightly changed when used in accounting (not
VM_FAULT_MAJOR). More information in patch 1.
- Always account the page fault onto the one that triggered the page
fault. This does not matter much for #PF handlings, but mostly for
gup. More information on this in patch 25.
Patchset layout:
Patch 1: Introduced the accounting in handle_mm_fault(), not enabled.
Patch 2-23: Enable the new accounting for arch #PF handlers one by one.
Patch 24: Enable the new accounting for the rest outliers (gup, iommu, etc.)
Patch 25: Cleanup GUP task_struct pointer since it's not needed any more
This patch (of 25):
This is a preparation patch to move page fault accountings into the
general code in handle_mm_fault(). This includes both the per task
flt_maj/flt_min counters, and the major/minor page fault perf events. To
do this, the pt_regs pointer is passed into handle_mm_fault().
PERF_COUNT_SW_PAGE_FAULTS should still be kept in per-arch page fault
handlers.
So far, all the pt_regs pointer that passed into handle_mm_fault() is
NULL, which means this patch should have no intented functional change.
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Brian Cain <bcain@codeaurora.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Chris Zankel <chris@zankel.net>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: David S. Miller <davem@davemloft.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: Greentime Hu <green.hu@gmail.com>
Cc: Guo Ren <guoren@kernel.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Helge Deller <deller@gmx.de>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: James E.J. Bottomley <James.Bottomley@HansenPartnership.com>
Cc: John Hubbard <jhubbard@nvidia.com>
Cc: Jonas Bonn <jonas@southpole.se>
Cc: Ley Foon Tan <ley.foon.tan@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>
Cc: Matt Turner <mattst88@gmail.com>
Cc: Max Filippov <jcmvbkbc@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Michal Simek <monstr@monstr.eu>
Cc: Nick Hu <nickhu@andestech.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Pekka Enberg <penberg@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Richard Henderson <rth@twiddle.net>
Cc: Rich Felker <dalias@libc.org>
Cc: Russell King <linux@armlinux.org.uk>
Cc: Stafford Horne <shorne@gmail.com>
Cc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Vasily Gorbik <gor@linux.ibm.com>
Cc: Vincent Chen <deanbo422@gmail.com>
Cc: Vineet Gupta <vgupta@synopsys.com>
Cc: Will Deacon <will@kernel.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Link: http://lkml.kernel.org/r/20200707225021.200906-1-peterx@redhat.com
Link: http://lkml.kernel.org/r/20200707225021.200906-2-peterx@redhat.com
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2020-08-12 01:37:44 +00:00
|
|
|
fault = handle_mm_fault(vma, addr, flags, NULL);
|
2017-10-24 07:25:00 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If we need to retry but a fatal signal is pending, handle the
|
2020-06-09 04:33:54 +00:00
|
|
|
* signal first. We do not need to release the mmap_lock because it
|
2017-10-24 07:25:00 +00:00
|
|
|
* would already be released in __lock_page_or_retry in mm/filemap.c.
|
|
|
|
*/
|
2020-04-02 04:08:06 +00:00
|
|
|
if (fault_signal_pending(fault, regs)) {
|
2017-10-24 07:25:00 +00:00
|
|
|
if (!user_mode(regs))
|
|
|
|
goto no_context;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (unlikely(fault & VM_FAULT_ERROR)) {
|
|
|
|
if (fault & VM_FAULT_OOM)
|
|
|
|
goto out_of_memory;
|
|
|
|
else if (fault & VM_FAULT_SIGBUS)
|
|
|
|
goto do_sigbus;
|
|
|
|
else
|
|
|
|
goto bad_area;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 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.
|
|
|
|
*/
|
nds32: Perf porting
This is the commit that porting the perf for nds32.
1.Raw event:
The raw events start with 'r'.
Usage:
perf stat -e rXYZ ./app
X: the index of performance counter.
YZ: the index(convert to hexdecimal) of events
Example:
'perf stat -e r101 ./app' means the counter 1 will count the instruction
event.
The index of counter and events can be found in
"Andes System Privilege Architecture Version 3 Manual".
Or you can perform the 'perf list' to find the symbolic name of raw events.
2.Perf mmap2:
Fix unexpected perf mmap2() page fault
When the mmap2() called by perf application,
you will encounter such condition:"failed to write."
With return value -EFAULT
This is due to the page fault caused by "reading" buffer
from the mapped legal address region to write to the descriptor.
The page_fault handler will get a VM_FAULT_SIGBUS return value,
which should not happens here.(Due to this is a read request.)
You can refer to kernel/events/core.c:perf_mmap_fault(...)
If "(vmf->pgoff && (vmf->flags & FAULT_FLAG_WRITE))" is evaluated
as true, you will get VM_FAULT_SIGBUS as return value.
However, this is not an write request. The flags which indicated
why the page fault happens is wrong.
Furthermore, NDS32 SPAv3 is not able to detect it is read or write.
It only know either it is instruction fetch or data access.
Therefore, by removing the wrong flag assignment(actually, the hardware
is not able to show the reason), we can fix this bug.
3.Perf multiple events map to same counter.
When there are multiple events map to the same counter, the counter
counts inaccurately. This is because each counter only counts one event
in the same time.
So when there are multiple events map to same counter, they have to take
turns in each context.
There are two solution:
1. Print the error message when multiple events map to the same counter.
But print the error message would let the program hang in loop. The ltp
(linux test program) would be failed when the program hang in loop.
2. Don't print the error message, the ltp would pass. But the user need to
have the knowledge that don't count the events which map to the same
counter, or the user will get the inaccurate results.
We choose method 2 for the solution
Signed-off-by: Nickhu <nickhu@andestech.com>
Acked-by: Greentime Hu <greentime@andestech.com>
Signed-off-by: Greentime Hu <greentime@andestech.com>
2018-10-25 02:24:15 +00:00
|
|
|
perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS, 1, regs, addr);
|
2017-10-24 07:25:00 +00:00
|
|
|
if (flags & FAULT_FLAG_ALLOW_RETRY) {
|
nds32: Perf porting
This is the commit that porting the perf for nds32.
1.Raw event:
The raw events start with 'r'.
Usage:
perf stat -e rXYZ ./app
X: the index of performance counter.
YZ: the index(convert to hexdecimal) of events
Example:
'perf stat -e r101 ./app' means the counter 1 will count the instruction
event.
The index of counter and events can be found in
"Andes System Privilege Architecture Version 3 Manual".
Or you can perform the 'perf list' to find the symbolic name of raw events.
2.Perf mmap2:
Fix unexpected perf mmap2() page fault
When the mmap2() called by perf application,
you will encounter such condition:"failed to write."
With return value -EFAULT
This is due to the page fault caused by "reading" buffer
from the mapped legal address region to write to the descriptor.
The page_fault handler will get a VM_FAULT_SIGBUS return value,
which should not happens here.(Due to this is a read request.)
You can refer to kernel/events/core.c:perf_mmap_fault(...)
If "(vmf->pgoff && (vmf->flags & FAULT_FLAG_WRITE))" is evaluated
as true, you will get VM_FAULT_SIGBUS as return value.
However, this is not an write request. The flags which indicated
why the page fault happens is wrong.
Furthermore, NDS32 SPAv3 is not able to detect it is read or write.
It only know either it is instruction fetch or data access.
Therefore, by removing the wrong flag assignment(actually, the hardware
is not able to show the reason), we can fix this bug.
3.Perf multiple events map to same counter.
When there are multiple events map to the same counter, the counter
counts inaccurately. This is because each counter only counts one event
in the same time.
So when there are multiple events map to same counter, they have to take
turns in each context.
There are two solution:
1. Print the error message when multiple events map to the same counter.
But print the error message would let the program hang in loop. The ltp
(linux test program) would be failed when the program hang in loop.
2. Don't print the error message, the ltp would pass. But the user need to
have the knowledge that don't count the events which map to the same
counter, or the user will get the inaccurate results.
We choose method 2 for the solution
Signed-off-by: Nickhu <nickhu@andestech.com>
Acked-by: Greentime Hu <greentime@andestech.com>
Signed-off-by: Greentime Hu <greentime@andestech.com>
2018-10-25 02:24:15 +00:00
|
|
|
if (fault & VM_FAULT_MAJOR) {
|
2017-10-24 07:25:00 +00:00
|
|
|
tsk->maj_flt++;
|
nds32: Perf porting
This is the commit that porting the perf for nds32.
1.Raw event:
The raw events start with 'r'.
Usage:
perf stat -e rXYZ ./app
X: the index of performance counter.
YZ: the index(convert to hexdecimal) of events
Example:
'perf stat -e r101 ./app' means the counter 1 will count the instruction
event.
The index of counter and events can be found in
"Andes System Privilege Architecture Version 3 Manual".
Or you can perform the 'perf list' to find the symbolic name of raw events.
2.Perf mmap2:
Fix unexpected perf mmap2() page fault
When the mmap2() called by perf application,
you will encounter such condition:"failed to write."
With return value -EFAULT
This is due to the page fault caused by "reading" buffer
from the mapped legal address region to write to the descriptor.
The page_fault handler will get a VM_FAULT_SIGBUS return value,
which should not happens here.(Due to this is a read request.)
You can refer to kernel/events/core.c:perf_mmap_fault(...)
If "(vmf->pgoff && (vmf->flags & FAULT_FLAG_WRITE))" is evaluated
as true, you will get VM_FAULT_SIGBUS as return value.
However, this is not an write request. The flags which indicated
why the page fault happens is wrong.
Furthermore, NDS32 SPAv3 is not able to detect it is read or write.
It only know either it is instruction fetch or data access.
Therefore, by removing the wrong flag assignment(actually, the hardware
is not able to show the reason), we can fix this bug.
3.Perf multiple events map to same counter.
When there are multiple events map to the same counter, the counter
counts inaccurately. This is because each counter only counts one event
in the same time.
So when there are multiple events map to same counter, they have to take
turns in each context.
There are two solution:
1. Print the error message when multiple events map to the same counter.
But print the error message would let the program hang in loop. The ltp
(linux test program) would be failed when the program hang in loop.
2. Don't print the error message, the ltp would pass. But the user need to
have the knowledge that don't count the events which map to the same
counter, or the user will get the inaccurate results.
We choose method 2 for the solution
Signed-off-by: Nickhu <nickhu@andestech.com>
Acked-by: Greentime Hu <greentime@andestech.com>
Signed-off-by: Greentime Hu <greentime@andestech.com>
2018-10-25 02:24:15 +00:00
|
|
|
perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS_MAJ,
|
|
|
|
1, regs, addr);
|
|
|
|
} else {
|
2017-10-24 07:25:00 +00:00
|
|
|
tsk->min_flt++;
|
nds32: Perf porting
This is the commit that porting the perf for nds32.
1.Raw event:
The raw events start with 'r'.
Usage:
perf stat -e rXYZ ./app
X: the index of performance counter.
YZ: the index(convert to hexdecimal) of events
Example:
'perf stat -e r101 ./app' means the counter 1 will count the instruction
event.
The index of counter and events can be found in
"Andes System Privilege Architecture Version 3 Manual".
Or you can perform the 'perf list' to find the symbolic name of raw events.
2.Perf mmap2:
Fix unexpected perf mmap2() page fault
When the mmap2() called by perf application,
you will encounter such condition:"failed to write."
With return value -EFAULT
This is due to the page fault caused by "reading" buffer
from the mapped legal address region to write to the descriptor.
The page_fault handler will get a VM_FAULT_SIGBUS return value,
which should not happens here.(Due to this is a read request.)
You can refer to kernel/events/core.c:perf_mmap_fault(...)
If "(vmf->pgoff && (vmf->flags & FAULT_FLAG_WRITE))" is evaluated
as true, you will get VM_FAULT_SIGBUS as return value.
However, this is not an write request. The flags which indicated
why the page fault happens is wrong.
Furthermore, NDS32 SPAv3 is not able to detect it is read or write.
It only know either it is instruction fetch or data access.
Therefore, by removing the wrong flag assignment(actually, the hardware
is not able to show the reason), we can fix this bug.
3.Perf multiple events map to same counter.
When there are multiple events map to the same counter, the counter
counts inaccurately. This is because each counter only counts one event
in the same time.
So when there are multiple events map to same counter, they have to take
turns in each context.
There are two solution:
1. Print the error message when multiple events map to the same counter.
But print the error message would let the program hang in loop. The ltp
(linux test program) would be failed when the program hang in loop.
2. Don't print the error message, the ltp would pass. But the user need to
have the knowledge that don't count the events which map to the same
counter, or the user will get the inaccurate results.
We choose method 2 for the solution
Signed-off-by: Nickhu <nickhu@andestech.com>
Acked-by: Greentime Hu <greentime@andestech.com>
Signed-off-by: Greentime Hu <greentime@andestech.com>
2018-10-25 02:24:15 +00:00
|
|
|
perf_sw_event(PERF_COUNT_SW_PAGE_FAULTS_MIN,
|
|
|
|
1, regs, addr);
|
|
|
|
}
|
2017-10-24 07:25:00 +00:00
|
|
|
if (fault & VM_FAULT_RETRY) {
|
|
|
|
flags |= FAULT_FLAG_TRIED;
|
|
|
|
|
2020-06-09 04:33:51 +00:00
|
|
|
/* No need to mmap_read_unlock(mm) as we would
|
2017-10-24 07:25:00 +00:00
|
|
|
* have already released it in __lock_page_or_retry
|
|
|
|
* in mm/filemap.c.
|
|
|
|
*/
|
|
|
|
goto retry;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-06-09 04:33:25 +00:00
|
|
|
mmap_read_unlock(mm);
|
2017-10-24 07:25:00 +00:00
|
|
|
return;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Something tried to access memory that isn't in our memory map..
|
|
|
|
* Fix it, but check if it's kernel or user first..
|
|
|
|
*/
|
|
|
|
bad_area:
|
2020-06-09 04:33:25 +00:00
|
|
|
mmap_read_unlock(mm);
|
2017-10-24 07:25:00 +00:00
|
|
|
|
|
|
|
bad_area_nosemaphore:
|
|
|
|
|
|
|
|
/* User mode accesses just cause a SIGSEGV */
|
|
|
|
|
|
|
|
if (user_mode(regs)) {
|
|
|
|
tsk->thread.address = addr;
|
|
|
|
tsk->thread.error_code = error_code;
|
|
|
|
tsk->thread.trap_no = entry;
|
2019-05-23 16:04:24 +00:00
|
|
|
force_sig_fault(SIGSEGV, si_code, (void __user *)addr);
|
2017-10-24 07:25:00 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
no_context:
|
|
|
|
|
|
|
|
/* Are we prepared to handle this kernel fault?
|
|
|
|
*
|
|
|
|
* (The kernel has valid exception-points in the source
|
|
|
|
* when it acesses user-memory. When it fails in one
|
|
|
|
* of those points, we find it in a table and do a jump
|
|
|
|
* to some fixup code that loads an appropriate error
|
|
|
|
* code)
|
|
|
|
*/
|
|
|
|
|
|
|
|
{
|
|
|
|
const struct exception_table_entry *entry;
|
|
|
|
|
|
|
|
if ((entry =
|
|
|
|
search_exception_tables(instruction_pointer(regs))) !=
|
|
|
|
NULL) {
|
|
|
|
/* Adjust the instruction pointer in the stackframe */
|
|
|
|
instruction_pointer(regs) = entry->fixup;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Oops. The kernel tried to access some bad page. We'll have to
|
|
|
|
* terminate things with extreme prejudice.
|
|
|
|
*/
|
|
|
|
|
|
|
|
bust_spinlocks(1);
|
|
|
|
pr_alert("Unable to handle kernel %s at virtual address %08lx\n",
|
|
|
|
(addr < PAGE_SIZE) ? "NULL pointer dereference" :
|
|
|
|
"paging request", addr);
|
|
|
|
|
|
|
|
show_pte(mm, addr);
|
|
|
|
die("Oops", regs, error_code);
|
|
|
|
bust_spinlocks(0);
|
|
|
|
do_exit(SIGKILL);
|
|
|
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We ran out of memory, or some other thing happened to us that made
|
|
|
|
* us unable to handle the page fault gracefully.
|
|
|
|
*/
|
|
|
|
|
|
|
|
out_of_memory:
|
2020-06-09 04:33:25 +00:00
|
|
|
mmap_read_unlock(mm);
|
2017-10-24 07:25:00 +00:00
|
|
|
if (!user_mode(regs))
|
|
|
|
goto no_context;
|
|
|
|
pagefault_out_of_memory();
|
|
|
|
return;
|
|
|
|
|
|
|
|
do_sigbus:
|
2020-06-09 04:33:25 +00:00
|
|
|
mmap_read_unlock(mm);
|
2017-10-24 07:25:00 +00:00
|
|
|
|
|
|
|
/* Kernel mode? Handle exceptions or die */
|
|
|
|
if (!user_mode(regs))
|
|
|
|
goto no_context;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Send a sigbus
|
|
|
|
*/
|
|
|
|
tsk->thread.address = addr;
|
|
|
|
tsk->thread.error_code = error_code;
|
|
|
|
tsk->thread.trap_no = entry;
|
2019-05-23 16:04:24 +00:00
|
|
|
force_sig_fault(SIGBUS, BUS_ADRERR, (void __user *)addr);
|
2017-10-24 07:25:00 +00:00
|
|
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
vmalloc_fault:
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* Synchronize this task's top level page-table
|
|
|
|
* with the 'reference' page table.
|
|
|
|
*
|
|
|
|
* Use current_pgd instead of tsk->active_mm->pgd
|
|
|
|
* since the latter might be unavailable if this
|
|
|
|
* code is executed in a misfortunately run irq
|
|
|
|
* (like inside schedule() between switch_mm and
|
|
|
|
* switch_to...).
|
|
|
|
*/
|
|
|
|
|
|
|
|
unsigned int index = pgd_index(addr);
|
|
|
|
pgd_t *pgd, *pgd_k;
|
2019-12-05 00:54:08 +00:00
|
|
|
p4d_t *p4d, *p4d_k;
|
2017-10-24 07:25:00 +00:00
|
|
|
pud_t *pud, *pud_k;
|
|
|
|
pmd_t *pmd, *pmd_k;
|
|
|
|
pte_t *pte_k;
|
|
|
|
|
|
|
|
pgd = (pgd_t *) __va(__nds32__mfsr(NDS32_SR_L1_PPTB)) + index;
|
|
|
|
pgd_k = init_mm.pgd + index;
|
|
|
|
|
|
|
|
if (!pgd_present(*pgd_k))
|
|
|
|
goto no_context;
|
|
|
|
|
2019-12-05 00:54:08 +00:00
|
|
|
p4d = p4d_offset(pgd, addr);
|
|
|
|
p4d_k = p4d_offset(pgd_k, addr);
|
|
|
|
if (!p4d_present(*p4d_k))
|
|
|
|
goto no_context;
|
|
|
|
|
|
|
|
pud = pud_offset(p4d, addr);
|
|
|
|
pud_k = pud_offset(p4d_k, addr);
|
2017-10-24 07:25:00 +00:00
|
|
|
if (!pud_present(*pud_k))
|
|
|
|
goto no_context;
|
|
|
|
|
|
|
|
pmd = pmd_offset(pud, addr);
|
|
|
|
pmd_k = pmd_offset(pud_k, addr);
|
|
|
|
if (!pmd_present(*pmd_k))
|
|
|
|
goto no_context;
|
|
|
|
|
|
|
|
if (!pmd_present(*pmd))
|
|
|
|
set_pmd(pmd, *pmd_k);
|
|
|
|
else
|
|
|
|
BUG_ON(pmd_page(*pmd) != pmd_page(*pmd_k));
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Since the vmalloc area is global, we don't
|
|
|
|
* need to copy individual PTE's, it is enough to
|
|
|
|
* copy the pgd pointer into the pte page of the
|
|
|
|
* root task. If that is there, we'll find our pte if
|
|
|
|
* it exists.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* Make sure the actual PTE exists as well to
|
|
|
|
* catch kernel vmalloc-area accesses to non-mapped
|
|
|
|
* addres. If we don't do this, this will just
|
|
|
|
* silently loop forever.
|
|
|
|
*/
|
|
|
|
|
|
|
|
pte_k = pte_offset_kernel(pmd_k, addr);
|
|
|
|
if (!pte_present(*pte_k))
|
|
|
|
goto no_context;
|
|
|
|
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|