1. 27 10月, 2017 1 次提交
  2. 19 10月, 2017 3 次提交
  3. 18 10月, 2017 1 次提交
  4. 01 10月, 2017 1 次提交
  5. 18 8月, 2017 1 次提交
  6. 10 8月, 2017 3 次提交
  7. 08 8月, 2017 1 次提交
  8. 04 8月, 2017 4 次提交
  9. 03 8月, 2017 1 次提交
  10. 25 7月, 2017 1 次提交
    • J
      ibmvnic: Check for transport event on driver resume · a248878d
      John Allen 提交于
      On resume, the ibmvnic driver will fail to resume normal operation.
      The main crq gets closed on suspend by the vnic server and doesn't get
      reopened again as the interrupt for the transport event that would reset
      the main crq comes in after the driver has been suspended.
      
      This patch resolves the issue by removing the calls to kick the receive
      interrupts handlers and instead directly invoking the main crq interrupt
      handler. This will ensure that we see the transport event necessary to
      properly resume the driver.
      Signed-off-by: NJohn Allen <jallen@linux.vnet.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a248878d
  11. 30 6月, 2017 1 次提交
    • T
      ibmvnic: Fix assignment of RX/TX IRQ's · 5df969c3
      Thomas Falcon 提交于
      The driver currently creates RX/TX queues during device probe, but
      assigns IRQ's to them during device open. On reset, however,
      IRQ's are assigned when resetting the queues. If there is a reset
      while the device is closed and the device is later opened, the driver will
      request IRQ's twice, causing the open to fail. This patch assigns
      the IRQ's in the ibmvnic_init function after the queues are reset or
      initialized, ensuring IRQ's are only requested once.
      Signed-off-by: NThomas Falcon <tlfalcon@linux.vnet.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5df969c3
  12. 22 6月, 2017 2 次提交
    • N
      ibmvnic: Correct return code checking for ibmvnic_init during probe · 6d659237
      Nathan Fontenot 提交于
      The update to ibmvnic_init to allow an EAGAIN return code broke
      the calling of ibmvnic_init from ibmvnic_probe. The code now
      will return from this point in the probe routine if anything
      other than EAGAIN is returned. The check should be to see if rc
      is non-zero and not equal to EAGAIN.
      
      Without this fix, the vNIC driver can return 0 (success) from
      its probe routine due to ibmvnic_init returning zero, but before
      completing the probe process and registering with the netdev layer.
      
      Fixes: 6a2fb0e9 (ibmvnic: driver initialization for kdump/kexec)
      Signed-off-by: NNathan Fontenot <nfont@linux.vnet.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6d659237
    • T
      ibmvnic: Fix error handling when registering long-term-mapped buffers · f3be0cbc
      Thomas Falcon 提交于
      The patch stores the return code of the REQUEST_MAP_RSP sub-CRQ command
      in the private data structure, where it can be later checked during
      device open or a reset.
      
      In the case of a reset, the mapping request to the vNIC Server may fail,
      especially in the case of a partition migration. The driver attempts to
      handle this by re-allocating the buffer and re-sending the mapping request.
      
      The original error handling implementation was removed. The separate
      function handling the REQUEST_MAP response message was also removed,
      since it is now simple enough to be handled in the ibmvnic_handle_crq
      function.
      Signed-off-by: NThomas Falcon <tlfalcon@linux.vnet.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f3be0cbc
  13. 21 6月, 2017 1 次提交
  14. 17 6月, 2017 1 次提交
    • N
      ibmvnic: driver initialization for kdump/kexec · 6a2fb0e9
      Nathan Fontenot 提交于
      When booting into the kdump/kexec kernel, pHyp and vios
      are not prepared for the initialization crq request and
      a failover transport event is generated. This is not
      handled correctly.
      
      At this point in initialization the driver is still in
      the 'probing' state and cannot handle a full reset of the
      driver as is normally done for a failover transport event.
      
      To correct this we catch driver resets while still in the
      'probing' state and return EAGAIN. This results in the
      driver tearing down the main crq and calling ibmvnic_init()
      again.
      Signed-off-by: NNathan Fontenot <nfont@linux.vnet.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6a2fb0e9
  15. 16 6月, 2017 5 次提交
  16. 14 6月, 2017 2 次提交
    • N
      ibmvnic: Remove netdev notify for failover resets · 61d3e1d9
      Nathan Fontenot 提交于
      When handling a driver reset due to a failover of the backing
      server on the vios, doing the netdev_notify_peers() can cause
      network traffic to stall or halt. Remove the netdev notify call
      for failover resets.
      Signed-off-by: NNathan Fontenot <nfont@linux.vnet.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      61d3e1d9
    • T
      ibmvnic: Client-initiated failover · 40c9db8a
      Thomas Falcon 提交于
      The IBM vNIC protocol provides support for the user to initiate
      a failover from the client LPAR in case the current backing infrastructure
      is deemed inadequate or in an error state.
      
      Support for two H_VIOCTL sub-commands for vNIC devices are required
      to implement this function. These commands are H_GET_SESSION_TOKEN
      and H_SESSION_ERR_DETECTED.
      
      "[H_GET_SESSION_TOKEN] is used to obtain a session token from a VNIC client
      adapter.  This token is opaque to the caller and is intended to be used in
      tandem with the SESSION_ERROR_DETECTED vioctl subfunction."
      
      "[H_SESSION_ERR_DETECTED] is used to report that the currently active
      backing device for a VNIC client adapter is behaving poorly, and that
      the hypervisor should attempt to fail over to a different backing device,
      if one is available."
      
      To provide tools access to this functionality the vNIC driver creates a
      sysfs file that, when written to, will send a request to pHyp to failover
      to a different backing device.
      Signed-off-by: NThomas Falcon <tlfalcon@linux.vnet.ibm.com>
      Reviewed-by: NNathan Fontenot <nfont@linux.vnet.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      40c9db8a
  17. 08 6月, 2017 1 次提交
  18. 03 6月, 2017 1 次提交
  19. 27 5月, 2017 9 次提交