linux-toradex.git/drivers/infiniband/core/mad.c, branch v4.0

IB/mad: Add user space RMPP support

2014-08-11T03:36:00+00:00

Using the new registration mechanism, define a flag that indicates the
user wishes to process RMPP messages in user space rather than have
the kernel process them.

Signed-off-by: Ira Weiny 
Signed-off-by: Roland Dreier

IB/mad: add new ioctl to ABI to support new registration options

2014-08-11T03:36:00+00:00

Registrations options are specified through flags.  Definitions of flags will
be in subsequent patches.

Signed-off-by: Ira Weiny 
Signed-off-by: Roland Dreier

IB/mad: Add dev_notice messages for various umad/mad registration failures

2014-08-11T03:36:00+00:00

Registration failures can be difficult to debug from userspace.  This
gives more visibility.

Signed-off-by: Ira Weiny 
Signed-off-by: Roland Dreier

IB/mad: Update module to [pr|dev]_* style print messages

2014-08-11T03:35:39+00:00

Use dev_* style print when struct device is available.

Also combine previously line broken user-visible strings as per
Documentation/CodingStyle:

"However, never break user-visible strings such as printk messages,
because that breaks the ability to grep for them."

Signed-off-by: Ira Weiny 

[ Remove PFX so the patch actually builds.  - Roland ]

Signed-off-by: Roland Dreier

IB/mad: Check and handle potential DMA mapping errors

2014-04-01T17:36:07+00:00

Running with DMA_API_DEBUG enabled and not checking for DMA mapping
errors triggers a kernel stack trace with "DMA-API: device driver
failed to check map error" message.  Add these checks to the MAD
module, both to be be more robust and also eliminate these
false-positive stack traces.

Signed-off-by: Yan Burman 
Signed-off-by: Or Gerlitz 
Signed-off-by: Roland Dreier

IB/core: Create QP1 using the pkey index which contains the default pkey

2013-07-31T21:15:17+00:00

Currently, QP1 is created using pkey index 0. This patch simply looks
for the index containing the default pkey, rather than hard-coding
pkey index 0.

This change will have no effect in native mode, since QP0 and QP1 are
created before the SM configures the port, so pkey table will still be
the default table defined by the IB Spec, in C10-123: "If non-volatile
storage is not used to hold P_Key Table contents, then if a PM
(Partition Manager) is not present, and prior to PM initialization of
the P_Key Table, the P_Key Table must act as if it contains a single
valid entry, at P_Key_ix = 0, containing the default partition
key. All other entries in the P_Key Table must be invalid."

Thus, in the native mode case, the driver will find the default pkey
at index 0 (so it will be no different than the hard-coding).

However, in SR-IOV mode, for VFs, the pkey table may be
paravirtualized, so that the VF's pkey index zero may not necessarily
be mapped to the real pkey index 0. For VFs, therefore, it is
important to find the virtual index which maps to the real default
pkey.

This commit does the following for QP1 creation:

1. Find the pkey index containing the default pkey, and use that index
   if found.  ib_find_pkey() returns the index of the
   limited-membership default pkey (0x7FFF) if the full-member default
   pkey is not in the table.

2. If neither form of the default pkey is found, use pkey index 0
   (previous behavior).

Signed-off-by: Jack Morgenstein 
Signed-off-by: Or Gerlitz 
Reviewed-by: Sean Hefty 
Signed-off-by: Roland Dreier

workqueue: deprecate __cancel_delayed_work()

2012-08-21T20:18:24+00:00

Now that cancel_delayed_work() can be safely called from IRQ handlers,
there's no reason to use __cancel_delayed_work().  Use
cancel_delayed_work() instead of __cancel_delayed_work() and mark the
latter deprecated.

Signed-off-by: Tejun Heo 
Acked-by: Jens Axboe 
Cc: Jiri Kosina 
Cc: Roland Dreier 
Cc: Tomi Valkeinen

workqueue: use mod_delayed_work() instead of __cancel + queue

2012-08-21T20:18:24+00:00

Now that mod_delayed_work() is safe to call from IRQ handlers,
__cancel_delayed_work() followed by queue_delayed_work() can be
replaced with mod_delayed_work().

Most conversions are straight-forward except for the following.

* net/core/link_watch.c: linkwatch_schedule_work() was doing a quite
  elaborate dancing around its delayed_work.  Collapse it such that
  linkwatch_work is queued for immediate execution if LW_URGENT and
  existing timer is kept otherwise.

Signed-off-by: Tejun Heo 
Cc: "David S. Miller" 
Cc: Tomi Valkeinen

IB/mad: Don't send response for failed MADs

2012-04-24T23:08:57+00:00

Commit 0b307043049f ("IB/mad: Return error response for unsupported
MADs") does not failed MADs (eg those that return
IB_MAD_RESULT_FAILURE) properly -- these MADs should be silently
discarded. (We should not force the lower-layer drivers to return
SUCCESS | CONSUMED in this case, since the MAD is NOT successful).
Unsupported MADs are not failures -- they return SUCCESS, but with an
"unsupported error" status value inside the response MAD.

Reviewed-by: Hal Rosenstock 
Signed-off-by: Jack Morgenstein 
Signed-off-by: Roland Dreier

IB/mad: Set 'D' bit in response for unhandled MADs

2012-04-24T23:06:50+00:00

Commit 0b307043049f ("IB/mad: Return error response for unsupported
MADs") does not handle directed-route MADs properly -- it fails to set
the 'D' bit in the response MAD status field.  This is a problem for
SmInfo MADs when the receiver does not have an SM running.

Reviewed-by: Hal Rosenstock 
Signed-off-by: Jack Morgenstein 
Signed-off-by: Roland Dreier