Hi all,
For sched_switch tracepoint, I guess maybe it would be more reasonable
to show guest samples together with host samples by default, instead of
setting an option to display guest samples when we meet with this
confused situation.
To take care of this issue, the code should be changed
Hi all,
For sched_switch tracepoint, I guess maybe it would be more reasonable
to show guest samples together with host samples by default, instead of
setting an option to display guest samples when we meet with this
confused situation.
To take care of this issue, the code should be changed
On 10/18/17 1:09 AM, Mengting Zhang wrote:
> @@ -2771,6 +2772,8 @@ int cmd_script(int argc, const char **argv)
> "Show context switch events (if recorded)"),
> OPT_BOOLEAN('\0', "show-namespace-events",
> _namespace_events,
> "Show namespace events (if
On 10/18/17 1:09 AM, Mengting Zhang wrote:
> @@ -2771,6 +2772,8 @@ int cmd_script(int argc, const char **argv)
> "Show context switch events (if recorded)"),
> OPT_BOOLEAN('\0', "show-namespace-events",
> _namespace_events,
> "Show namespace events (if
By default, 'perf script' always exclude guest samples in host.
However, for some tracepoint events(e.g. sched_switch), the tracing
output lost sched_out samples for vcpu thread if 'perf script'
filter guest samples, which is confusing. Therefore, it'd be better
to display guest samples together
By default, 'perf script' always exclude guest samples in host.
However, for some tracepoint events(e.g. sched_switch), the tracing
output lost sched_out samples for vcpu thread if 'perf script'
filter guest samples, which is confusing. Therefore, it'd be better
to display guest samples together
6 matches
Mail list logo
