public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: masami.hiramatsu.pt@hitachi•com (Masami Hiramatsu)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RFC 2/6] arm64: Kprobes with single stepping support
Date: Thu, 14 Nov 2013 01:05:23 +0900	[thread overview]
Message-ID: <5283A343.1000305@hitachi.com> (raw)
In-Reply-To: <20131112115935.23d05236@gandalf.local.home>

(2013/11/13 1:59), Steven Rostedt wrote:
> On Tue, 12 Nov 2013 16:25:26 +0530
> Sandeepa Prabhu <sandeepa.prabhu@linaro•org> wrote:
> 
> 
>>>
>>> BTW, I'm currently trying a general housecleaning of __kprobes
>>> annotations. It may also have impact on your patch.
>>> https://lkml.org/lkml/2013/11/8/187
>> Hmm, we can help testing your patchset on arm64 platforms. Also have
>> many doubts on the changes you are working [blacklisting probes etc]
>>
>> Basically I had tried placing kprobe on memcpy() and the model hung
>> (insmod never returned back!). Fast-model I have does not have option
>> of any debug so no clue what happened!.
>> memcpy() is low-level call being used internally within kprobes, so
>> probably we cannot handle probe on that routine, but then how to make
>> sure all such API are rejected by kprobe sub-system ?
> 
> Working on ports of ftrace, I found that many of the functions in lib/
> are used by several locations that just can't be traced, due to how
> low level they are. I just simply blacklisted the entire lib/
> directory (See the top of lib/Makefile)
> 
> I wonder if there's an easy way to blacklist entire directories from
> being used by kprobes too. Or at least do it by a file per file basis.

Hm, perhaps we can do some magic in post-build script as kallsyms does.
1) make an object file
2) extract symbols from the file
3) put the symbols into data section as a list of strings
4) analyze the list at boot (init) time by using kallsyms
how about this? :)

Thank you,

-- 
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt at hitachi.com

  reply	other threads:[~2013-11-13 16:05 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 11:17 [PATCH RFC v2 0/6] ARM64: Add kernel probes(Kprobes) support Sandeepa Prabhu
2013-10-17 11:17 ` [PATCH RFC v4 1/6] arm64: support single-step and breakpoint handler hooks Sandeepa Prabhu
2013-10-25 15:22   ` Will Deacon
2013-12-03 14:33     ` Sandeepa Prabhu
2013-12-03 19:44       ` Will Deacon
2013-10-17 11:17 ` [PATCH RFC 2/6] arm64: Kprobes with single stepping support Sandeepa Prabhu
2013-11-08 16:56   ` Will Deacon
2013-11-09  9:10     ` Masami Hiramatsu
2013-11-11  5:39       ` Sandeepa Prabhu
2013-11-11  7:54         ` Masami Hiramatsu
2013-11-11 10:51           ` Masami Hiramatsu
2013-11-11 10:58             ` Will Deacon
2013-11-11 17:32               ` Masami Hiramatsu
2013-11-12  6:23                 ` Sandeepa Prabhu
2013-11-12  7:27                   ` Masami Hiramatsu
2013-11-12  8:44                     ` Sandeepa Prabhu
2013-11-12 10:17                       ` Masami Hiramatsu
2013-11-12 10:55                         ` Sandeepa Prabhu
2013-11-12 14:11                           ` Masami Hiramatsu
2013-11-12 16:59                           ` Steven Rostedt
2013-11-13 16:05                             ` Masami Hiramatsu [this message]
     [not found]                     ` <CA+b37P1sNsEXrJFfVL51sZ-SeGNCBiwXnOwCiFY8CBwSXPw+mQ@mail.gmail.com>
2013-11-13  7:08                       ` Sandeepa Prabhu
2013-11-13 14:07                       ` Masami Hiramatsu
2013-11-13 14:31                       ` Will Deacon
2013-11-13 15:55                         ` Sandeepa Prabhu
2013-11-15 16:39                           ` Will Deacon
2013-11-18  6:55                             ` Sandeepa Prabhu
2013-11-18  8:51                               ` Sandeepa Prabhu
2013-11-13 13:58               ` Peter Zijlstra
2013-11-13 14:20                 ` Will Deacon
2013-11-11  5:35     ` Sandeepa Prabhu
2013-11-11 11:21       ` Will Deacon
2013-11-12  6:52         ` Sandeepa Prabhu
2013-11-15 16:37           ` Will Deacon
2013-11-18  6:43             ` Sandeepa Prabhu
2013-10-17 11:17 ` [PATCH RFC 3/6] arm64: Kprobes instruction simulation support Sandeepa Prabhu
2013-11-08 17:03   ` Will Deacon
2013-11-11  5:58     ` Sandeepa Prabhu
2013-10-17 11:17 ` [PATCH RFC 4/6] arm64: Add kernel return probes support(kretprobes) Sandeepa Prabhu
2013-11-08 17:04   ` Will Deacon
2013-11-11  4:29     ` Sandeepa Prabhu
2013-11-11  7:53       ` AKASHI Takahiro
2013-11-11  8:55         ` Sandeepa Prabhu
2013-10-17 11:17 ` [PATCH RFC 5/6] arm64: Enable kprobes support for arm64 platform Sandeepa Prabhu
2013-10-17 11:17 ` [PATCH RFC 6/6] kprobes: Add cases for arm and arm64 in sample module Sandeepa Prabhu
2013-10-25 15:24   ` Will Deacon
2013-11-06 11:05     ` Sandeepa Prabhu
2013-10-18  8:32 ` [PATCH RFC v2 0/6] ARM64: Add kernel probes(Kprobes) support Masami Hiramatsu
2013-10-21  4:17   ` Sandeepa Prabhu

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=5283A343.1000305@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /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