Roland Dreier b581401ed0 mlx4_core: Initialize ctx_list and ctx_lock earlier ... We may call mlx4_dispatch_event() before mlx4_register_device() is called for a device, because for example a catastrophic error happens immediately after we enable interrupts. Therefore priv->ctx_list and priv->ctx_lock need to be initialized earlier. This bug was actually exposed by the MSI-X bug that returned IRQ numbers to drivers in reverse order, so that the first FW command interrupt looked to mlx4 like a catastrophic error. Signed-off-by: Roland Dreier <rolandd@cisco.com>		2007-06-07 11:51:58 -07:00
..
alloc.c	IB/mlx4: Fix last allocated object tracking in bitmap allocator	2007-05-29 16:07:09 -07:00
catas.c
cmd.c
cq.c	mlx4_core: Fix CQ context layout	2007-06-07 11:51:57 -07:00
eq.c	missing includes in mlx4	2007-05-15 18:56:37 -07:00
fw.c	mlx4_core: Fix array overrun in dump_dev_cap_flags()	2007-05-19 08:51:57 -07:00
fw.h
icm.c	missing includes in mlx4	2007-05-15 18:56:37 -07:00
icm.h
intf.c	mlx4_core: Initialize ctx_list and ctx_lock earlier	2007-06-07 11:51:58 -07:00
main.c	mlx4_core: Initialize ctx_list and ctx_lock earlier	2007-06-07 11:51:58 -07:00
Makefile
mcg.c
mlx4.h	mlx4_core: Remove unused doorbell_lock	2007-05-13 08:54:18 -07:00
mr.c
pd.c
profile.c
qp.c
reset.c	missing includes in mlx4	2007-05-15 18:56:37 -07:00
srq.c