From: "Steven Rostedt (Google)" <rostedt@xxxxxxxxxxx> We have a use case where the host is very minimal (like an embedded device) and does not even have networking enabled. But it does have vsockets. We need to trace this host and have it send its data to the guest. By running trace-cmd listen on the guest and have the host use vsockets instead of networking, can allow this host to be traced. Depends on: https://patchwork.kernel.org/project/linux-trace-devel/list/?series=632868 https://lore.kernel.org/r/20220417182154.1041513-1-rostedt@xxxxxxxxxxx Changes since v2: https://lore.kernel.org/all/20220415011023.938663-1-rostedt@xxxxxxxxxxx/ - Fixed freeing of host variable that was not allocated Changes since v1: https://lore.kernel.org/all/20220412042739.836516-1-rostedt@xxxxxxxxxxx/ - Rebased on top of: https://lore.kernel.org/all/20220415010007.938408-1-rostedt@xxxxxxxxxxx/ - Added the documentation patch Steven Rostedt (Google) (5): trace-cmd listen: Remove UDP from function names trace-cmd listen: Replace bool use_tcp with enum type trace-cmd record: Replace bool use_tcp with enum type trace-cmd listen: Add vsocket usage trace-cmd listen: Add documentation on vsocket usage .../trace-cmd/trace-cmd-listen.1.txt | 4 + .../trace-cmd/trace-cmd-record.1.txt | 8 + .../include/private/trace-cmd-private.h | 1 + lib/trace-cmd/trace-msg.c | 15 +- tracecmd/include/trace-local.h | 8 + tracecmd/trace-listen.c | 196 +++++++++++++----- tracecmd/trace-record.c | 93 +++++++-- tracecmd/trace-usage.c | 2 + 8 files changed, 256 insertions(+), 71 deletions(-) -- 2.35.1
|