summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorEric Farman <farman@linux.ibm.com>2022-07-07 16:57:29 +0300
committerAlex Williamson <alex.williamson@redhat.com>2022-07-07 23:06:12 +0300
commitcffcc109fd682075dee79bade3d60a07152a8fd1 (patch)
tree362d5ce3e81909926554acff20d9fbb4a2de9ec1 /tools/perf/scripts/python
parentf6c876d67e956de8d69349b0ee43bc7277c09e5c (diff)
downloadlinux-cffcc109fd682075dee79bade3d60a07152a8fd1.tar.xz
vfio/ccw: Do not change FSM state in subchannel event
The routine vfio_ccw_sch_event() is tasked with handling subchannel events, specifically machine checks, on behalf of vfio-ccw. It correctly calls cio_update_schib(), and if that fails (meaning the subchannel is gone) it makes an FSM event call to mark the subchannel Not Operational. If that worked, however, then it decides that if the FSM state was already Not Operational (implying the subchannel just came back), then it should simply change the FSM to partially- or fully-open. Remove this trickery, since a subchannel returning will require more probing than simply "oh all is well again" to ensure it works correctly. Fixes: bbe37e4cb8970 ("vfio: ccw: introduce a finite state machine") Signed-off-by: Eric Farman <farman@linux.ibm.com> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com> Link: https://lore.kernel.org/r/20220707135737.720765-4-farman@linux.ibm.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions