1. 11 Feb, 2007 5 commits
    • David S. Miller's avatar
      [SPARC64]: Update defconfig. · 784020fb
      David S. Miller authored
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      784020fb
    • David S. Miller's avatar
      [SPARC64]: Add PCI MSI support on Niagara. · 35a17eb6
      David S. Miller authored
      This is kind of hokey, we could use the hardware provided facilities
      much better.
      
      MSIs are assosciated with MSI Queues.  MSI Queues generate interrupts
      when any MSI assosciated with it is signalled.  This suggests a
      two-tiered IRQ dispatch scheme:
      
      	MSI Queue interrupt --> queue interrupt handler
      		MSI dispatch --> driver interrupt handler
      
      But we just get one-level under Linux currently.  What I'd like to do
      is possibly stick the IRQ actions into a per-MSI-Queue data structure,
      and dispatch them form there, but the generic IRQ layer doesn't
      provide a way to do that right now.
      
      So, the current kludge is to "ACK" the interrupt by processing the
      MSI Queue data structures and ACK'ing them, then we run the actual
      handler like normal.
      
      We are wasting a lot of useful information, for example the MSI data
      and address are provided with ever MSI, as well as a system tick if
      available.  If we could pass this into the IRQ handler it could help
      with certain things, in particular for PCI-Express error messages.
      
      The MSI entries on sparc64 also tell you exactly which bus/device/fn
      sent the MSI, which would be great for error handling when no
      registered IRQ handler can service the interrupt.
      
      We override the disable/enable IRQ chip methods in sun4v_msi, so we
      have to call {mask,unmask}_msi_irq() directly from there.  This is
      another ugly wart.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      35a17eb6
    • David S. Miller's avatar
      [SPARC64] IRQ: Use irq_desc->chip_data instead of irq_desc->handler_data · 68c92186
      David S. Miller authored
      Otherwise we can't use the generic MSI code.
      
      Furthermore, properly use the {get,set}_irq_foo() abstracted
      interfaces instead of direct accesses to irq_desc[]->foo.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      68c92186
    • Fabio Massimo Di Nitto's avatar
    • Fabio Massimo Di Nitto's avatar
      [PARTITION]: Add whole_disk attribute. · d18d7682
      Fabio Massimo Di Nitto authored
      Some partitioning systems create special partitions that
      span the entire disk.  One example are Sun partitions, and
      this whole-disk partition exists to tell the firmware the
      extent of the entire device so it can load the boot block
      and do other things.
      
      Such partitions should not be treated as normal partitions,
      because all the other partitions overlap this whole-disk one.
      So we'd see multiple instances of the same UUID etc. which
      we do not want.  udev and friends can thus search for this
      'whole_disk' attribute and use it to decide to ignore the
      partition.
      Signed-off-by: default avatarFabio Massimo Di Nitto <fabbione@ubuntu.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      d18d7682
  2. 09 Feb, 2007 35 commits