From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: oleg@redhat.com, srikar@linux.vnet.ibm.com, rostedt@goodmis.org,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, linux-doc@vger.kernel.org,
ananth@linux.vnet.ibm.com, alexis.berlemont@gmail.com,
naveen.n.rao@linux.vnet.ibm.com,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH 0/7] Uprobes: Support SDT markers having reference count (semaphore)
Date: Sat, 16 Jun 2018 20:37:24 +0530 [thread overview]
Message-ID: <fa2a2578-1f39-8858-afa0-d8076aa5bc15@linux.ibm.com> (raw)
In-Reply-To: <20180616225032.3fc9a027dca76926ff198ff8@kernel.org>
Hi Masami,
On 06/16/2018 07:20 PM, Masami Hiramatsu wrote:
> Hi Ravi,
>
> Sorry for replying later.
No issues :)
>
> On Mon, 11 Jun 2018 10:01:58 +0530
> Ravi Bangoria <ravi.bangoria@linux.ibm.com> wrote:
>
>> Hi Masami,
>>
>>>>> Hmm, it sounds simple... maybe we can increment refctr in install_breakpoint/
>>>>> remove_breakpoint?
>>>>
>>>> Not really, it would be simpler if I can put it inside install_breakpoint().
>>>> Consider an mmap() case. Probed instruction resides in the text section whereas
>>>> reference counter resides in the data section. These sections gets mapped using
>>>> separate mmap() calls. So, when process mmaps the text section we will change the
>>>> instruction, but section holding the reference counter may not have been mapped
>>>> yet in the virtual memory. If so, we will fail to update the reference counter.
>>>
>>> Got it.
>>> In such case, maybe we can hook the target page mmapped and do install_breakpoint()
>>> at that point. Since the instruction is protected by a refctr, unless mmap the
>>> page on where the refctr is, the program doesn't reach the tracepoint. Is that right?
>>>
>>
>> You mean, when mmap(text) happens, save the target page somewhere and when
>> mmap(data) happens, update both instruction and ref_ctr?
>
> Yes. I think you can just clone the target(text) page but not install
> breakpoint, and if mmap(data) happens, update both.
I'm preparing a prototype according to this. The only difference in my approach is,
I'm not delaying instruction update. I.e. let instruction update happen as it is,
just mark that uprobe as delayed. Whenever vma holding reference counter gets mapped,
update the reference counter.
Will post the series soon.
Thanks for the reply,
Ravi
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-16 15:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 8:33 [PATCH 0/7] Uprobes: Support SDT markers having reference count (semaphore) Ravi Bangoria
2018-06-06 8:33 ` [PATCH 1/7] Uprobes: Simplify uprobe_register() body Ravi Bangoria
2018-06-06 8:33 ` [PATCH 2/7] Uprobes: Support SDT markers having reference count (semaphore) Ravi Bangoria
2018-06-06 8:33 ` [PATCH 3/7] Uprobes/sdt: Fix multiple update of same reference counter Ravi Bangoria
2018-06-06 8:33 ` [PATCH 4/7] trace_uprobe/sdt: Prevent multiple reference counter for same uprobe Ravi Bangoria
2018-06-06 8:33 ` [PATCH 5/7] Uprobes/sdt: " Ravi Bangoria
2018-06-06 8:33 ` [PATCH 6/7] Uprobes/sdt: Document about reference counter Ravi Bangoria
2018-06-06 8:33 ` [PATCH 7/7] perf probe: Support SDT markers having reference counter (semaphore) Ravi Bangoria
2018-06-06 8:35 ` [PATCH 0/7] Uprobes: Support SDT markers having reference count (semaphore) Ravi Bangoria
2018-06-08 1:10 ` Masami Hiramatsu
2018-06-08 2:29 ` Ravi Bangoria
2018-06-08 5:14 ` Masami Hiramatsu
2018-06-08 6:34 ` Ravi Bangoria
2018-06-08 15:45 ` Masami Hiramatsu
2018-06-11 4:31 ` Ravi Bangoria
2018-06-16 13:50 ` Masami Hiramatsu
2018-06-16 15:07 ` Ravi Bangoria [this message]
2018-06-08 16:36 ` Oleg Nesterov
2018-06-11 4:13 ` Ravi Bangoria
2018-06-20 16:37 ` Steven Rostedt
2018-06-21 2:35 ` Ravi Bangoria
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=fa2a2578-1f39-8858-afa0-d8076aa5bc15@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexis.berlemont@gmail.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=jolsa@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).