On Wed, Sep 07, 2022 at 02:02:00PM +0200, Christoph Hellwig wrote: > On Wed, Sep 07, 2022 at 02:38:00PM +0300, Patrisious Haddad wrote: > > From: Israel Rukshin <israelr@xxxxxxxxxx> > > > > Add debug prints for fatal QP events that are helpful for finding the > > root cause of the errors. The ib_get_qp_err_syndrome is called at > > a work queue since the QP event callback is running on an > > interrupt context that can't sleep. > > What an awkward interface. What prevents us from allowing > ib_get_qp_err_syndrome to be called from arbitrary calling contexts, > or even better just delivering the error directly as part of the > event? We need to call to our FW through command interface and unfortunately it is not possible to do in atomic context. Thanks
