----- Original Message -----
> From: "francis deslauriers" <[email protected]>
> To: [email protected], "francis deslauriers" 
> <[email protected]>
> Sent: Wednesday, June 18, 2014 10:19:40 PM
> Subject: [lttng-dev] [PATCH lttng-tools] Add vpid,    vppid and vtid 
> explanation in add-context help menu
> 
> From: Francis Deslauriers <[email protected]>
> 
> Signed-off-by: Francis Deslauriers <[email protected]>
> ---
>  src/bin/lttng/commands/add_context.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/src/bin/lttng/commands/add_context.c
> b/src/bin/lttng/commands/add_context.c
> index 405b782..52d0db4 100644
> --- a/src/bin/lttng/commands/add_context.c
> +++ b/src/bin/lttng/commands/add_context.c
> @@ -514,6 +514,9 @@ static void usage(FILE *ofp)
>       fprintf(ofp, "                           TYPE can be one of the strings
>       below:\n");
>       print_ctx_type(ofp);
>       fprintf(ofp, "\n");
> +     fprintf(ofp, "Note that the vpid, vppid and vtid context types represent
> the virtual process id,\n"
> +                     "virtual parent process id and virtual thread id as 
> seen from the current
> execution context\n"
> +                     "as oppose to the pid, ppid and tid that are kernel 
> internal data
> structures.\n\n");

oppose -> opposed

that are -> which are

Other than that,

Acked-by: Mathieu Desnoyers <[email protected]>


>       fprintf(ofp, "Example:\n");
>       fprintf(ofp, "This command will add the context information 'prio' and 
> two
>       per-cpu\n"
>                       "perf counters (hardware branch misses and cache 
> misses), to all
>                       channels\n"
> --
> 1.8.3.2
> 
> 
> _______________________________________________
> lttng-dev mailing list
> [email protected]
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> 

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Reply via email to