From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Pavel Odintsov <pavel.odintsov@gmail.com>,
Andrew Vagin <avagin@parallels.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] [RFC] kernel: add a netlink interface to get information about processes
Date: Fri, 27 Feb 2015 18:50:15 -0300 [thread overview]
Message-ID: <20150227215015.GD28401@kernel.org> (raw)
In-Reply-To: <54F0D96B.3050409@gmail.com>
Em Fri, Feb 27, 2015 at 01:54:03PM -0700, David Ahern escreveu:
> On 2/27/15 1:43 PM, Arnaldo Carvalho de Melo wrote:
>
> > From the subject line, there is patchkit, but I couldn't find it... Can
> >you resend it to me or point me to some url where I can get it?
>
> https://lkml.org/lkml/2015/2/17/64
Yeah, I eventually found it, this would be great for perf:
Another good feature of task_diag is an ability to request information
for a few processes. Currently here are two stratgies
TASK_DIAG_DUMP_ALL - get information for all tasks
TASK_DIAG_DUMP_CHILDREN - get information for children of a specified
tasks
I.e. 'perf record -a' would use that TASK_DIAG_DUMP_ALL to synthesize
PERF_RECORD_{FORK,COMM} events, we would still need some way to generate
the PERF_RECORD_MMAP entries tho.
- Arnaldo
next prev parent reply other threads:[~2015-02-27 21:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 13:00 [PATCH 0/7] [RFC] kernel: add a netlink interface to get information about processes Pavel Odintsov
2015-02-27 20:43 ` Arnaldo Carvalho de Melo
2015-02-27 20:54 ` David Ahern
2015-02-27 21:50 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-19 12:50 Pavel Odintsov
2015-02-17 8:20 Andrey Vagin
2015-02-17 8:53 ` Arnd Bergmann
2015-02-17 21:33 ` Andrew Vagin
2015-02-18 11:06 ` Arnd Bergmann
2015-02-18 12:42 ` Andrew Vagin
2015-02-18 14:46 ` Arnd Bergmann
2015-02-19 14:04 ` Andrew Vagin
2015-02-17 16:09 ` David Ahern
2015-02-17 20:32 ` Andrew Vagin
2015-02-17 19:05 ` Andy Lutomirski
2015-02-18 14:27 ` Andrew Vagin
2015-02-19 1:18 ` Andy Lutomirski
2015-02-19 21:39 ` Andrew Vagin
2015-02-20 20:33 ` Andy Lutomirski
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=20150227215015.GD28401@kernel.org \
--to=acme@kernel.org \
--cc=avagin@parallels.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel.odintsov@gmail.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