Searched hist:d46966013bb4f1fbed7cf995828523a3d1f265c6 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/afs/ |
| H A D | flock.c | diff d46966013bb4f1fbed7cf995828523a3d1f265c6 Thu Apr 25 08:26:50 CDT 2019 David Howells <dhowells@redhat.com> afs: Add file locking tracepoints
Add two tracepoints for monitoring AFS file locking. Firstly, add one that
follows the operational part:
echo 1 >/sys/kernel/debug/tracing/events/afs/afs_flock_op/enable
And add a second that more follows the event-driven part:
echo 1 >/sys/kernel/debug/tracing/events/afs/afs_flock_ev/enable
Individual file_lock structs seen by afs are tagged with debugging IDs that
are displayed in the trace log to make it easier to see what's going on,
especially as setting the first lock always seems to involve copying the
file_lock twice.
Signed-off-by: David Howells <dhowells@redhat.com>
|
| /openbmc/linux/include/trace/events/ |
| H A D | afs.h | diff d46966013bb4f1fbed7cf995828523a3d1f265c6 Thu Apr 25 08:26:50 CDT 2019 David Howells <dhowells@redhat.com> afs: Add file locking tracepoints
Add two tracepoints for monitoring AFS file locking. Firstly, add one that
follows the operational part:
echo 1 >/sys/kernel/debug/tracing/events/afs/afs_flock_op/enable
And add a second that more follows the event-driven part:
echo 1 >/sys/kernel/debug/tracing/events/afs/afs_flock_ev/enable
Individual file_lock structs seen by afs are tagged with debugging IDs that
are displayed in the trace log to make it easier to see what's going on,
especially as setting the first lock always seems to involve copying the
file_lock twice.
Signed-off-by: David Howells <dhowells@redhat.com>
|
| /openbmc/linux/include/linux/ |
| H A D | fs.h | diff d46966013bb4f1fbed7cf995828523a3d1f265c6 Thu Apr 25 08:26:50 CDT 2019 David Howells <dhowells@redhat.com> afs: Add file locking tracepoints
Add two tracepoints for monitoring AFS file locking. Firstly, add one that
follows the operational part:
echo 1 >/sys/kernel/debug/tracing/events/afs/afs_flock_op/enable
And add a second that more follows the event-driven part:
echo 1 >/sys/kernel/debug/tracing/events/afs/afs_flock_ev/enable
Individual file_lock structs seen by afs are tagged with debugging IDs that
are displayed in the trace log to make it easier to see what's going on,
especially as setting the first lock always seems to involve copying the
file_lock twice.
Signed-off-by: David Howells <dhowells@redhat.com>
|