On Thu, 28 Feb 2019 10:59:13 -0500
"Jason J. Herne" wrote:
> On 2/4/19 6:41 AM, Cornelia Huck wrote:
> >> @@ -148,6 +370,9 @@ int do_cio(SubChannelId schid, uint32_t ccw_addr, int
> >> fmt)
> >> continue;
> >> }
> >>
> >> +print_irb_err(&irb);
> >> +ba
On 2/4/19 6:41 AM, Cornelia Huck wrote:
...
+static void print_irb_err(Irb *irb)
+{
+Ccw0 *this_ccw = u32toptr(irb->scsw.cpa);
+Ccw0 *prev_ccw = u32toptr(irb->scsw.cpa - 8);
I don't think you can cast this conditionally to format 0 -- I'd pass
in the format from do_cio and handle it a
On Tue, 29 Jan 2019 08:29:18 -0500
"Jason J. Herne" 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:
>
> vf
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 C
On Wed, 12 Dec 2018 09:11:14 -0500
"Jason J. Herne" 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:
>
> vf
On 12/12/2018 09:11 AM, Jason J. Herne 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 er
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 C
