1. 09 2月, 2010 3 次提交
  2. 19 1月, 2010 1 次提交
    • G
      [SCSI] lpfc: restore MSI-X/MSI support · 8605c46c
      George Kadianakis 提交于
      A Gentoo bug report [1] showed that as of 2.6.31 lpfc only uses INTx interrupts.
      This patch restores lpfc's ability to support MSI-X/MSI interrupts that the
      "Addition of SLI4 Interface - Base Support" patch [2] broke.
      It reestablishes MSI-X as the default interrupt method and in case MSI-X is not
      supported lpfc_sli{4,}_enable_intr fallbacks to MSI and then to INTx.
      
      [1]: http://bugs.gentoo.org/show_bug.cgi?id=296319
      [2]: commit da0436e9
      
      [James Smart:
      Background:
      Nothing Broke. This was intended.
      
      We had originally enabled MSI-X by default, but in qualification within the
      last 12 months, we encountered a major catch-22:
      
      There were at least 4 platforms, from 2 major OEMs, that :
      - Say they support MSI-X - platform routines work and act as if they do.
      - We enable it, generate a test interrupt to check they really do deliver it,
      and it works.
      - But shortly after attachment, the system hangs or loses interrupts,
      resulting in a bad system behavior.
      
      Given the distro's picking up the 2.6.32 kernel, we had to stick with a
      default of MSI-X off, with user-enabled MSI-X as these platforms couldn't get
      fixed.
      
      However, we're also now encountering platforms that require MSI-X and never
      INTx, so we must change. It's desired also for also for performance reasons.
      
      So - now (2.6.33) is the right time to re-enable MSI-X by default.
      ]
      [jejb: fix up comment on default values]
      Signed-off-by: NGeorge Kadianakis <desnacked@gmail.com>
      Acked-by: NJames Smart  <james.smart@emulex.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      8605c46c
  3. 18 1月, 2010 1 次提交
  4. 05 1月, 2010 6 次提交
  5. 10 12月, 2009 1 次提交
  6. 05 12月, 2009 14 次提交
  7. 04 12月, 2009 1 次提交
  8. 02 10月, 2009 1 次提交
  9. 21 9月, 2009 1 次提交
  10. 23 8月, 2009 9 次提交
  11. 16 6月, 2009 1 次提交
    • G
      debugfs: Fix terminology inconsistency of dir name to mount debugfs filesystem. · 156f5a78
      GeunSik Lim 提交于
      Many developers use "/debug/" or "/debugfs/" or "/sys/kernel/debug/"
      directory name to mount debugfs filesystem for ftrace according to
      ./Documentation/tracers/ftrace.txt file.
      
      And, three directory names(ex:/debug/, /debugfs/, /sys/kernel/debug/) is
      existed in kernel source like ftrace, DRM, Wireless, Documentation,
      Network[sky2]files to mount debugfs filesystem.
      
      debugfs means debug filesystem for debugging easy to use by greg kroah
      hartman. "/sys/kernel/debug/" name is suitable as directory name
      of debugfs filesystem.
      - debugfs related reference: http://lwn.net/Articles/334546/
      
      Fix inconsistency of directory name to mount debugfs filesystem.
      
      * From Steven Rostedt
        - find_debugfs() and tracing_files() in this patch.
      Signed-off-by: NGeunSik Lim <geunsik.lim@samsung.com>
      Acked-by     : Inaky Perez-Gonzalez <inaky@linux.intel.com>
      Reviewed-by  : Steven Rostedt <rostedt@goodmis.org>
      Reviewed-by  : James Smart <james.smart@emulex.com>
      CC: Jiri Kosina <trivial@kernel.org>
      CC: David Airlie <airlied@linux.ie>
      CC: Peter Osterlund <petero2@telia.com>
      CC: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
      CC: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
      CC: Masami Hiramatsu <mhiramat@redhat.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      156f5a78
  12. 15 6月, 2009 1 次提交