On Wed, 12 Dec 2018 09:11:14 -0500 "Jason J. Herne" <jjhe...@linux.ibm.com> wrote:
> Add verbose error output for when unexpected i/o errors happen. This eases the > burden of debugging and reporting i/o errors. No error information is printed > in the success case, here is an example of what is output on error: > > vfio-ccw device I/O error - Interrupt Response Block Data: > Function Ctrl : [Start] > Activity Ctrl : [Start-Pending] > Status Ctrl : [Alert] [Primary] [Secondary] [Status-Pending] > Device Status : [Unit-Check] > Channel Status : > cpa=: 0x0000000001e67098 > prev_ccw=: 0x0000000000000000 > this_ccw=: 0x0000000000000000 > > Sense Data (fmt 32-bytes): > Sense Condition Flags : [Equipment-Check] > Residual Count =: 0x0000000000000000 > Phys Drive ID =: 0x000000000000009e > low cyl address =: 0x0000000000000000 > head addr & hi cyl =: 0x0000000000000000 > format/message =: 0x0000000000000008 > fmt-dependent[0-7] =: 0x0000000000000004 > fmt-dependent[8-15]=: 0xe561282305082fff > prog action code =: 0x0000000000000016 > Configuration info =: 0x00000000000040e0 > mcode / hi-cyl =: 0x0000000000000000 > cyl & head addr [0]=: 0x0000000000000000 > cyl & head addr [1]=: 0x0000000000000000 > cyl & head addr [2]=: 0x0000000000000000 Even though we currently only support eckd dasd passed through via vfio-ccw, it is probably not a good idea to hardcode this? > > Signed-off-by: Jason J. Herne <jjhe...@linux.ibm.com> > --- > pc-bios/s390-ccw/cio.c | 225 > ++++++++++++++++++++++++++++++++++++++++++++++++ > pc-bios/s390-ccw/libc.h | 11 +++ > 2 files changed, 236 insertions(+)
