From: "Christophe Bédard via lttng-dev" <lttng-dev@lists.lttng.org>
To: Genevieve Bastien <gbastien@versatic.net>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: Correctly using callstack-user context
Date: Wed, 13 May 2020 11:34:55 -0400 [thread overview]
Message-ID: <CAAS9dobBZRWw3WkZQrn2UGkHC1+tuS0BLmZCJxpxSQvDjG7oxg@mail.gmail.com> (raw)
In-Reply-To: <bdeb584b-7c42-9e26-ce10-a1b008212541@versatic.net>
[-- Attachment #1.1: Type: text/plain, Size: 572 bytes --]
On Wed, 13 May 2020 at 10:18, Genevieve Bastien via lttng-dev <
lttng-dev@lists.lttng.org> wrote:
> We had a very very experimental branch with it, using backtrace first,
> then unwind. But it is not suggested, not performant. It's far from the
> correct desired implementation, for which Mathieu could give more details.
>
> It works, but not to be used in production. Students have used it in the
> lab for some specific use case prototyping. I won't share the branch here,
> but if you wish to try, let me know.
>
> Geneviève
>
Sure, I'd be interested!
[-- Attachment #1.2: Type: text/html, Size: 1069 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
WARNING: multiple messages have this Message-ID (diff)
From: "Christophe Bédard via lttng-dev" <lttng-dev@lists.lttng.org>
To: Genevieve Bastien <gbastien@versatic.net>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Correctly using callstack-user context
Date: Wed, 13 May 2020 11:34:55 -0400 [thread overview]
Message-ID: <CAAS9dobBZRWw3WkZQrn2UGkHC1+tuS0BLmZCJxpxSQvDjG7oxg@mail.gmail.com> (raw)
Message-ID: <20200513153455.QVzuGmn1nZf0NeHFlq2nMT3GhbS_xnKIadBxiBRALOg@z> (raw)
In-Reply-To: <bdeb584b-7c42-9e26-ce10-a1b008212541@versatic.net>
[-- Attachment #1.1: Type: text/plain, Size: 572 bytes --]
On Wed, 13 May 2020 at 10:18, Genevieve Bastien via lttng-dev <
lttng-dev@lists.lttng.org> wrote:
> We had a very very experimental branch with it, using backtrace first,
> then unwind. But it is not suggested, not performant. It's far from the
> correct desired implementation, for which Mathieu could give more details.
>
> It works, but not to be used in production. Students have used it in the
> lab for some specific use case prototyping. I won't share the branch here,
> but if you wish to try, let me know.
>
> Geneviève
>
Sure, I'd be interested!
[-- Attachment #1.2: Type: text/html, Size: 1069 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-05-13 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 21:09 Correctly using callstack-user context Christophe Bédard via lttng-dev
2020-05-11 21:09 ` [lttng-dev] " Christophe Bédard via lttng-dev
2020-05-12 12:27 ` Mathieu Desnoyers via lttng-dev
2020-05-12 12:27 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
2020-05-13 13:42 ` Christophe Bédard via lttng-dev
2020-05-13 13:42 ` [lttng-dev] " Christophe Bédard via lttng-dev
2020-05-13 14:02 ` Genevieve Bastien via lttng-dev
2020-05-13 14:02 ` [lttng-dev] " Genevieve Bastien via lttng-dev
2020-05-13 15:34 ` Christophe Bédard via lttng-dev [this message]
2020-05-13 15:34 ` Christophe Bédard via lttng-dev
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=CAAS9dobBZRWw3WkZQrn2UGkHC1+tuS0BLmZCJxpxSQvDjG7oxg@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=bedard.christophe@gmail.com \
--cc=gbastien@versatic.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.