1. 01 11月, 2016 4 次提交
    • S
      qed*: Management firmware - notifications and defaults · 0fefbfba
      Sudarsana Kalluru 提交于
      Management firmware is interested in various tidbits about
      the driver - including the driver state & several configuration
      related fields [MTU, primtary MAC, etc.].
      This adds the necessray logic to update MFW with such configurations,
      some of which are passed directly via qed while for others APIs
      are provide so that qede would be able to later configure if needed.
      
      This also introduces a new default configuration for MTU which would
      replace the default inherited by being an ethernet device.
      Signed-off-by: NSudarsana Kalluru <Sudarsana.Kalluru@cavium.com>
      Signed-off-by: NYuval Mintz <Yuval.Mintz@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0fefbfba
    • J
      solos-pci: use permission-specific DEVICE_ATTR variants · 89d9123e
      Julia Lawall 提交于
      Use DEVICE_ATTR_RW for read-write attributes.  This simplifies the
      source code, improves readbility, and reduces the chance of
      inconsistencies.
      
      The semantic patch that makes this change is as follows:
      (http://coccinelle.lip6.fr/)
      
      // <smpl>
      @rw@
      declarer name DEVICE_ATTR;
      identifier x,x_show,x_store;
      @@
      
      DEVICE_ATTR(x, \(0644\|S_IRUGO|S_IWUSR\), x_show, x_store);
      
      @script:ocaml@
      x << rw.x;
      x_show << rw.x_show;
      x_store << rw.x_store;
      @@
      
      if not (x^"_show" = x_show && x^"_store" = x_store)
      then Coccilib.include_match false
      
      @@
      declarer name DEVICE_ATTR_RW;
      identifier rw.x,rw.x_show,rw.x_store;
      @@
      
      - DEVICE_ATTR(x, \(0644\|S_IRUGO|S_IWUSR\), x_show, x_store);
      + DEVICE_ATTR_RW(x);
      // </smpl>
      Signed-off-by: NJulia Lawall <Julia.Lawall@lip6.fr>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      89d9123e
    • J
      ptp: use permission-specific DEVICE_ATTR variants · 63215705
      Julia Lawall 提交于
      Use DEVICE_ATTR_RO for read only attributes.  This simplifies the
      source code, improves readbility, and reduces the chance of
      inconsistencies.
      
      The semantic patch that makes this change is as follows:
      (http://coccinelle.lip6.fr/)
      
      // <smpl>
      @ro@
      declarer name DEVICE_ATTR;
      identifier x,x_show;
      @@
      
      DEVICE_ATTR(x, \(0444\|S_IRUGO\), x_show, NULL);
      
      @script:ocaml@
      x << ro.x;
      x_show << ro.x_show;
      @@
      
      if not (x^"_show" = x_show) then Coccilib.include_match false
      
      @@
      declarer name DEVICE_ATTR_RO;
      identifier ro.x,ro.x_show;
      @@
      
      - DEVICE_ATTR(x, \(0444\|S_IRUGO\), x_show, NULL);
      + DEVICE_ATTR_RO(x);
      // </smpl>
      Signed-off-by: NJulia Lawall <Julia.Lawall@lip6.fr>
      Acked-by: NRichard Cochran <richardcochran@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      63215705
    • A
      ldmvsw: tx queue stuck in stopped state after LDC reset · 8778b276
      Aaron Young 提交于
      The following patch fixes an issue with the ldmvsw driver where
      the network connection of a guest domain becomes non-functional after
      the guest domain has panic'd and rebooted.
      
      The root cause was determined to be from the following series of
      events:
      
      1. Guest domain panics - resulting in the guest no longer processing
         network packets (from ldmvsw driver)
      2. The ldmvsw driver (in the control domain) eventually exerts flow
         control due to no more available tx drings and stops the tx queue
         for the guest domain
      3. The LDC of the network connection for the guest is reset when
         the guest domain reboots after the panic.
      4. The LDC reset event is received by the ldmvsw driver and the ldmvsw
         responds by clearing the tx queue for the guest.
      5. ldmvsw waits indefinitely for a DATA ACK from the guest - which is
         the normal method to re-enable the tx queue. But the ACK never comes
         because the tx queue was cleared due to the LDC reset.
      
      To fix this issue, in addition to clearing the tx queue, re-enable the
      tx queue on a LDC reset. This prevents the ldmvsw from getting caught in
      this deadlocked state of waiting for a DATA ACK which will never come.
      Signed-off-by: NAaron Young <Aaron.Young@oracle.com>
      Acked-by: NSowmini Varadhan <sowmini.varadhan@oracle.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8778b276
  2. 31 10月, 2016 20 次提交
  3. 30 10月, 2016 16 次提交