]> asedeno.scripts.mit.edu Git - linux.git/commit
vfio-ccw: Refactor how the traces are built
authorEric Farman <farman@linux.ibm.com>
Wed, 16 Oct 2019 14:20:37 +0000 (16:20 +0200)
committerCornelia Huck <cohuck@redhat.com>
Thu, 17 Oct 2019 09:35:56 +0000 (11:35 +0200)
commit7af52cca6f1c4d785b652682a8f7687df1061318
tree0c93ecf860bd1c0174811e4ed316b3eeff4c21d0
parent89d0180a60fcc5368eb2d92faeb1e012f8a591b3
vfio-ccw: Refactor how the traces are built

Commit 3cd90214b70f ("vfio: ccw: add tracepoints for interesting error
paths") added a quick trace point to determine where a channel program
failed while being processed.  It's a great addition, but adding more
traces to vfio-ccw is more cumbersome than it needs to be.

Let's refactor how this is done, so that additional traces are easier
to add and can exist outside of the FSM if we ever desire.

Signed-off-by: Eric Farman <farman@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Message-Id: <20191016142040.14132-2-farman@linux.ibm.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
drivers/s390/cio/Makefile
drivers/s390/cio/vfio_ccw_cp.h
drivers/s390/cio/vfio_ccw_fsm.c
drivers/s390/cio/vfio_ccw_trace.c [new file with mode: 0644]
drivers/s390/cio/vfio_ccw_trace.h