From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: "Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: [PATCH v3 00/11] trace-cmd: Allow agent to use networking
Date: Wed, 20 Apr 2022 11:26:26 -0400 [thread overview]
Message-ID: <20220420152637.13105-1-rostedt@goodmis.org> (raw)
From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
There's no reason for trace-cmd agent not to be able to do the communication
over TCP instead of vsockets. Have trace-cmd record pass in a host name or
IP address (IPv4 or IPv6) to the -A option and if the cid or guest name
fails, then try host name or IP address.
This will fall back to the P2P time sync protocol and recordings from
different hosts can be synchronized.
Also add more debug prints when the --debug option is used. This proved
useful to debugging this code.
Changes since v2: https://lore.kernel.org/all/20220417184538.1044417-1-rostedt@goodmis.org/
- Added comments about USE_UDP as being the default, as well as
explicitly setting it to zero. (Tzvetomir Stoyanov)
- Appended https://lore.kernel.org/all/20220417211315.1049221-1-rostedt@goodmis.org/
to the patch set.
- Added more warnings about the insecurities of using trace-cmd agent
with the -N option. (Tzvetomir Stoyanov)
Changes since v1: https://lore.kernel.org/r/20220417011958.1013591-1-rostedt@goodmis.org
- Rebased on the above dependency.
- Added patch to allow compiling of agent without vsocket support.
Steven Rostedt (Google) (11):
trace-cmd record: Move port_type into instance
trace-cmd library: Add network roles for time sync
trace-cmd record: Allow for ip connections to agents
trace-cmd agent: Allow for ip connections from the agent
trace-cmd library: Create tracecmd_debug() for debug printing
trace-cmd: Add debug prints for network connections
trace-cmd: Add print helpers to show connections
trace-cmd: Override tracecmd_debug() to show thread id
trace-cmd agent: Have agent work without vsockets available
trace-cmd agent: Have -N take a host name
trace-cmd agent: Add documentation
Documentation/trace-cmd/trace-cmd-agent.1.txt | 62 ++++
lib/trace-cmd/Makefile | 2 +-
.../include/private/trace-cmd-private.h | 5 +
lib/trace-cmd/include/trace-tsync-local.h | 6 +-
lib/trace-cmd/trace-msg.c | 12 +-
lib/trace-cmd/trace-timesync-ptp.c | 4 +-
lib/trace-cmd/trace-timesync.c | 2 +
lib/trace-cmd/trace-util.c | 12 +
tracecmd/Makefile | 5 +-
tracecmd/include/trace-local.h | 25 +-
tracecmd/trace-agent.c | 126 ++++++--
tracecmd/trace-cmd.c | 20 +-
tracecmd/trace-listen.c | 139 +++++++--
tracecmd/trace-record.c | 269 ++++++++++++------
tracecmd/trace-usage.c | 5 +-
tracecmd/trace-vsock.c | 20 ++
16 files changed, 562 insertions(+), 152 deletions(-)
create mode 100644 Documentation/trace-cmd/trace-cmd-agent.1.txt
--
2.35.1
next reply other threads:[~2022-04-20 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 15:26 Steven Rostedt [this message]
2022-04-20 15:26 ` [PATCH v3 01/11] trace-cmd record: Move port_type into instance Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 02/11] trace-cmd library: Add network roles for time sync Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 03/11] trace-cmd record: Allow for ip connections to agents Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 04/11] trace-cmd agent: Allow for ip connections from the agent Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 05/11] trace-cmd library: Create tracecmd_debug() for debug printing Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 06/11] trace-cmd: Add debug prints for network connections Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 07/11] trace-cmd: Add print helpers to show connections Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 08/11] trace-cmd: Override tracecmd_debug() to show thread id Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 09/11] trace-cmd agent: Have agent work without vsockets available Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 10/11] trace-cmd agent: Have -N take a host name Steven Rostedt
2022-04-20 15:26 ` [PATCH v3 11/11] trace-cmd agent: Add documentation Steven Rostedt
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=20220420152637.13105-1-rostedt@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
/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).