For some STM hardware (e.g. ARM CoreSight STM), the masterID associated to a source is set at the hardware level and not user configurable. Since the masterID information isn't available to SW, introducing a new value of -1 to reflect this reality. Signed-off-by: Chunyan Zhang <zhang.chunyan@xxxxxxxxxx> --- Documentation/trace/stm.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/trace/stm.txt b/Documentation/trace/stm.txt index ea035f9..f03bc2b 100644 --- a/Documentation/trace/stm.txt +++ b/Documentation/trace/stm.txt @@ -47,6 +47,12 @@ through 127 in it. Now, any producer (trace source) identifying itself with "user" identification string will be allocated a master and channel from within these ranges. +$ cat /config/stp-policy/dummy_stm.my-policy/user/masters +-1 -1 + +Would indicate the masters for this rule are set in hardware and +not configurable in user space. + These rules can be nested, for example, one can define a rule "dummy" under "user" directory from the example above and this new rule will be used for trace sources with the id string of "user/dummy". -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
