1. 16 Jul, 2007 6 commits
    • David S. Miller's avatar
      [SPARC64]: Add domain-services nodes to VIO device tree. · 2c4f4ecb
      David S. Miller authored
      They sit under the root of the MD tree unlike the rest of
      the LDC channel based virtual devices.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • David S. Miller's avatar
      [SPARC64]: Assorted LDC bug cures. · cb481235
      David S. Miller authored
      1) LDC_MODE_RELIABLE is deprecated an unused by anything, plus
         it and LDC_MODE_STREAM were mis-numbered.
      2) read_stream() should try to read as much as possible into
         the per-LDC stream buffer area, so do not trim the read_nonraw()
         length by the caller's size parameter.
      3) Send data ACKs when necessary in read_nonraw().
      4) In read_nonraw() when we get a pure ACK, advance the RX head
         unconditionally past it.
      5) Provide the ACKID field in the ldcdgb() packet dump in read_nonraw().
         This helps debugging stream mode LDC channel problems.
      6) Decrease verbosity of rx_data_wait() so that it is more useful.
         A debugging message each loop iteration is too much.
      7) In process_data_ack() stop the loop checking when we hit lp->tx_tail
         not lp->tx_head.
      8) Set the seqid field properly in send_data_nack().
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • David S. Miller's avatar
      [SPARC64]: Do not ACK an INO if it is disabled or inprogress. · 5a606b72
      David S. Miller authored
      This is also a partial workaround for a bug in the LDOM firmware which
      double-transmits RX inos during high load.  Without this, such an
      event causes the kernel to loop forever in the interrupt call chain
      ACK'ing but never actually running the IRQ handler (and thus clearing
      the interrupt condition in the device).
      There is still a bad potential effect when double INOs occur,
      not covered by this changeset.  Namely, if the INO is already on
      the per-cpu INO vector list, we still blindly re-insert it and
      thus we can end up losing interrupts already linked in after
      We could deal with that by traversing the list before insertion,
      but that's too expensive for this edge case.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • David S. Miller's avatar
    • David S. Miller's avatar
    • David S. Miller's avatar
      [SPARC64]: Add LDOM virtual channel driver and VIO device layer. · e53e97ce
      David S. Miller authored
      Virtual devices on Sun Logical Domains are built on top
      of a virtual channel framework.  This, with help of hypervisor
      interfaces, provides a link layer protocol with basic
      handshaking over which virtual device clients and servers
      Built on top of this is a VIO device protocol which has it's
      own handshaking and message types.  At this layer attributes
      are exchanged (disk size, network device addresses, etc.)
      descriptor rings are registered, and data transfers are
      triggers and replied to.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  2. 15 Jul, 2007 34 commits