On Sun, Oct 20, 2019 at 09:44:00AM +0300, Leon Romanovsky wrote: > From: Michael Guralnik <michaelgur@xxxxxxxxxxxx> > > Add a test in mlx5_ib initialization process to test whether > write-combining is supported on the machine. > The test will run as part of the enable_driver callback to ensure that > the test runs after the device is setup and can create and modify the > QP needed, but runs before the device is exposed to the users. > > The test opens UD QP and posts NOP WQEs, the WQE written to the BlueFlame > is different from the WQE in memory, requesting CQE only on the BlueFlame > WQE. By checking whether we received a completion on one of these WQEs we > can know if BlueFlame succeeded and whether write-combining is supported. > > Change reporting of BlueFlame support to be dependent on write-combining > support. > > Signed-off-by: Michael Guralnik <michaelgur@xxxxxxxxxxxx> > Signed-off-by: Leon Romanovsky <leonro@xxxxxxxxxxxx> > --- > drivers/infiniband/hw/mlx5/main.c | 15 +- > drivers/infiniband/hw/mlx5/mem.c | 200 +++++++++++++++++++++++++++ > drivers/infiniband/hw/mlx5/mlx5_ib.h | 6 + > drivers/infiniband/hw/mlx5/qp.c | 6 +- > 4 files changed, 224 insertions(+), 3 deletions(-) > We found statistical failure with this patch and I'll resend it. Thanks
