From: "Steven Rostedt (Google)" <rostedt@xxxxxxxxxxx> 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. Steven Rostedt (Google) (8): 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 .../include/private/trace-cmd-private.h | 5 + 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/include/trace-local.h | 16 ++ tracecmd/trace-agent.c | 106 +++++-- tracecmd/trace-cmd.c | 18 ++ tracecmd/trace-listen.c | 84 ++++-- tracecmd/trace-record.c | 258 ++++++++++++------ tracecmd/trace-vsock.c | 20 ++ 11 files changed, 403 insertions(+), 134 deletions(-) -- 2.35.1
|