coresight: etm3x: Don't trace PID for non-root PID namespace

ETMv3 driver enables PID tracing by directly using perf config from
userspace, this means the tracer will capture PID packets from root
namespace but the profiling session runs in non-root PID namespace.
Finally, the recorded packets can mislead perf reporting with the
mismatched PID values.

This patch changes to only enable PID tracing for root PID namespace.
Note, the hardware supports VMID tracing from ETMv3.5, but the driver
never enables VMID trace, this patch doesn't handle VMID trace (bit 30
in ETMCR register) particularly.

Signed-off-by: Leo Yan <leo.yan@linaro.org>
Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Link: https://lore.kernel.org/r/20220204152403.71775-5-leo.yan@linaro.org

diff --git a/drivers/hwtracing/coresight/coresight-etm3x-core.c b/drivers/hwtracing/coresight/coresight-etm3x-core.c
index cf64ce73a7412136a358ade02ab0cc7bacaddbf9..7d413ba8b823c9a22d38331afb9c803d8cc214bf 100644 (file)
--- a/drivers/hwtracing/coresight/coresight-etm3x-core.c
+++ b/drivers/hwtracing/coresight/coresight-etm3x-core.c
@@ -340,6 +340,10 @@ static int etm_parse_event_config(struct etm_drvdata *drvdata,
 
        config->ctrl = attr->config;
 
+       /* Don't trace contextID when runs in non-root PID namespace */
+       if (!task_is_in_init_pid_ns(current))
+               config->ctrl &= ~ETMCR_CTXID_SIZE;
+
        /*
         * Possible to have cores with PTM (supports ret stack) and ETM
         * (never has ret stack) on the same SoC. So if we have a request