Mathieu Poirier <mathieu.poirier@xxxxxxxxxx> writes: > On 30 September 2015 at 03:58, Alexander Shishkin > <alexander.shishkin@xxxxxxxxxxxxxxx> wrote: >> Most of these things can also be bypassed, as at least initially perf >> events won't be using trigger/sequencer configurations, so we could >> simply clear all these things out when a first perf event is created >> (which would also disallow any sysfs poking around the etm/etb) and not >> worry about them in the pmu callbacks. > > I don't want to restrain configuration options to what is available > through Perf's cmd line. The sysFS interface is there to complement > what is currently not available. In practice this means that part of your trace configuration will be global and part -- per event, which can indeed work if you only have one event at a time, but again, makes using perf infrastructure redundant for this driver. For multiple events this doesn't make much sense. Regards, -- Alex -- 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
