From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] [RELEASE] LTTng-Tools 2.4.0-rc1 - Époque Opaque
Date: Fri, 15 Nov 2013 20:22:34 +0000 [thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD267A2503@VAL-E-01.valcartier.drdc-rddc.gc.ca> (raw)
-----Message d'origine-----
Date: Fri, 15 Nov 2013 12:27:01 -0500
From: David Goulet <dgoulet@efficios.com>
> 1) Live support. It's now possible to stream traces (kernel and UST)
> while they being extracted meaning a relayd can now receive traces live
> and a viewer can attach to it to process the trace while running. The
> "--live" has been added to lttng create command that sets up a live
> tracing session.
>
> See doc/live-reading-howto.txt and doc/live-reading-protocol.txt for
> more detail on that feature.
Does this mean you can't do a "live" trace to local storage?
> 2) Java Util Logging support. With a special LTTngAgent located in
> lttng-ust project (liblttng-ust-jul) to trace JUL events and gather UST
> traces with them.
>
> The -j/--jul domain has been added to lttng command line so you can list
> the possible JUL Logger object and enable/disable them. It is the same
> as using the UST or Kernel domain.
>
> As of now, filters and loglevel are ignored with the JUL domain.
Saying "It is the same as using the UST or Kernel domain" leaves a lot of questions unanswered, since the kernel and user-space behave *very* differently on a lot of points.
1) Does --jul require root privileges?
2) I suppose the various commands have --kernel pre-empting --userspace pre-empting --ul?
3) add-context: does --jul have the same possible context types as --userspace (i.e. ip, pthread_id, procname, vpid, vtid)?
4) enable-channel:
4.1) Are the --jul --subbuf-size, --num-subbuf and --read-timer defaults the same as with --userspace?
4.2) Presumably --output can only be mmap?
4.3) Are the --jul buffering schemes the same as with --userspace (i.e. --buffers-pid and --buffers-uid)?
4.4) If yes, won't they all degenerate to the virtual machine's user and process IDs?
5) enable-event:
5.1) Can you assign --jul events to multiple channels like you can in --userspace?
5.2) Is the --jul event type --tracepoint or something else entirely?
5.3) Can the trailing wild card (and exclusion option) be used in the event name when enabling/disabling --jul events?
6) list: Does bug #654 also apply to --jul?
Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada | Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>
next reply other threads:[~2013-11-15 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 20:22 Thibault, Daniel [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-15 17:27 David Goulet
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=48CF5AC71E61DB46B70D0F388054EFFD267A2503@VAL-E-01.valcartier.drdc-rddc.gc.ca \
--to=daniel.thibault@drdc-rddc.gc.ca \
/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