diff options
author | Eric Farman <farman@linux.ibm.com> | 2019-10-16 16:20:38 +0200 |
---|---|---|
committer | Cornelia Huck <cohuck@redhat.com> | 2019-10-17 11:36:29 +0200 |
commit | 970ebeb84880906b396e53539b95fdbbf3e786a2 (patch) | |
tree | 6e87139dca24afefff99ed75563c0c0cc382c4c8 /usr/initramfs_data.S | |
parent | vfio-ccw: Refactor how the traces are built (diff) | |
download | linux-dev-970ebeb84880906b396e53539b95fdbbf3e786a2.tar.xz linux-dev-970ebeb84880906b396e53539b95fdbbf3e786a2.zip |
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 'usr/initramfs_data.S')
0 files changed, 0 insertions, 0 deletions