From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: akpm@linux-foundation.org, aneesh.kumar@linux.ibm.com,
carmenjackson@google.com, dan.j.williams@intel.com,
dancol@google.com, jglisse@redhat.com, linux-mm@kvack.org,
mayankgupta@google.com, mhocko@suse.com, minchan@kernel.org,
mm-commits@vger.kernel.org, rcampbell@nvidia.com,
timmurray@google.com, torvalds@linux-foundation.org,
vbabka@suse.cz, willy@infradead.org, primiano@google.com
Subject: Re: [patch 026/158] mm: emit tracepoint when RSS changes
Date: Mon, 2 Dec 2019 18:53:24 -0500 [thread overview]
Message-ID: <20191202185324.30b502bb@gandalf.local.home> (raw)
In-Reply-To: <20191202234514.GR17234@google.com>
On Mon, 2 Dec 2019 18:45:14 -0500
Joel Fernandes <joel@joelfernandes.org> wrote:
>
> I would love for that to happen but I don't develop Perfetto much. If I am
> writing a tool I will definitely give it a go from my side. CC'ing Perfetto's
> lead developer Primiano -- I believe you have already met Primiano at a
> conference before as he mentioned it to me that you guys met. I also believe
> this topic of using a common library was discussed before, but something
> about licensing came up.
libtraceevent is under LGPL, is that an issue?
-- Steve
next prev parent reply other threads:[~2019-12-02 23:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 1:50 [patch 026/158] mm: emit tracepoint when RSS changes akpm
2019-12-02 17:14 ` Steven Rostedt
2019-12-02 21:13 ` Joel Fernandes
2019-12-02 21:56 ` Steven Rostedt
2019-12-02 23:45 ` Joel Fernandes
2019-12-02 23:53 ` Steven Rostedt [this message]
2019-12-03 2:48 ` Primiano Tucci
2019-12-03 5:38 ` Mathieu Desnoyers
2019-12-03 10:44 ` Primiano Tucci
2019-12-03 15:58 ` Steven Rostedt
2019-12-04 4:08 ` Joel Fernandes
2019-12-03 14:53 ` Steven Rostedt
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=20191202185324.30b502bb@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=carmenjackson@google.com \
--cc=dan.j.williams@intel.com \
--cc=dancol@google.com \
--cc=jglisse@redhat.com \
--cc=joel@joelfernandes.org \
--cc=linux-mm@kvack.org \
--cc=mayankgupta@google.com \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=primiano@google.com \
--cc=rcampbell@nvidia.com \
--cc=timmurray@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).