Christof Schmitt 339f4f4eab [SCSI] zfcp: Trigger logging in the FCP channel on qdio error conditions ... Exploit the cio siosl function to trigger logging in the FCP channel on qdio error conditions. Add a helper function in zfcp_qdio to ensure that tracing is only triggered once before calling qdio_shutdown. Trigger in zfcp for hardware logs are: - timeout for FSF requests to the FCP channel - "no recommendation" status from FCP channel - invalid FSF protocol status - stalled outbound queue - unknown request id on inbound queue - QDIO_ERROR_SLSB_STATE All of the above triggers run from the Linux qdio softirq context, so no additional synchronization is necessary for the handling of the ZFCP_STATUS_ADAPTER_SIOSL_ISSUED flag. Reviewed-by: Swen Schillig <swen@vnet.ibm.com> Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>		2010-07-28 09:48:58 -05:00
..
block	[S390] dasd: unit check handling during internal cio I/O	2010-05-26 23:27:09 +02:00
char	Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial	2010-05-20 09:20:59 -07:00
cio	[SCSI] zfcp: Enable data division support for FCP devices	2010-07-28 09:48:55 -05:00
crypto	[S390] avoid default_llseek in s390 drivers	2010-05-17 10:00:16 +02:00
kvm	include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h	2010-03-30 22:02:32 +09:00
net	Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6	2010-05-20 21:04:44 -07:00
scsi	[SCSI] zfcp: Trigger logging in the FCP channel on qdio error conditions	2010-07-28 09:48:58 -05:00
Makefile	[S390] split/move machine check handler code	2009-03-26 15:24:10 +01:00