linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
To: Slavomir Kaslev <slavomir.kaslev@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v15 11/18] trace-cmd: Exchange tracing IDs between host and guest
Date: Fri, 29 Nov 2019 12:22:57 +0200	[thread overview]
Message-ID: <CAPpZLN5UETUxHTD_OuXp_mCC4PJRzK9Ox_sASLG1fcmuZkgf=g@mail.gmail.com> (raw)
In-Reply-To: <CAPpZLN4+uRCzUcjgH0nL_KKu39d5=EpEMUhLdVDRsmPEn4X-Lg@mail.gmail.com>

On Thu, Nov 28, 2019 at 4:58 PM Tzvetomir Stoyanov
<tz.stoyanov@gmail.com> wrote:
>
> On Thu, Nov 28, 2019 at 4:34 PM Slavomir Kaslev
> <slavomir.kaslev@gmail.com> wrote:
> >
>  ...
> > > -       ret = tracecmd_msg_recv_trace_req(msg_handle, &argc, &argv, &use_fifos);
> > > +       ret = tracecmd_msg_recv_trace_req(msg_handle, &argc, &argv,
> > > +                                         &use_fifos, &trace_id);
> >
> > Why is `tracecmd_msg_recv_trace_req` receiving trace_id if it's
> > getting generated by the agent below?
> >
> Each peer generates its own trace id and stores it in its trace.dat
> file. tracecmd_msg_recv_trace_req() receives the trace ID of the host
> and tracecmd_msg_send_trace_resp() replies its own trace ID.
> May be it is a good idea in case of guest to not generate trace ID,
> but to use the one generated by the host ?

Actually each peer in a tracing session must have its own, unique trace ID.
These IDs are used to distinguish guests (in case there is more than one) in
the host context. In the host's trace.dat file a TRACECMD_OPTION_GUEST
option is written for each guest, describing guest VCPU - host PID mapping
and guest's trace ID is used to identify guests.
The host's trace ID is sent to the guest using tracecmd_msg_recv_trace_req()
and indeed it is not used anywhere, but I prefer to keep this exchange
part of the
trace request / reply negotiation, it could be useful in the future.

>
> > >         if (ret < 0)
> > >                 die("Failed to receive trace request");
> > >
> > > @@ -153,13 +155,13 @@ static void agent_handle(int sd, int nr_cpus, int page_size)
> > >
> > >         if (!use_fifos)
> > >                 make_vsocks(nr_cpus, fds, ports);
> > > -
> > > +       trace_id = tracecmd_generate_traceid();
> > >         ret = tracecmd_msg_send_trace_resp(msg_handle, nr_cpus, page_size,
> > > -                                          ports, use_fifos);
> > > +                                          ports, use_fifos, trace_id);
> > >         if (ret < 0)
> > >                 die("Failed to send trace response");
> > > -
> > > -       trace_record_agent(msg_handle, nr_cpus, fds, argc, argv, use_fifos);
> > > +       trace_record_agent(msg_handle, nr_cpus, fds, argc, argv,
> > > +                          use_fifos, trace_id);
> > >
> > >         free(argv[0]);
> > >         free(argv);
> >
> > Cheers,
> >
> > -- Slavi
>
>
>
> --
> Tzvetomir (Ceco) Stoyanov
> VMware Open Source Technology Center



-- 
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center

  reply	other threads:[~2019-11-29 10:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  8:53 [PATCH v15 00/18]Timestamp synchronization of host - guest tracing session Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 01/18] trace-cmd: Implement new lib API: tracecmd_local_events_system() Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 02/18] trace-cmd: Add support for negative time offsets in trace.dat file Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 03/18] trace-cmd: Add implementations of htonll() and ntohll() Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 04/18] trace-cmd: Add new library APIs for ftrace instances Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 05/18] trace-cmd: Add new library API for local CPU count Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 06/18] trace-cmd: Add new library API for reading ftrace buffers Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 07/18] trace-cmd: Find and store pids of tasks, which run virtual CPUs of given VM Tzvetomir Stoyanov (VMware)
2019-11-28  8:53 ` [PATCH v15 08/18] trace-cmd: Implement new API tracecmd_add_option_v() Tzvetomir Stoyanov (VMware)
2019-11-28  8:54 ` [PATCH v15 09/18] trace-cmd: Add new API to generate a unique ID of the tracing session Tzvetomir Stoyanov (VMware)
2019-11-28  8:54 ` [PATCH v15 10/18] trace-cmd: Store the session tracing ID in the trace.dat file Tzvetomir Stoyanov (VMware)
2019-11-28  8:54 ` [PATCH v15 11/18] trace-cmd: Exchange tracing IDs between host and guest Tzvetomir Stoyanov (VMware)
2019-11-28 14:34   ` Slavomir Kaslev
2019-11-28 14:58     ` Tzvetomir Stoyanov
2019-11-29 10:22       ` Tzvetomir Stoyanov [this message]
2019-11-28  8:54 ` [PATCH v15 12/18] trace-cmd: Implement new option in trace.dat file: TRACECMD_OPTION_TIME_SHIFT Tzvetomir Stoyanov (VMware)
2019-11-28  8:54 ` [PATCH v15 13/18] trace-cmd: Add guest information in host's trace.dat file Tzvetomir Stoyanov (VMware)
2019-11-28  8:54 ` [PATCH v15 14/18] trace-cmd: Add host trace clock as guest trace argument Tzvetomir Stoyanov (VMware)
2019-11-28 14:45   ` Slavomir Kaslev
2019-11-28 15:05     ` Tzvetomir Stoyanov
2019-11-28  8:54 ` [PATCH v15 15/18] trace-cmd: Refactor few trace-cmd internal functions Tzvetomir Stoyanov (VMware)
2019-11-28 14:51   ` Slavomir Kaslev
2019-11-28 15:08     ` Tzvetomir Stoyanov
2019-11-28  8:54 ` [PATCH v15 16/18] trace-cmd: Basic infrastructure for host - guest timestamp synchronization Tzvetomir Stoyanov (VMware)
2019-11-28 15:08   ` Slavomir Kaslev
2019-11-28 15:27     ` Tzvetomir Stoyanov
2019-11-28  8:54 ` [PATCH v15 17/18] trace-cmd: [POC] PTP-like algorithm " Tzvetomir Stoyanov (VMware)
2019-11-28  8:54 ` [PATCH v15 18/18] trace-cmd: Debug scripts for " Tzvetomir Stoyanov (VMware)

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='CAPpZLN5UETUxHTD_OuXp_mCC4PJRzK9Ox_sASLG1fcmuZkgf=g@mail.gmail.com' \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=slavomir.kaslev@gmail.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;
as well as URLs for NNTP newsgroup(s).