From: "Zhang, Yanmin" <yanmin.zhang@intel.com>
To: <prasanna@in.ibm.com>
Cc: <systemtap@sources.redhat.com>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
"Mao, Bibo" <bibo.mao@intel.com>
Subject: RE: Review patches of user space kprobe
Date: Mon, 09 Jan 2006 02:06:00 -0000 [thread overview]
Message-ID: <8126E4F969BA254AB43EA03C59F44E8404692DBE@pdsmsx404> (raw)
>>-----Original Message-----
>>From: systemtap-owner@sourceware.org [mailto:systemtap-owner@sourceware.org] On Behalf Of Prasanna S Panchamukhi
>>Sent: 2006年1月6日 18:26
>>To: Zhang, Yanmin
>>Cc: systemtap@sources.redhat.com; Keshavamurthy, Anil S; Mao, Bibo
>>Subject: Re: Review patches of user space kprobe
>>> >>This is done to make use of register_kprobe(), the address returned by
>>> >>kmap_atomic is passed to register_kprobe() and even though the kernel data
>>> >>address is stored at kp.addr, that is enough to distinguish between
>>> >>kernel probes.
>>> Is it true on all arch? I don't think it's safe to do so. Actually, register_kprobe just needs know it's a uprobe.
>>yes, otherwise need to find out a way to pass the mapped address to register_kprobe(). All this can be avoided
>>if register_kprobe() is bypassed :).
It's a good solution if register_kprobe is bypassed.
next reply other threads:[~2006-01-09 2:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 2:06 Zhang, Yanmin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 2:04 Zhang, Yanmin
2006-01-09 1:48 Zhang, Yanmin
2006-01-06 9:12 Zhang, Yanmin
2006-01-06 9:28 ` Prasanna S Panchamukhi
2006-01-06 9:08 Zhang, Yanmin
2006-01-06 10:22 ` Prasanna S Panchamukhi
2006-01-06 10:30 ` Roland McGrath
2006-01-06 5:29 Zhang, Yanmin
2006-01-06 9:08 ` Prasanna S Panchamukhi
2006-01-06 5:22 Zhang, Yanmin
2006-01-06 9:04 ` Prasanna S Panchamukhi
2006-01-06 4:27 Zhang, Yanmin
2006-01-06 12:28 ` Prasanna S Panchamukhi
2006-01-06 3:20 Zhang, Yanmin
2006-01-06 8:53 ` Prasanna S Panchamukhi
2006-01-06 2:52 Zhang, Yanmin
2006-01-06 6:53 ` Prasanna S Panchamukhi
2006-01-05 7:09 Zhang, Yanmin
2006-01-05 11:27 ` Prasanna S Panchamukhi
2005-12-22 13:24 Zhang, Yanmin
2006-01-05 11:10 ` Prasanna S Panchamukhi
2005-12-22 7:14 Zhang, Yanmin
2005-12-22 5:41 Zhang, Yanmin
2005-12-22 6:00 ` Vara Prasad
2006-01-05 11:06 ` Prasanna S Panchamukhi
2005-12-22 5:34 Zhang, Yanmin
2006-01-05 10:30 ` Prasanna S Panchamukhi
2005-12-22 5:09 Zhang, Yanmin
2006-01-05 10:29 ` Prasanna S Panchamukhi
2005-12-21 8:31 Zhang, Yanmin
2006-01-05 10:28 ` Prasanna S Panchamukhi
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=8126E4F969BA254AB43EA03C59F44E8404692DBE@pdsmsx404 \
--to=yanmin.zhang@intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=bibo.mao@intel.com \
--cc=prasanna@in.ibm.com \
--cc=systemtap@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).