1. 24 8月, 2012 1 次提交
  2. 24 4月, 2012 4 次提交
  3. 15 12月, 2011 1 次提交
  4. 22 9月, 2011 1 次提交
  5. 30 6月, 2011 1 次提交
  6. 22 12月, 2010 1 次提交
    • K
      [SCSI] mpt2sas: Modify code to support Expander switch · 7f6f794d
      Kashyap, Desai 提交于
      Issue : Switch swap doesn't work when device missing delay is enabled.
      
      (1) add support to individually add and remove phys to and from
      existing ports. This replaces the routine
      _transport_delete_duplicate_port.
      (2) _scsih_sas_host_refresh - was modified to change the link rate
      from zero to 1.5 GB rate when the firmware reports there is an
      attached device with zero link.
      (3) add new function mpt2sas_device_remove, this is wrapper function
      deletes some redundant code through out driver by combining into one
      subrountine
      (4) two subroutines were modified so the sas_device, raid_device, and
      port lists are traversed once when objects are deleted from the list.
      Previously it was looping back each time an object was deleted from the
      list.
      Signed-off-by: NKashyap Desai <kashyap.desai@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      7f6f794d
  7. 28 7月, 2010 5 次提交
  8. 12 4月, 2010 1 次提交
    • K
      [SCSI] mpt2sas: sanity added to remove duplicate port from topology · 38c29114
      Kashyap, Desai 提交于
      There are few special cases which needs to be handled deleting old port.
      
      CASE1: In topology you need cascaded expanders. Through sysfs just make sure
      topology is up. Erase the manufacturing image of the cascaded expander and
      reset the board. In some cases Adapter will receive Exapnder Add event
      before expander delete. In such a case, driver needs to delete duplicate
      port before adding new port.
      
      CASE2: Enable Device Missing delay of HBA through lsiutils. If expander or
      end device is hotswapped with different device before DMD timer expires,
      driver will get device add for new device first and then device deletion
      event for the original devices will arrive later at DMD timer expires. In
      this case also driver need to delete duplicate port before adding port for
      new device.
      
      Added new function which will make sure when new port is
      added, that its not claiming the same phy resources already in use by
      another port. If it does, then it will delete the other port before adding
      the new port.
      Signed-off-by: NKashyap Desai <kashyap.desai@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      38c29114
  9. 11 4月, 2010 2 次提交
  10. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  11. 09 2月, 2010 1 次提交
    • K
      [SCSI] mpt2sas: Added phy_enable and set_phy_speed sysfs callback support. · 50d5c606
      Kashyap, Desai 提交于
      Added new callbacks phy_enable and set_phy_speed in the
      mpt2sas_transport_functions template. This will allow end user to
      enable/disable phys and change links rates using the SysFS interface.
      Current implementation only supports direct attached phys, but we
      could in the future add support for expander based phys.
      A new subroutine mpt2sas_config_set_sas_iounit_pg1 was added;
      this wrapper function used to send request to controller firmware to modify
      the phys and link rates. A new subroutine _transport_find_local_phy was added;
      a function for easly obtaining the local phy object for direct attached.
      
      Example to disable a phy
      echo 0 > /sys/class/phy3:0/enable
      
      Example to enable the same phy
      echo 1 > /sys/class/phy3:0/enable
      
      Example to change the link rate to 1.5
      #echo "1.5 Gbit" > /sys/class/phy3:0/maximum_linkrate
      #cat /sys/class/phy3:0/negotiated_linkrate
      1.5 Gbit
      
      Example to change the link rate to 3.0
      #echo "3.0 Gbit" > /sys/class/phy3:0/maximum_linkrate
      #cat /sys/class/phy3:0/negotiated_linkrate
      3.0 Gbit
      
      Example to change the link rate to 6.0
      #echo "6.0 Gbit" > /sys/class/phy3:0/maximum_linkrate
      #cat /sys/class/phy3:0/negotiated_linkrate
      6.0 Gbit
      Signed-off-by: NKashyap Desai <kashyap.desai@lsi.com>
      Reviewed-by: NEric Moore <eric.moore@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      50d5c606
  12. 30 10月, 2009 2 次提交
    • K
      [SCSI] mpt2sas : PPC (power pc) endian bug fix's · 463217bf
      Kashyap, Desai 提交于
      (1) EEDP(End to End data protection) was not working. This was due to not
      setting EEDP BlockSize and Flags to little endian format in the message
      frame.
      (2) Some expander sysfs attributes were not getting set properly.  The sas
      format was not getting set due to endian issues with sas_format field in the
      struct rep_manu_reply. Since sas_format was not set properly, the
      component_vendor_id, component_revision_id, and component_id were not set.
      (3) In _transport_smp_handler: we don't need to convert the smid from little
      endian to cpu prior to calling mpt2sas_base_free_smid, because its allready
      in cpu format. (4) Some loginfos and ioc status were not xonverted from
      little endian to cpu.
      Signed-off-by: NKashyap Desai <kashyap.desai@lsi.com>
      Signed-off-by: NEric Moore <Eric.moore@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      463217bf
    • K
      [SCSI] mpt2sas: Driver will use sas address instead of handle as a lookup · c5e039be
      Kashyap, Desai 提交于
      The device driver was not handling updating device handles in all cases
      across diag resets. To fix this issue, the driver is converted to using sas
      address instead of handle as a lookup reference to the parent expander or
      sas_host. Also, for both expanders and sas host, the phy handle will be one
      unique handle. In the sas host case, the phy handle can be different for
      every phy, so the change is to set the handle to the handle of the first
      phy; every phy will be one single sas address(phy 0) instead of a different
      sas address for every phy(previous implementation). So making one consistent
      sas address for all the direct attachedports to the sas host, will make it
      better user experience when using udev /dev/disk/by-path dev nodes
      Signed-off-by: NKashyap Desai <kashyap.desai@lsi.com>
      Signed-off-by: NEric Moore <Eric.moore@lsi.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      c5e039be
  13. 02 10月, 2009 4 次提交
  14. 05 9月, 2009 2 次提交
  15. 24 5月, 2009 1 次提交
  16. 19 5月, 2009 1 次提交
    • T
      block: set rq->resid_len to blk_rq_bytes() on issue · 5f49f631
      Tejun Heo 提交于
      In commit c3a4d78c, while introducing
      rq->resid_len, the default value of residue count was changed from
      full count to zero.  The conversion was done under the assumption that
      when a request fails residue count wasn't defined.  However, Boaz and
      James pointed out that this wasn't true and the residue count should
      be preserved for failed requests too.
      
      This patchset restores the original behavior by setting rq->resid_len
      to blk_rq_bytes(rq) on request start and restoring explicit clearing
      in affected drivers.  While at it, take advantage of the fact that
      rq->resid_len is set to full count where applicable.
      
      * ide-cd: rq->resid_len cleared on pc success
      
      * mptsas: req->resid_len cleared on success
      
      * sas_expander: rsp/req->resid_len cleared on success
      
      * mpt2sas_transport: req->resid_len cleared on success
      
      * ide-cd, ide-tape, mptsas, sas_host_smp, mpt2sas_transport, ub: take
        advantage of initial full count to simplify code
      
      Boaz Harrosh spotted bug in resid_len initialization.  Fixed as
      suggested.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Acked-by: NBorislav Petkov <petkovbb@googlemail.com>
      Cc: Boaz Harrosh <bharrosh@panasas.com>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: Pete Zaitcev <zaitcev@redhat.com>
      Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
      Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>
      Cc: Eric Moore <Eric.Moore@lsi.com>
      Cc: Darrick J. Wong <djwong@us.ibm.com>
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      5f49f631
  17. 11 5月, 2009 2 次提交
    • T
      block: cleanup rq->data_len usages · b0790410
      Tejun Heo 提交于
      With recent unification of fields, it's now guaranteed that
      rq->data_len always equals blk_rq_bytes().  Convert all non-IDE direct
      users to accessors.  IDE will be converted in a separate patch.
      
      Boaz: spotted incorrect data_len/resid_len conversion in osd.
      
      [ Impact: convert direct rq->data_len usages to blk_rq_bytes() ]
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Acked-by: NSergei Shtylyov <sshtylyov@ru.mvista.com>
      Cc: Pete Zaitcev <zaitcev@redhat.com>
      Cc: Eric Moore <Eric.Moore@lsi.com>
      Cc: Markus Lidel <Markus.Lidel@shadowconnect.com>
      Cc: Darrick J. Wong <djwong@us.ibm.com>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: Eric Moore <Eric.Moore@lsi.com>
      Cc: Boaz Harrosh <bharrosh@panasas.com>
      Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      b0790410
    • T
      block: add rq->resid_len · c3a4d78c
      Tejun Heo 提交于
      rq->data_len served two purposes - the length of data buffer on issue
      and the residual count on completion.  This duality creates some
      headaches.
      
      First of all, block layer and low level drivers can't really determine
      what rq->data_len contains while a request is executing.  It could be
      the total request length or it coulde be anything else one of the
      lower layers is using to keep track of residual count.  This
      complicates things because blk_rq_bytes() and thus
      [__]blk_end_request_all() relies on rq->data_len for PC commands.
      Drivers which want to report residual count should first cache the
      total request length, update rq->data_len and then complete the
      request with the cached data length.
      
      Secondly, it makes requests default to reporting full residual count,
      ie. reporting that no data transfer occurred.  The residual count is
      an exception not the norm; however, the driver should clear
      rq->data_len to zero to signify the normal cases while leaving it
      alone means no data transfer occurred at all.  This reverse default
      behavior complicates code unnecessarily and renders block PC on some
      drivers (ide-tape/floppy) unuseable.
      
      This patch adds rq->resid_len which is used only for residual count.
      
      While at it, remove now unnecessasry blk_rq_bytes() caching in
      ide_pc_intr() as rq->data_len is not changed anymore.
      
      Boaz	: spotted missing conversion in osd
      Sergei	: spotted too early conversion to blk_rq_bytes() in ide-tape
      
      [ Impact: cleanup residual count handling, report 0 resid by default ]
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
      Cc: Borislav Petkov <petkovbb@googlemail.com>
      Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>
      Cc: Mike Miller <mike.miller@hp.com>
      Cc: Eric Moore <Eric.Moore@lsi.com>
      Cc: Alan Stern <stern@rowland.harvard.edu>
      Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Cc: Doug Gilbert <dgilbert@interlog.com>
      Cc: Mike Miller <mike.miller@hp.com>
      Cc: Eric Moore <Eric.Moore@lsi.com>
      Cc: Darrick J. Wong <djwong@us.ibm.com>
      Cc: Pete Zaitcev <zaitcev@redhat.com>
      Cc: Boaz Harrosh <bharrosh@panasas.com>
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      c3a4d78c
  18. 14 3月, 2009 1 次提交
    • E
      [SCSI] mpt2sas v00.100.11.15 · 635374e7
      Eric Moore 提交于
      * This is new scsi lld device driver from LSI supporting the SAS 2.0
        standard. I have split patchs by filename.
      
      * Here is list of new 6gb host controllers:
      
        LSI SAS2004
        LSI SAS2008
        LSI SAS2108
        LSI SAS2116
      
      * Here are the changes in the 4th posting of this patch set:
      
      (1) fix compile errors when SCSI_MPT2SAS_LOGGING is not enabled
      (2) add mpt2sas to the SCSI Mid Layer Makefile
      (3) append mpt2sas_ to the naming of all non-static functions
      (4) fix oops for SMP_PASSTHRU
      (5) doorbell algorithm imported changes from windows driver
      
      * Here are the changes in the 3rd posting of this patch set:
      
      (1) add readl following writel from the function that disables interrupts
      (2) replace 0xFFFFFFFFFFFFFFFFULL with ~0ULL
      (3) when calling pci_enable_msix, only pass one msix entry (instead of 15).
      (4) remove the "current HW implementation uses..... " comment in the sources
      (5) merged bug fix for SIGIO/POLLIN notifcation; reported by the storlib team.
      
      * Here are the changes in the 2nd posting of this patch set:
      
      (1) use little endian types in the mpi headers
      (2) merged in bug fix's from inhouse drivers.
      Signed-off-by: NEric Moore <eric.moore@lsi.com>
      Tested-by: Npeter Bogdanovic <pbog@us.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      635374e7
新手
引导
客服 返回
顶部