From: Masami Hiramatsu <mhiramat@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: uprobe support mix of ftrace and perf
Date: Mon, 26 Nov 2018 17:16:34 +0900 [thread overview]
Message-ID: <20181126171634.a68dbf9d7ce40e8c982ffec6@kernel.org> (raw)
In-Reply-To: <20181122143209.GE28270@redhat.com>
Hi Oleg,
On Thu, 22 Nov 2018 15:32:10 +0100
Oleg Nesterov <oleg@redhat.com> wrote:
> Hi Masami,
>
> On 11/20, Masami Hiramatsu wrote:
> >
> > Hello Oleg,
> >
> > I have a question about the (revert) commit 48212542067a
> > ("tracing/uprobes: Revert "Support mix of ftrace and perf""). I found
> > this limitation still exists on uprobe events.
>
> Yes...
>
> > Would you have any plan or idea to fix this issue? I thought this revert
> > patch was a tentative one, and should be fixed afterwards.
>
> To be honest, I was going to fix this "soon" many years ago, but today I simply
> can't recall how this code actually works and what exactly we need to do to
> support ftrace/perf at the same time...
>
> I'll try to read this code later, but I can't promise anything :/
I understand, it may take a while... no need to promise :). I'll also look
into it.
Thank you,
>
> Oleg.
>
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2018-11-26 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 13:01 uprobe support mix of ftrace and perf Masami Hiramatsu
2018-11-22 14:32 ` Oleg Nesterov
2018-11-26 8:16 ` Masami Hiramatsu [this message]
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=20181126171634.a68dbf9d7ce40e8c982ffec6@kernel.org \
--to=mhiramat@kernel.org \
--cc=jovi.zhangwei@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=tom.zanussi@linux.intel.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).