linux-toradex.git/include/linux/mlx4, branch v4.12-rc4

treewide: spelling: correct diffrent[iate] and banlance typos

2017-05-09T00:15:13+00:00

Add these misspellings to scripts/spelling.txt too

Link: http://lkml.kernel.org/r/962aace119675e5fe87be2a88ddac1a5486f8e60.1490931810.git.joe@perches.com
Signed-off-by: Joe Perches 
Acked-by: Mauro Carvalho Chehab 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

IB/mlx4: Support RAW Ethernet when RoCE is disabled

2017-04-21T16:26:05+00:00

On some environments, such as certain SR-IOV VF configurations, RoCE
isn't supported for mlx4 Ethernet ports. Currently the driver will
not open IB device on that port.

This is problematic since we do want user-space RAW Ethernet QPs functionality
to remain in place. For that end, enhance the relevant driver flows such that we
do create a device instance in that case.

Signed-off-by: Majd Dibbiny 
Signed-off-by: Leon Romanovsky 
Signed-off-by: Doug Ledford

net/mlx4_core: Avoid delays during VF driver device shutdown

2017-03-17T03:14:51+00:00

Some Hypervisors detach VFs from VMs by instantly causing an FLR event
to be generated for a VF.

In the mlx4 case, this will cause that VF's comm channel to be disabled
before the VM has an opportunity to invoke the VF device's "shutdown"
method.

For such Hypervisors, there is a race condition between the VF's
shutdown method and its internal-error detection/reset thread.

The internal-error detection/reset thread (which runs every 5 seconds) also
detects a disabled comm channel. If the internal-error detection/reset
flow wins the race, we still get delays (while that flow tries repeatedly
to detect comm-channel recovery).

The cited commit fixed the command timeout problem when the
internal-error detection/reset flow loses the race.

This commit avoids the unneeded delays when the internal-error
detection/reset flow wins.

Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver device shutdown")
Signed-off-by: Jack Morgenstein 
Reported-by: Simon Xiao 
Signed-off-by: Tariq Toukan 
Signed-off-by: David S. Miller

net/mlx4: && vs & typo

2017-03-01T17:50:58+00:00

Bitwise & was obviously intended here.

Fixes: 745d8ae4622c ("net/mlx4: Spoofcheck and zero MAC can't coexist")
Signed-off-by: Dan Carpenter 
Reviewed-by: Tariq Toukan 
Signed-off-by: David S. Miller

net/mlx4: Spoofcheck and zero MAC can't coexist

2017-02-23T15:57:56+00:00

Spoofcheck can't be enabled if VF MAC is zero.
Vice versa, can't zero MAC if spoofcheck is on.

Fixes: 8f7ba3ca12f6 ('net/mlx4: Add set VF mac address support')
Signed-off-by: Eugenia Emantayev 
Signed-off-by: Tariq Toukan 
Signed-off-by: David S. Miller

net/mlx4_en: Pass user MTU value to Firmware at set port command

2017-01-30T20:26:43+00:00

When starting the port, driver will inform Firmware about the actual MTU
which does not include implicit headers, such as FCS or VLAN tags.

Signed-off-by: Shaker Daibes 
Signed-off-by: Tariq Toukan 
Signed-off-by: David S. Miller

net/mlx4_en: Adding support of turning off link autonegotiation via ethtool

2017-01-30T20:26:42+00:00

This feature will allow the user to disable auto negotiation
on the port for mlx4 devices while setting the speed is limited
to 1GbE speeds.
Other speeds will not be accepted in autoneg off mode.

This functionality is permitted providing that the firmware
is compatible with this feature.
The above is determined by querying a new dedicated capability
bit in the device.

Signed-off-by: Ariel Levkovich 
Signed-off-by: Tariq Toukan 
Signed-off-by: David S. Miller

net/mlx4_core: Fix raw qp flow steering rules under SRIOV

2016-12-29T19:17:40+00:00

Demoting simple flow steering rule priority (for DPDK) was achieved by
wrapping FW commands MLX4_QP_FLOW_STEERING_ATTACH/DETACH for the PF
as well, and forcing the priority to MLX4_DOMAIN_NIC in the wrapper
function for the PF and all VFs.

In function mlx4_ib_create_flow(), this change caused the main rule
creation for the PF to be wrapped, while it left the associated
tunnel steering rule creation unwrapped for the PF.

This mismatch caused rule deletion failures in mlx4_ib_destroy_flow()
for the PF when the detach wrapper function did not find the associated
tunnel-steering rule (since creation of that rule for the PF did not
go through the wrapper function).

Fix this by setting MLX4_QP_FLOW_STEERING_ATTACH/DETACH to be "native"
(so that the PF invocation does not go through the wrapper), and perform
the required priority demotion for the PF in the mlx4_ib_create_flow()
code path.

Fixes: 48564135cba8 ("net/mlx4_core: Demote simple multicast and broadcast flow steering rules")
Signed-off-by: Jack Morgenstein 
Signed-off-by: Tariq Toukan 
Signed-off-by: David S. Miller

clocksource: Use a plain u64 instead of cycle_t

2016-12-25T10:04:12+00:00

There is no point in having an extra type for extra confusion. u64 is
unambiguous.

Conversion was done with the following coccinelle script:

@rem@
@@
-typedef u64 cycle_t;

@fix@
typedef cycle_t;
@@
-cycle_t
+u64

Signed-off-by: Thomas Gleixner 
Cc: Peter Zijlstra 
Cc: John Stultz

Revert "net/mlx4_en: Avoid unregister_netdev at shutdown flow"

2016-11-28T20:33:46+00:00

This reverts commit 9d76931180557270796f9631e2c79b9c7bb3c9fb.

Using unregister_netdev at shutdown flow prevents calling
the netdev's ndos or trying to access its freed resources.

This fixes crashes like the following:
 Call Trace:
  [] dev_get_phys_port_id+0x1e/0x30
  [] rtnl_fill_ifinfo+0x4be/0xff0
  [] rtmsg_ifinfo_build_skb+0x73/0xe0
  [] rtmsg_ifinfo.part.27+0x16/0x50
  [] rtmsg_ifinfo+0x18/0x20
  [] netdev_state_change+0x46/0x50
  [] linkwatch_do_dev+0x38/0x50
  [] __linkwatch_run_queue+0xf5/0x170
  [] linkwatch_event+0x25/0x30
  [] process_one_work+0x152/0x400
  [] worker_thread+0x125/0x4b0
  [] ? rescuer_thread+0x350/0x350
  [] kthread+0xca/0xe0
  [] ? kthread_park+0x60/0x60
  [] ret_from_fork+0x25/0x30

Fixes: 9d7693118055 ("net/mlx4_en: Avoid unregister_netdev at shutdown flow")
Signed-off-by: Tariq Toukan 
Reported-by: Sebastian Ott 
Reported-by: Steve Wise 
Cc: Jiri Pirko 
Signed-off-by: David S. Miller