From: Pengfei Li <[email protected]>
Hi Steven, Masami,
Gentle ping on this v4 series now that the 7.2 merge window has settled.
I'd especially value a quick steer on the two design questions from the
cover letter, since they shape how I respin:
1. Eager vs lazy allocation of the element pool (~8 MB at the default
bits=14 when CONFIG_FTRACE_STACKMAP=y, whether or not userspace ever
enables the option). Is eager allocation acceptable, or should v5
switch to lazy allocation on the first 'echo 1 > options/stackmap'?
2. Whether to introduce the stack_map_bin binary interface now, or ship
the text stack_map interface first and add the binary export once
trace-cmd / libtraceevent integration is designed.
Happy to respin in either direction. Full series for reference:
https://lore.kernel.org/all/[email protected]/
Thanks,
Pengfei
