7df01d96b2
Oprofile counters are setup when profiling is disabled. Thus, writing to oprofilefs has no immediate effect. Changes are updated only after oprofile is reenabled. To keep userland and kernel states synchronized, we now allow configuration of oprofile only if profiling is disabled. In this case it checks if the profiler is running and then disables write access to oprofilefs by returning -EBUSY. The change should be backward compatible with current oprofile userland daemon. Acked-by: Maynard Johnson <maynardj@us.ibm.com> Cc: William Cohen <wcohen@redhat.com> Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> Signed-off-by: Robert Richter <robert.richter@amd.com> |
||
|---|---|---|
| .. | ||
| buffer_sync.c | ||
| buffer_sync.h | ||
| cpu_buffer.c | ||
| cpu_buffer.h | ||
| event_buffer.c | ||
| event_buffer.h | ||
| oprof.c | ||
| oprof.h | ||
| oprofile_files.c | ||
| oprofile_perf.c | ||
| oprofile_stats.c | ||
| oprofile_stats.h | ||
| oprofilefs.c | ||
| timer_int.c | ||