diff options
| author | Eric Farman <farman@linux.ibm.com> | 2019-10-16 17:20:38 +0300 |
|---|---|---|
| committer | Cornelia Huck <cohuck@redhat.com> | 2019-10-17 12:36:29 +0300 |
| commit | 970ebeb84880906b396e53539b95fdbbf3e786a2 (patch) | |
| tree | 6e87139dca24afefff99ed75563c0c0cc382c4c8 /drivers/s390/cio/vfio_ccw_trace.c | |
| parent | 7af52cca6f1c4d785b652682a8f7687df1061318 (diff) | |
| download | linux-970ebeb84880906b396e53539b95fdbbf3e786a2.tar.xz | |
vfio-ccw: Trace the FSM jumptable
It would be nice if we could track the sequence of events within
vfio-ccw, based on the state of the device/FSM and our calling
sequence within it. So let's add a simple trace here so we can
watch the states change as things go, and allow it to be folded
into the rest of the other cio traces.
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Message-Id: <20191016142040.14132-3-farman@linux.ibm.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'drivers/s390/cio/vfio_ccw_trace.c')
| -rw-r--r-- | drivers/s390/cio/vfio_ccw_trace.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/s390/cio/vfio_ccw_trace.c b/drivers/s390/cio/vfio_ccw_trace.c index d5cc943c6864..b37bc68e7f18 100644 --- a/drivers/s390/cio/vfio_ccw_trace.c +++ b/drivers/s390/cio/vfio_ccw_trace.c @@ -9,4 +9,5 @@ #define CREATE_TRACE_POINTS #include "vfio_ccw_trace.h" +EXPORT_TRACEPOINT_SYMBOL(vfio_ccw_fsm_event); EXPORT_TRACEPOINT_SYMBOL(vfio_ccw_io_fctl); |