From: Steven Rostedt <rostedt@goodmis.org>
To: Jeff Xie <xiehuan09@gmail.com>
Cc: mingo@redhat.com, mhiramat@kernel.org, zanussi@kernel.org,
linux-kernel@vger.kernel.org, chensong_2000@189.cn
Subject: Re: [PATCH v15 2/4] trace/objtrace: Get the value of the object
Date: Wed, 28 Sep 2022 10:40:17 -0400 [thread overview]
Message-ID: <20220928104017.73cbe8eb@gandalf.local.home> (raw)
In-Reply-To: <CAEr6+EAHVUntQMVAC0_Rm7A2wWWC9TZsYi4PgV-tdO0bvUKguA@mail.gmail.com>
On Wed, 28 Sep 2022 22:15:24 +0800
Jeff Xie <xiehuan09@gmail.com> wrote:
> > > > > This code is available in the kprobe code that eprobes also uses:
> > > > >
> > > > > See process_fetch_insn() in kernel/trace/trace_eprobe.c
> > > > >
> > > > > and the parsing of the string is in kernel/trace/trace_probe.c:
> > > > >
> > > > > parse_probe_arg()
>
> I guess I won't be able to finish it until the next merge window, I've
> been trying it for a few days
Yeah, the merge window is expected to open next week, so it likely will not
be able to make that. But hopefully the next window it will!
> In my spare time recently, with no progress, it looks like it's really
> more complicated to implement ;-)
Yeah, I was playing with it too. It is complicated, but I do not see any
show stoppers from getting it working.
-- Steve
next prev parent reply other threads:[~2022-09-28 14:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 3:27 [PATCH v15 0/4] trace: Introduce objtrace trigger to trace the kernel object Jeff Xie
2022-08-19 3:27 ` [PATCH v15 1/4] trace: Add trace any " Jeff Xie
2022-10-17 19:58 ` Steven Rostedt
2022-10-18 8:35 ` Jeff Xie
2022-08-19 3:27 ` [PATCH v15 2/4] trace/objtrace: Get the value of the object Jeff Xie
2022-09-24 20:01 ` Steven Rostedt
2022-09-25 5:27 ` Jeff Xie
2022-09-25 15:53 ` Steven Rostedt
2022-09-25 16:49 ` Jeff Xie
2022-09-28 14:15 ` Jeff Xie
2022-09-28 14:40 ` Steven Rostedt [this message]
2022-08-19 3:27 ` [PATCH v15 3/4] selftests/ftrace: Add testcases for objtrace Jeff Xie
2022-08-19 3:27 ` [PATCH v15 4/4] Documentation: trace/objtrace: Add documentation " Jeff Xie
2022-10-17 19:40 ` [PATCH v15 0/4] trace: Introduce objtrace trigger to trace the kernel object Steven Rostedt
2022-10-18 7:01 ` Jeff Xie
2022-11-29 16:09 ` Jeff Xie
2022-11-29 16:30 ` Steven Rostedt
2022-12-17 8:27 ` Jeff Xie
2023-01-31 9:55 ` Jeff Xie
2023-01-31 15:36 ` Steven Rostedt
2023-01-31 15:48 ` Jeff Xie
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=20220928104017.73cbe8eb@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chensong_2000@189.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=xiehuan09@gmail.com \
--cc=zanussi@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
all inboxes | Powered by JetHome®