From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
Fenghua Yu <fenghua.yu@intel.com>,
arcml <linux-snps-arc@lists.infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] mm: Generalize and rename notify_page_fault() as kprobe_page_fault()
Date: Tue, 18 Jun 2019 08:56:33 -0700 [thread overview]
Message-ID: <8b184218-6880-204e-a9dd-e627c5ca92ca@synopsys.com> (raw)
In-Reply-To: <e5f45089-c3aa-4d78-2c8d-ed22f863d9ee@synopsys.com>
+CC Masami San, Eugeniy
On 6/13/19 10:57 AM, Vineet Gupta wrote:
> On 6/13/19 3:07 AM, Anshuman Khandual wrote:
>> Questions:
>>
>> AFAICT there is no equivalent of erstwhile notify_page_fault() during page
>> fault handling in arc and mips archs which can call this generic function.
>> Please let me know if that is not the case.
>
> For ARC do_page_fault() is entered for MMU exceptions (TLB Miss, access violations
> r/w/x etc). kprobes uses a combination of UNIMP_S and TRAP_S instructions which
> don't funnel into do_page_fault().
>
> UINMP_S leads to
>
> instr_service
> do_insterror_or_kprobe
> notify_die(DIE_IERR)
> kprobe_exceptions_notify
> arc_kprobe_handler
>
>
> TRAP_S 2 leads to
>
> EV_Trap
> do_non_swi_trap
> trap_is_kprobe
> notify_die(DIE_TRAP)
> kprobe_exceptions_notify
> arc_post_kprobe_handler
>
> But indeed we are *not* calling into kprobe_fault_handler() - from eithet of those
> paths and not sure if the existing arc*_kprobe_handler() combination does the
> equivalent in tandem.
@Eugeniy can you please investigate this - do we have krpobes bit rot in ARC port.
-Vineet
next prev parent reply other threads:[~2019-06-18 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 10:07 [PATCH] mm: Generalize and rename notify_page_fault() as kprobe_page_fault() Anshuman Khandual
2019-06-13 17:57 ` Vineet Gupta
2019-06-18 15:56 ` Vineet Gupta [this message]
2019-06-20 7:19 ` Masami Hiramatsu
2019-06-13 20:04 ` Andrew Morton
2019-06-14 5:15 ` Anshuman Khandual
2019-06-29 14:50 ` Guenter Roeck
2019-06-30 4:41 ` Anshuman Khandual
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=8b184218-6880-204e-a9dd-e627c5ca92ca@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=anshuman.khandual@arm.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mhiramat@kernel.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