From: Serica via lttng-dev <lttng-dev@lists.lttng.org>
To: =?gb18030?B?TWF0aGlldSBEZXNub3llcnM=?= <mathieu.desnoyers@efficios.com>
Cc: =?gb18030?B?bHR0bmctZGV2?= <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] =?gb18030?b?u9i4tKO6ICBFbmFtZWJsaW5nIG5hbWVzcGFjZSBj?= =?gb18030?q?ontexts?=
Date: Tue, 29 Dec 2020 21:18:57 +0800 [thread overview]
Message-ID: <tencent_4C429FE980FC54AC7AC796244B4048B19805@qq.com> (raw)
In-Reply-To: <1510592650.3765.1609214285939.JavaMail.zimbra@efficios.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset="gb18030", Size: 4912 bytes --]
Hi,
The version of my lttng is: lttng (LTTng Trace Control) 2.10.7 - KeKriek.
The output of "lttng add-context --list" is as follows:
pid
procname
prio
nice
vpid
tid
pthread_id
vtid
ppid
vppid
hostname
ip
interruptible
preemptible
need_reschedule
migratable
perf:cpu:cpu-cycles
perf:cpu:cycles
perf:cpu:stalled-cycles-frontend
perf:cpu:idle-cycles-frontend
perf:cpu:stalled-cycles-backend
perf:cpu:idle-cycles-backend
perf:cpu:instructions
perf:cpu:cache-references
perf:cpu:cache-misses
perf:cpu:branch-instructions
perf:cpu:branches
perf:cpu:branch-misses
perf:cpu:bus-cycles
perf:cpu:L1-dcache-loads
perf:cpu:L1-dcache-load-misses
perf:cpu:L1-dcache-stores
perf:cpu:L1-dcache-store-misses
perf:cpu:L1-dcache-prefetches
perf:cpu:L1-dcache-prefetch-misses
perf:cpu:L1-icache-loads
perf:cpu:L1-icache-load-misses
perf:cpu:L1-icache-stores
perf:cpu:L1-icache-store-misses
perf:cpu:L1-icache-prefetches
perf:cpu:L1-icache-prefetch-misses
perf:cpu:LLC-loads
perf:cpu:LLC-load-misses
perf:cpu:LLC-stores
perf:cpu:LLC-store-misses
perf:cpu:LLC-prefetches
perf:cpu:LLC-prefetch-misses
perf:cpu:dTLB-loads
perf:cpu:dTLB-load-misses
perf:cpu:dTLB-stores
perf:cpu:dTLB-store-misses
perf:cpu:dTLB-prefetches
perf:cpu:dTLB-prefetch-misses
perf:cpu:iTLB-loads
perf:cpu:iTLB-load-misses
perf:cpu:branch-loads
perf:cpu:branch-load-misses
perf:cpu:cpu-clock
perf:cpu:task-clock
perf:cpu:page-fault
perf:cpu:faults
perf:cpu:major-faults
perf:cpu:minor-faults
perf:cpu:context-switches
perf:cpu:cs
perf:cpu:cpu-migrations
perf:cpu:migrations
perf:cpu:alignment-faults
perf:cpu:emulation-faults
perf:thread:cpu-cycles
perf:thread:cycles
perf:thread:stalled-cycles-frontend
perf:thread:idle-cycles-frontend
perf:thread:stalled-cycles-backend
perf:thread:idle-cycles-backend
perf:thread:instructions
perf:thread:cache-references
perf:thread:cache-misses
perf:thread:branch-instructions
perf:thread:branches
perf:thread:branch-misses
perf:thread:bus-cycles
perf:thread:L1-dcache-loads
perf:thread:L1-dcache-load-misses
perf:thread:L1-dcache-stores
perf:thread:L1-dcache-store-misses
perf:thread:L1-dcache-prefetches
perf:thread:L1-dcache-prefetch-misses
perf:thread:L1-icache-loads
perf:thread:L1-icache-load-misses
perf:thread:L1-icache-stores
perf:thread:L1-icache-store-misses
perf:thread:L1-icache-prefetches
perf:thread:L1-icache-prefetch-misses
perf:thread:LLC-loads
perf:thread:LLC-load-misses
perf:thread:LLC-stores
perf:thread:LLC-store-misses
perf:thread:LLC-prefetches
perf:thread:LLC-prefetch-misses
perf:thread:dTLB-loads
perf:thread:dTLB-load-misses
perf:thread:dTLB-stores
perf:thread:dTLB-store-misses
perf:thread:dTLB-prefetches
perf:thread:dTLB-prefetch-misses
perf:thread:iTLB-loads
perf:thread:iTLB-load-misses
perf:thread:branch-loads
perf:thread:branch-load-misses
perf:thread:cpu-clock
perf:thread:task-clock
perf:thread:page-fault
perf:thread:faults
perf:thread:major-faults
perf:thread:minor-faults
perf:thread:context-switches
perf:thread:cs
perf:thread:cpu-migrations
perf:thread:migrations
perf:thread:alignment-faults
perf:thread:emulation-faults
Thanks,
Serica
------------------ ÔʼÓʼþ ------------------
·¢¼þÈË: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>;
·¢ËÍʱ¼ä: 2020Äê12ÔÂ29ÈÕ(ÐÇÆÚ¶þ) ÖÐÎç11:58
ÊÕ¼þÈË: "Serica"<serica_law@qq.com>;
³ËÍ: "lttng-dev"<lttng-dev@lists.lttng.org>;
Ö÷Ìâ: Re: [lttng-dev] Enamebling namespace contexts
----- On Dec 23, 2020, at 9:55 PM, lttng-dev <lttng-dev@lists.lttng.org> wrote:
Hi,
ThI found that lttng is working on container awareness in this slides: https://archive.fosdem.org/2019/schedule/event/containers_lttng/attachments/slides/3419/export/events/attachments/containers_lttng/slides/3419/lttng_containers_fosdem19.pdf
On page #13, there is a command: lttng add-context -k -t procname -t pid -t vpid -t tid -t vtid -t pid_ns, where pid_ns and other namespace identifiers are very useful for tracing containers. However, it seems like that lttng of current version doesn't support adding context pid_ns(Error: Unknown context type pid_ns). Do you know how to enable these features?
What version of LTTng do you use (output of "lttng --version"), and what is the output of "lttng add-context --list" ?
Thanks,
Mathieu
Thanks a lot.
Btw, have a nice holiday!
Serica
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
[-- Attachment #1.2: Type: text/html, Size: 7394 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-12-29 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 2:55 [lttng-dev] Enamebling namespace contexts Serica via lttng-dev
2020-12-29 3:58 ` Mathieu Desnoyers via lttng-dev
2020-12-29 13:18 ` Serica via lttng-dev [this message]
2021-01-04 15:36 ` [lttng-dev] 回复: " Jonathan Rajotte-Julien 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=tencent_4C429FE980FC54AC7AC796244B4048B19805@qq.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=serica_law@qq.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