[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1828884A29C6694DAF28B7E6B8A82373992F4867@ORSMSX109.amr.corp.intel.com>
Date: Wed, 23 Apr 2014 21:34:55 +0000
From: "Hefty, Sean" <sean.hefty@...el.com>
To: Carol Soto <clsoto@...ux.vnet.ibm.com>,
"roland@...nel.org" <roland@...nel.org>,
"hal.rosenstock@...il.com" <hal.rosenstock@...il.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "brking@...ux.vnet.ibm.com" <brking@...ux.vnet.ibm.com>
Subject: RE: [Patch 3/3] IB/ib_cm: hang in cm_destroy_id during PCI error
injection
> > This is a device level event, not a port event. The port_num value may
> not be valid.
> The first patch of the series(IB/mlx4: send a IB_EVENT_DEVICE_FATAL to
> users during PCI error injection), when mlx4 send the IB_EVENT_DEVICE_FATAL
> event I am passing the port number to that field so in that way I was
> able to make it work. Any other suggestions are welcome.
This would need to be done for all devices.
Converting this to a per port event requires multiple events per device, which would impact the user space ABI. I think the patch itself needs to change to remove the per port association and operate at the device level, since it is really a device event.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists