From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] Test pid_ns in local build
Date: Wed, 25 Sep 2019 14:03:50 -0400 [thread overview]
Message-ID: <CA+jJMxtPN3NdSPKTzoFa0hW37sG-pSwDmVXf4g3mxzR+ixQrqg@mail.gmail.com> (raw)
In-Reply-To: <8132a2ff30f649c49c50246545302804@SVR-IES-MBX-04.mgc.mentorg.com>
On Thu, 19 Sep 2019 at 02:12, Polzer, Franz <Franz_Polzer at mentor.com> wrote:
>
> Hi Michael,
>
> Many thanks for your help!
>
> Is there any schedule bringing that feature into LTTng master?
Hi,
I can't give you an exact time line, but within the next 3-4 weeks.
J?r?mie
>
> Thanks and br,
> Franz
>
> -----Original Message-----
> From: lttng-dev [mailto:lttng-dev-bounces@lists.lttng.org] On Behalf Of Michael Jeanson
> Sent: Dienstag, 17. September 2019 16:06
> To: lttng-dev at lists.lttng.org
> Subject: Re: [lttng-dev] Test pid_ns in local build
>
> On 2019-09-17 4:03 a.m., Polzer, Franz wrote:
> > Hello,
> >
> > I wanted to give the pid_ns context tracing a try and built LTTng from
> > master, but I get the following error when applying this command:
> >
> > lttng add-context -k -t procname -t pid -t vpid -t tid -t vtid -t
> > pid_ns
> >
> > Error: Unknown context type pid_ns
> >
> > Maybe I need another branch to build from to get that feature in or
> > forgot to enable the feature during building?
> >
> > Where can I find documentation about the pid_ns tracing and how to
> > test the current version of that implementation?
> >
> > Thanks for your help and best regards,
> >
> > Franz
>
>
> Hi,
>
> The namespace statedump and contexts feature has not been merged in master yet. You can get it from my github in the "ns" feature branches.
>
> https://github.com/mjeanson/lttng-modules/tree/ns
> https://github.com/mjeanson/lttng-ust/tree/ns
> https://github.com/mjeanson/lttng-tools/tree/ns
>
> It's a bit out of date but should work as-is, or it can be easily rebased on current master branches.
>
>
> Cheers,
>
> Michael
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
J?r?mie Galarneau
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2019-09-25 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a49b436d1cd4659b96dfcaffe63b38e@SVR-IES-MBX-04.mgc.mentorg.com>
[not found] ` <e01b5c8b-9534-e726-e5cd-eb499ef3bc43@efficios.com>
2019-09-19 6:10 ` Polzer, Franz
2019-09-25 18:03 ` Jérémie Galarneau [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=CA+jJMxtPN3NdSPKTzoFa0hW37sG-pSwDmVXf4g3mxzR+ixQrqg@mail.gmail.com \
--to=jeremie.galarneau@efficios.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