Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
/* $NetBSD: isp_netbsd.c,v 1.44 2001/05/25 21:45:55 mjacob Exp $ */
|
2000-08-14 11:08:12 +04:00
|
|
|
/*
|
|
|
|
* This driver, which is contained in NetBSD in the files:
|
|
|
|
*
|
|
|
|
* sys/dev/ic/isp.c
|
2000-12-23 04:37:57 +03:00
|
|
|
* sys/dev/ic/isp_inline.h
|
|
|
|
* sys/dev/ic/isp_netbsd.c
|
|
|
|
* sys/dev/ic/isp_netbsd.h
|
|
|
|
* sys/dev/ic/isp_target.c
|
|
|
|
* sys/dev/ic/isp_target.h
|
|
|
|
* sys/dev/ic/isp_tpublic.h
|
|
|
|
* sys/dev/ic/ispmbox.h
|
|
|
|
* sys/dev/ic/ispreg.h
|
|
|
|
* sys/dev/ic/ispvar.h
|
2000-08-14 11:08:12 +04:00
|
|
|
* sys/microcode/isp/asm_sbus.h
|
|
|
|
* sys/microcode/isp/asm_1040.h
|
|
|
|
* sys/microcode/isp/asm_1080.h
|
|
|
|
* sys/microcode/isp/asm_12160.h
|
|
|
|
* sys/microcode/isp/asm_2100.h
|
|
|
|
* sys/microcode/isp/asm_2200.h
|
|
|
|
* sys/pci/isp_pci.c
|
|
|
|
* sys/sbus/isp_sbus.c
|
|
|
|
*
|
|
|
|
* Is being actively maintained by Matthew Jacob (mjacob@netbsd.org).
|
|
|
|
* This driver also is shared source with FreeBSD, OpenBSD, Linux, Solaris,
|
|
|
|
* Linux versions. This tends to be an interesting maintenance problem.
|
|
|
|
*
|
|
|
|
* Please coordinate with Matthew Jacob on changes you wish to make here.
|
|
|
|
*/
|
1998-07-15 23:44:04 +04:00
|
|
|
/*
|
|
|
|
* Platform (NetBSD) dependent common attachment code for Qlogic adapters.
|
1999-07-06 00:31:35 +04:00
|
|
|
* Matthew Jacob <mjacob@nas.nasa.gov>
|
|
|
|
*/
|
|
|
|
/*
|
|
|
|
* Copyright (C) 1997, 1998, 1999 National Aeronautics & Space Administration
|
1998-07-15 23:44:04 +04:00
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
1999-07-06 00:31:35 +04:00
|
|
|
* notice, this list of conditions and the following disclaimer.
|
1998-07-15 23:44:04 +04:00
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
* 3. The name of the author may not be used to endorse or promote products
|
1999-07-06 00:31:35 +04:00
|
|
|
* derived from this software without specific prior written permission
|
1998-07-15 23:44:04 +04:00
|
|
|
*
|
1999-07-06 00:31:35 +04:00
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
|
|
|
|
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
|
|
|
|
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
|
|
|
|
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
|
|
|
|
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
|
|
|
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
|
|
|
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
1998-07-15 23:44:04 +04:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include <dev/ic/isp_netbsd.h>
|
1999-10-14 06:31:11 +04:00
|
|
|
#include <sys/scsiio.h>
|
1998-07-15 23:44:04 +04:00
|
|
|
|
2000-07-07 07:14:53 +04:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Set a timeout for the watchdogging of a command.
|
|
|
|
*
|
|
|
|
* The dimensional analysis is
|
|
|
|
*
|
|
|
|
* milliseconds * (seconds/millisecond) * (ticks/second) = ticks
|
|
|
|
*
|
|
|
|
* =
|
|
|
|
*
|
|
|
|
* (milliseconds / 1000) * hz = ticks
|
|
|
|
*
|
|
|
|
*
|
|
|
|
* For timeouts less than 1 second, we'll get zero. Because of this, and
|
|
|
|
* because we want to establish *our* timeout to be longer than what the
|
|
|
|
* firmware might do, we just add 3 seconds at the back end.
|
|
|
|
*/
|
|
|
|
#define _XT(xs) ((((xs)->timeout/1000) * hz) + (3 * hz))
|
2000-07-06 02:23:05 +04:00
|
|
|
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
static void ispminphys_1020(struct buf *);
|
2001-03-14 08:44:21 +03:00
|
|
|
static void ispminphys(struct buf *);
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
static INLINE void ispcmd(struct ispsoftc *, XS_T *);
|
|
|
|
static void isprequest(struct scsipi_channel *, scsipi_adapter_req_t, void *);
|
2001-04-25 21:53:04 +04:00
|
|
|
static int
|
|
|
|
ispioctl(struct scsipi_channel *, u_long, caddr_t, int, struct proc *);
|
1998-07-15 23:44:04 +04:00
|
|
|
|
2001-04-25 21:53:04 +04:00
|
|
|
static void isp_polled_cmd(struct ispsoftc *, XS_T *);
|
2001-03-14 08:44:21 +03:00
|
|
|
static void isp_dog(void *);
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
static void isp_create_fc_worker(void *);
|
|
|
|
static void isp_fc_worker(void *);
|
1999-02-09 03:42:22 +03:00
|
|
|
|
1998-07-15 23:44:04 +04:00
|
|
|
/*
|
|
|
|
* Complete attachment of hardware, include subdevices.
|
|
|
|
*/
|
|
|
|
void
|
2001-03-14 08:44:21 +03:00
|
|
|
isp_attach(struct ispsoftc *isp)
|
1998-07-15 23:44:04 +04:00
|
|
|
{
|
|
|
|
isp->isp_state = ISP_RUNSTATE;
|
2001-04-25 21:53:04 +04:00
|
|
|
|
|
|
|
isp->isp_osinfo._adapter.adapt_dev = &isp->isp_osinfo._dev;
|
|
|
|
isp->isp_osinfo._adapter.adapt_nchannels = IS_DUALBUS(isp) ? 2 : 1;
|
|
|
|
isp->isp_osinfo._adapter.adapt_openings = isp->isp_maxcmds;
|
|
|
|
/*
|
|
|
|
* It's not stated whether max_periph is limited by SPI
|
|
|
|
* tag uage, but let's assume that it is.
|
|
|
|
*/
|
|
|
|
isp->isp_osinfo._adapter.adapt_max_periph = min(isp->isp_maxcmds, 255);
|
|
|
|
isp->isp_osinfo._adapter.adapt_ioctl = ispioctl;
|
|
|
|
isp->isp_osinfo._adapter.adapt_request = isprequest;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
if (isp->isp_type <= ISP_HA_SCSI_1020A) {
|
|
|
|
isp->isp_osinfo._adapter.adapt_minphys = ispminphys_1020;
|
|
|
|
} else {
|
|
|
|
isp->isp_osinfo._adapter.adapt_minphys = ispminphys;
|
|
|
|
}
|
2001-04-25 21:53:04 +04:00
|
|
|
|
|
|
|
isp->isp_osinfo._chan.chan_adapter = &isp->isp_osinfo._adapter;
|
|
|
|
isp->isp_osinfo._chan.chan_bustype = &scsi_bustype;
|
|
|
|
isp->isp_osinfo._chan.chan_channel = 0;
|
|
|
|
|
2000-08-02 03:55:09 +04:00
|
|
|
/*
|
|
|
|
* Until the midlayer is fixed to use REPORT LUNS, limit to 8 luns.
|
|
|
|
*/
|
2001-04-25 21:53:04 +04:00
|
|
|
isp->isp_osinfo._chan.chan_nluns = min(isp->isp_maxluns, 8);
|
|
|
|
|
1999-07-06 00:31:35 +04:00
|
|
|
if (IS_FC(isp)) {
|
2001-04-25 21:53:04 +04:00
|
|
|
isp->isp_osinfo._chan.chan_ntargets = MAX_FC_TARG;
|
|
|
|
isp->isp_osinfo._chan.chan_id = MAX_FC_TARG;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
isp->isp_osinfo.threadwork = 1;
|
|
|
|
/*
|
|
|
|
* Note that isp_create_fc_worker won't get called
|
|
|
|
* until much much later (after proc0 is created).
|
|
|
|
*/
|
|
|
|
kthread_create(isp_create_fc_worker, isp);
|
1998-07-15 23:44:04 +04:00
|
|
|
} else {
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
int bus = 0;
|
1999-05-12 22:59:23 +04:00
|
|
|
sdparam *sdp = isp->isp_param;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
|
2001-04-25 21:53:04 +04:00
|
|
|
isp->isp_osinfo._chan.chan_ntargets = MAX_TARGETS;
|
|
|
|
isp->isp_osinfo._chan.chan_id = sdp->isp_initiator_id;
|
1999-10-14 06:31:11 +04:00
|
|
|
isp->isp_osinfo.discovered[0] = 1 << sdp->isp_initiator_id;
|
1999-12-16 08:35:42 +03:00
|
|
|
if (IS_DUALBUS(isp)) {
|
2001-04-25 21:53:04 +04:00
|
|
|
isp->isp_osinfo._chan_b = isp->isp_osinfo._chan;
|
1999-05-12 22:59:23 +04:00
|
|
|
sdp++;
|
1999-10-17 05:23:21 +04:00
|
|
|
isp->isp_osinfo.discovered[1] =
|
|
|
|
1 << sdp->isp_initiator_id;
|
2001-04-25 21:53:04 +04:00
|
|
|
isp->isp_osinfo._chan_b.chan_id = sdp->isp_initiator_id;
|
|
|
|
isp->isp_osinfo._chan_b.chan_channel = 1;
|
1999-05-12 22:59:23 +04:00
|
|
|
}
|
2000-08-02 03:55:09 +04:00
|
|
|
ISP_LOCK(isp);
|
1999-05-12 22:59:23 +04:00
|
|
|
(void) isp_control(isp, ISPCTL_RESET_BUS, &bus);
|
1999-12-16 08:35:42 +03:00
|
|
|
if (IS_DUALBUS(isp)) {
|
1999-05-12 22:59:23 +04:00
|
|
|
bus++;
|
|
|
|
(void) isp_control(isp, ISPCTL_RESET_BUS, &bus);
|
|
|
|
}
|
2000-08-09 02:58:30 +04:00
|
|
|
ISP_UNLOCK(isp);
|
1999-03-17 09:15:47 +03:00
|
|
|
}
|
1999-02-09 03:42:22 +03:00
|
|
|
|
2000-08-02 03:55:09 +04:00
|
|
|
/*
|
|
|
|
* After this point, we'll be doing the new configuration
|
|
|
|
* schema which allows interrups, so we can do tsleep/wakeup
|
|
|
|
* for mailbox stuff at that point.
|
|
|
|
*/
|
|
|
|
isp->isp_osinfo.no_mbox_ints = 0;
|
|
|
|
|
1998-12-28 22:10:43 +03:00
|
|
|
/*
|
|
|
|
* And attach children (if any).
|
|
|
|
*/
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
config_found((void *)isp, &isp->isp_chanA, scsiprint);
|
1999-12-16 08:35:42 +03:00
|
|
|
if (IS_DUALBUS(isp)) {
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
config_found((void *)isp, &isp->isp_chanB, scsiprint);
|
1999-05-12 22:59:23 +04:00
|
|
|
}
|
1998-07-15 23:44:04 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* minphys our xfers
|
|
|
|
*/
|
|
|
|
|
|
|
|
static void
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
ispminphys_1020(struct buf *bp)
|
1998-07-15 23:44:04 +04:00
|
|
|
{
|
|
|
|
if (bp->b_bcount >= (1 << 24)) {
|
|
|
|
bp->b_bcount = (1 << 24);
|
|
|
|
}
|
|
|
|
minphys(bp);
|
|
|
|
}
|
|
|
|
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
static void
|
|
|
|
ispminphys(struct buf *bp)
|
|
|
|
{
|
|
|
|
if (bp->b_bcount >= (1 << 30)) {
|
|
|
|
bp->b_bcount = (1 << 30);
|
|
|
|
}
|
|
|
|
minphys(bp);
|
|
|
|
}
|
|
|
|
|
1999-10-14 06:31:11 +04:00
|
|
|
static int
|
2001-04-25 21:53:04 +04:00
|
|
|
ispioctl(struct scsipi_channel *chan, u_long cmd, caddr_t addr, int flag,
|
|
|
|
struct proc *p)
|
1999-10-14 06:31:11 +04:00
|
|
|
{
|
2001-04-25 21:53:04 +04:00
|
|
|
struct ispsoftc *isp = (void *)chan->chan_adapter->adapt_dev;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
int retval = ENOTTY;
|
1999-10-14 06:31:11 +04:00
|
|
|
|
|
|
|
switch (cmd) {
|
|
|
|
case SCBUSIORESET:
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
ISP_LOCK(isp);
|
2001-04-25 21:53:04 +04:00
|
|
|
if (isp_control(isp, ISPCTL_RESET_BUS, &chan->chan_channel))
|
1999-10-14 06:31:11 +04:00
|
|
|
retval = EIO;
|
|
|
|
else
|
|
|
|
retval = 0;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
ISP_UNLOCK(isp);
|
1999-10-14 06:31:11 +04:00
|
|
|
break;
|
2001-04-11 01:52:00 +04:00
|
|
|
case ISP_SDBLEV:
|
|
|
|
{
|
|
|
|
int olddblev = isp->isp_dblev;
|
|
|
|
isp->isp_dblev = *(int *)addr;
|
|
|
|
*(int *)addr = olddblev;
|
|
|
|
retval = 0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
case ISP_RESETHBA:
|
|
|
|
ISP_LOCK(isp);
|
|
|
|
isp_reinit(isp);
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
retval = 0;
|
|
|
|
break;
|
|
|
|
case ISP_FC_RESCAN:
|
|
|
|
if (IS_FC(isp)) {
|
|
|
|
ISP_LOCK(isp);
|
|
|
|
if (isp_fc_runstate(isp, 5 * 1000000)) {
|
|
|
|
retval = EIO;
|
|
|
|
} else {
|
|
|
|
retval = 0;
|
|
|
|
}
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
case ISP_FC_LIP:
|
|
|
|
if (IS_FC(isp)) {
|
|
|
|
ISP_LOCK(isp);
|
|
|
|
if (isp_control(isp, ISPCTL_SEND_LIP, 0)) {
|
|
|
|
retval = EIO;
|
|
|
|
} else {
|
|
|
|
retval = 0;
|
|
|
|
}
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
case ISP_FC_GETDINFO:
|
|
|
|
{
|
|
|
|
struct isp_fc_device *ifc = (struct isp_fc_device *) addr;
|
|
|
|
struct lportdb *lp;
|
|
|
|
|
|
|
|
if (ifc->loopid < 0 || ifc->loopid >= MAX_FC_TARG) {
|
|
|
|
retval = EINVAL;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
ISP_LOCK(isp);
|
|
|
|
lp = &FCPARAM(isp)->portdb[ifc->loopid];
|
|
|
|
if (lp->valid) {
|
|
|
|
ifc->loopid = lp->loopid;
|
|
|
|
ifc->portid = lp->portid;
|
|
|
|
ifc->node_wwn = lp->node_wwn;
|
|
|
|
ifc->port_wwn = lp->port_wwn;
|
|
|
|
retval = 0;
|
|
|
|
} else {
|
|
|
|
retval = ENODEV;
|
|
|
|
}
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
break;
|
|
|
|
}
|
1999-10-14 06:31:11 +04:00
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
return (retval);
|
|
|
|
}
|
|
|
|
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
static INLINE void
|
|
|
|
ispcmd(struct ispsoftc *isp, XS_T *xs)
|
1999-10-14 06:31:11 +04:00
|
|
|
{
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
ISP_LOCK(isp);
|
|
|
|
if (isp->isp_state < ISP_RUNSTATE) {
|
|
|
|
DISABLE_INTS(isp);
|
|
|
|
isp_init(isp);
|
|
|
|
if (isp->isp_state != ISP_INITSTATE) {
|
|
|
|
ENABLE_INTS(isp);
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
XS_SETERR(xs, HBA_BOTCH);
|
|
|
|
scsipi_done(xs);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
isp->isp_state = ISP_RUNSTATE;
|
|
|
|
ENABLE_INTS(isp);
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
* Handle the case of a FC card where the FC thread hasn't
|
|
|
|
* fired up yet and we have loop state to clean up. If we
|
|
|
|
* can't clear things up and we've never seen loop up, bounce
|
|
|
|
* the command.
|
|
|
|
*/
|
|
|
|
if (IS_FC(isp) && isp->isp_osinfo.threadwork &&
|
|
|
|
isp->isp_osinfo.thread == 0) {
|
|
|
|
volatile u_int8_t ombi = isp->isp_osinfo.no_mbox_ints;
|
|
|
|
int delay_time;
|
2001-04-25 21:53:04 +04:00
|
|
|
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
if (xs->xs_control & XS_CTL_POLL) {
|
|
|
|
isp->isp_osinfo.no_mbox_ints = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (isp->isp_osinfo.loop_checked == 0) {
|
|
|
|
delay_time = 10 * 1000000;
|
|
|
|
isp->isp_osinfo.loop_checked = 1;
|
|
|
|
} else {
|
|
|
|
delay_time = 250000;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (isp_fc_runstate(isp, delay_time) != 0) {
|
|
|
|
if (xs->xs_control & XS_CTL_POLL) {
|
|
|
|
isp->isp_osinfo.no_mbox_ints = ombi;
|
|
|
|
}
|
|
|
|
if (FCPARAM(isp)->loop_seen_once == 0) {
|
|
|
|
XS_SETERR(xs, HBA_SELTIMEOUT);
|
2001-04-25 21:53:04 +04:00
|
|
|
scsipi_done(xs);
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
ISP_UNLOCK(isp);
|
2001-04-25 21:53:04 +04:00
|
|
|
return;
|
|
|
|
}
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
/*
|
|
|
|
* Otherwise, fall thru to be queued up for later.
|
|
|
|
*/
|
|
|
|
} else {
|
|
|
|
int wasblocked =
|
|
|
|
(isp->isp_osinfo.blocked || isp->isp_osinfo.paused);
|
|
|
|
isp->isp_osinfo.threadwork = 0;
|
|
|
|
isp->isp_osinfo.blocked =
|
|
|
|
isp->isp_osinfo.paused = 0;
|
|
|
|
isp_prt(isp, ISP_LOGALL, "ispcmd, manual runstate, (freeze count %d)", isp->isp_chanA.chan_qfreeze);
|
|
|
|
if (wasblocked) {
|
|
|
|
scsipi_channel_thaw(&isp->isp_chanA, 1);
|
|
|
|
}
|
2001-04-25 21:53:04 +04:00
|
|
|
}
|
1999-10-01 03:06:18 +04:00
|
|
|
if (xs->xs_control & XS_CTL_POLL) {
|
2001-04-25 21:53:04 +04:00
|
|
|
isp->isp_osinfo.no_mbox_ints = ombi;
|
1999-02-09 03:42:22 +03:00
|
|
|
}
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
}
|
2000-07-06 02:23:05 +04:00
|
|
|
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
if (isp->isp_osinfo.paused) {
|
|
|
|
isp_prt(isp, ISP_LOGWARN, "I/O while paused");
|
|
|
|
xs->error = XS_RESOURCE_SHORTAGE;
|
|
|
|
scsipi_done(xs);
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (isp->isp_osinfo.blocked) {
|
|
|
|
isp_prt(isp, ISP_LOGWARN, "I/O while blocked");
|
|
|
|
xs->error = XS_REQUEUE;
|
|
|
|
scsipi_done(xs);
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (xs->xs_control & XS_CTL_POLL) {
|
|
|
|
volatile u_int8_t ombi = isp->isp_osinfo.no_mbox_ints;
|
|
|
|
isp->isp_osinfo.no_mbox_ints = 1;
|
|
|
|
isp_polled_cmd(isp, xs);
|
|
|
|
isp->isp_osinfo.no_mbox_ints = ombi;
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (isp_start(xs)) {
|
|
|
|
case CMD_QUEUED:
|
|
|
|
if (xs->timeout) {
|
|
|
|
callout_reset(&xs->xs_callout, _XT(xs), isp_dog, xs);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
case CMD_EAGAIN:
|
|
|
|
isp->isp_osinfo.paused = 1;
|
|
|
|
xs->error = XS_RESOURCE_SHORTAGE;
|
|
|
|
scsipi_channel_freeze(&isp->isp_chanA, 1);
|
|
|
|
if (IS_DUALBUS(isp)) {
|
|
|
|
scsipi_channel_freeze(&isp->isp_chanB, 1);
|
|
|
|
}
|
|
|
|
scsipi_done(xs);
|
|
|
|
break;
|
|
|
|
case CMD_RQLATER:
|
|
|
|
/*
|
|
|
|
* We can only get RQLATER from FC devices (1 channel only)
|
|
|
|
*
|
|
|
|
* Also, if we've never seen loop up, bounce the command
|
|
|
|
* (somebody has booted with no FC cable connected)
|
|
|
|
*/
|
|
|
|
if (FCPARAM(isp)->loop_seen_once == 0) {
|
|
|
|
XS_SETERR(xs, HBA_SELTIMEOUT);
|
2001-04-25 21:53:04 +04:00
|
|
|
scsipi_done(xs);
|
|
|
|
break;
|
|
|
|
}
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
if (isp->isp_osinfo.blocked == 0) {
|
|
|
|
isp->isp_osinfo.blocked = 1;
|
|
|
|
scsipi_channel_freeze(&isp->isp_chanA, 1);
|
|
|
|
isp_prt(isp, ISP_LOGALL, "ispcmd, RQLATER, (freeze count %d)", isp->isp_chanA.chan_qfreeze);
|
|
|
|
}
|
|
|
|
xs->error = XS_REQUEUE;
|
|
|
|
scsipi_done(xs);
|
|
|
|
break;
|
|
|
|
case CMD_COMPLETE:
|
|
|
|
scsipi_done(xs);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
ISP_UNLOCK(isp);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
isprequest(struct scsipi_channel *chan, scsipi_adapter_req_t req, void *arg)
|
|
|
|
{
|
|
|
|
struct ispsoftc *isp = (void *)chan->chan_adapter->adapt_dev;
|
|
|
|
|
|
|
|
switch (req) {
|
|
|
|
case ADAPTER_REQ_RUN_XFER:
|
|
|
|
ispcmd(isp, (XS_T *) arg);
|
|
|
|
break;
|
1998-07-15 23:44:04 +04:00
|
|
|
|
2001-04-25 21:53:04 +04:00
|
|
|
case ADAPTER_REQ_GROW_RESOURCES:
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
/* Not supported. */
|
|
|
|
break;
|
2001-04-25 21:53:04 +04:00
|
|
|
|
|
|
|
case ADAPTER_REQ_SET_XFER_MODE:
|
|
|
|
if (IS_SCSI(isp)) {
|
|
|
|
struct scsipi_xfer_mode *xm = arg;
|
|
|
|
int dflags = 0;
|
|
|
|
sdparam *sdp = SDPARAM(isp);
|
|
|
|
|
|
|
|
sdp += chan->chan_channel;
|
|
|
|
if (xm->xm_mode & PERIPH_CAP_TQING)
|
|
|
|
dflags |= DPARM_TQING;
|
|
|
|
if (xm->xm_mode & PERIPH_CAP_WIDE16)
|
|
|
|
dflags |= DPARM_WIDE;
|
|
|
|
if (xm->xm_mode & PERIPH_CAP_SYNC)
|
|
|
|
dflags |= DPARM_SYNC;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
ISP_LOCK(isp);
|
2001-04-25 21:53:04 +04:00
|
|
|
sdp->isp_devparam[xm->xm_target].dev_flags |= dflags;
|
|
|
|
dflags = sdp->isp_devparam[xm->xm_target].dev_flags;
|
|
|
|
sdp->isp_devparam[xm->xm_target].dev_update = 1;
|
|
|
|
isp->isp_update |= (1 << chan->chan_channel);
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
ISP_UNLOCK(isp);
|
2001-04-25 21:53:04 +04:00
|
|
|
isp_prt(isp, ISP_LOGDEBUG1,
|
|
|
|
"ispioctl: device flags 0x%x for %d.%d.X",
|
|
|
|
dflags, chan->chan_channel, xm->xm_target);
|
2000-07-06 02:23:05 +04:00
|
|
|
break;
|
2001-04-25 21:53:04 +04:00
|
|
|
}
|
|
|
|
default:
|
2000-07-06 02:23:05 +04:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2001-04-25 21:53:04 +04:00
|
|
|
static void
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
isp_polled_cmd(struct ispsoftc *isp, XS_T *xs)
|
2000-07-06 02:23:05 +04:00
|
|
|
{
|
|
|
|
int result;
|
|
|
|
int infinite = 0, mswait;
|
|
|
|
|
2000-08-02 03:55:09 +04:00
|
|
|
result = isp_start(xs);
|
2000-07-06 02:23:05 +04:00
|
|
|
|
1999-10-14 06:31:11 +04:00
|
|
|
switch (result) {
|
|
|
|
case CMD_QUEUED:
|
|
|
|
break;
|
|
|
|
case CMD_RQLATER:
|
|
|
|
if (XS_NOERR(xs)) {
|
2001-04-25 21:53:04 +04:00
|
|
|
xs->error = XS_REQUEUE;
|
1999-10-14 06:31:11 +04:00
|
|
|
}
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
case CMD_EAGAIN:
|
|
|
|
if (XS_NOERR(xs)) {
|
|
|
|
xs->error = XS_RESOURCE_SHORTAGE;
|
|
|
|
}
|
2001-04-25 21:53:04 +04:00
|
|
|
/* FALLTHROUGH */
|
1999-10-14 06:31:11 +04:00
|
|
|
case CMD_COMPLETE:
|
2001-04-25 21:53:04 +04:00
|
|
|
scsipi_done(xs);
|
|
|
|
return;
|
1999-10-14 06:31:11 +04:00
|
|
|
|
|
|
|
}
|
2000-07-06 02:23:05 +04:00
|
|
|
|
1998-07-15 23:44:04 +04:00
|
|
|
/*
|
|
|
|
* If we can't use interrupts, poll on completion.
|
|
|
|
*/
|
2000-07-06 02:23:05 +04:00
|
|
|
if ((mswait = XS_TIME(xs)) == 0)
|
|
|
|
infinite = 1;
|
|
|
|
|
|
|
|
while (mswait || infinite) {
|
|
|
|
if (isp_intr((void *)isp)) {
|
|
|
|
if (XS_CMD_DONE_P(xs)) {
|
|
|
|
break;
|
1998-07-15 23:44:04 +04:00
|
|
|
}
|
|
|
|
}
|
2000-08-02 03:55:09 +04:00
|
|
|
USEC_DELAY(1000);
|
2000-07-06 02:23:05 +04:00
|
|
|
mswait -= 1;
|
1998-07-15 23:44:04 +04:00
|
|
|
}
|
2000-07-06 02:23:05 +04:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If no other error occurred but we didn't finish,
|
|
|
|
* something bad happened.
|
|
|
|
*/
|
|
|
|
if (XS_CMD_DONE_P(xs) == 0) {
|
|
|
|
if (isp_control(isp, ISPCTL_ABORT_CMD, xs)) {
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_reinit(isp);
|
2000-07-06 02:23:05 +04:00
|
|
|
}
|
|
|
|
if (XS_NOERR(xs)) {
|
|
|
|
XS_SETERR(xs, HBA_BOTCH);
|
|
|
|
}
|
|
|
|
}
|
2001-04-25 21:53:04 +04:00
|
|
|
scsipi_done(xs);
|
1998-07-15 23:44:04 +04:00
|
|
|
}
|
|
|
|
|
2000-07-06 02:23:05 +04:00
|
|
|
void
|
2001-03-14 08:44:21 +03:00
|
|
|
isp_done(XS_T *xs)
|
1998-07-15 23:44:04 +04:00
|
|
|
{
|
2000-07-06 02:23:05 +04:00
|
|
|
XS_CMD_S_DONE(xs);
|
|
|
|
if (XS_CMD_WDOG_P(xs) == 0) {
|
|
|
|
struct ispsoftc *isp = XS_ISP(xs);
|
|
|
|
callout_stop(&xs->xs_callout);
|
|
|
|
if (XS_CMD_GRACE_P(xs)) {
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGDEBUG1,
|
|
|
|
"finished command on borrowed time");
|
1998-07-15 23:44:04 +04:00
|
|
|
}
|
2000-07-06 02:23:05 +04:00
|
|
|
XS_CMD_S_CLEAR(xs);
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
/*
|
|
|
|
* Fixup- if we get a QFULL, we need
|
|
|
|
* to set XS_BUSY as the error.
|
|
|
|
*/
|
|
|
|
if (xs->status == SCSI_QUEUE_FULL) {
|
|
|
|
xs->error = XS_BUSY;
|
|
|
|
}
|
|
|
|
if (isp->isp_osinfo.paused) {
|
|
|
|
isp->isp_osinfo.paused = 0;
|
|
|
|
scsipi_channel_timed_thaw(&isp->isp_chanA);
|
|
|
|
if (IS_DUALBUS(isp)) {
|
|
|
|
scsipi_channel_timed_thaw(&isp->isp_chanB);
|
|
|
|
}
|
|
|
|
}
|
2000-07-06 02:23:05 +04:00
|
|
|
scsipi_done(xs);
|
1998-07-15 23:44:04 +04:00
|
|
|
}
|
|
|
|
}
|
1998-12-28 22:10:43 +03:00
|
|
|
|
|
|
|
static void
|
2001-03-14 08:44:21 +03:00
|
|
|
isp_dog(void *arg)
|
1998-12-28 22:10:43 +03:00
|
|
|
{
|
2000-08-02 03:55:09 +04:00
|
|
|
XS_T *xs = arg;
|
2000-07-06 02:23:05 +04:00
|
|
|
struct ispsoftc *isp = XS_ISP(xs);
|
2001-03-14 08:44:21 +03:00
|
|
|
u_int16_t handle;
|
1998-12-28 22:10:43 +03:00
|
|
|
|
2000-08-14 11:08:12 +04:00
|
|
|
ISP_ILOCK(isp);
|
1998-12-28 22:10:43 +03:00
|
|
|
/*
|
2000-07-06 02:23:05 +04:00
|
|
|
* We've decided this command is dead. Make sure we're not trying
|
|
|
|
* to kill a command that's already dead by getting it's handle and
|
|
|
|
* and seeing whether it's still alive.
|
1998-12-28 22:10:43 +03:00
|
|
|
*/
|
2000-07-06 02:23:05 +04:00
|
|
|
handle = isp_find_handle(isp, xs);
|
|
|
|
if (handle) {
|
|
|
|
u_int16_t r, r1, i;
|
|
|
|
|
|
|
|
if (XS_CMD_DONE_P(xs)) {
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGDEBUG1,
|
|
|
|
"watchdog found done cmd (handle 0x%x)", handle);
|
2000-08-14 11:08:12 +04:00
|
|
|
ISP_IUNLOCK(isp);
|
2000-07-06 02:23:05 +04:00
|
|
|
return;
|
1998-12-28 22:10:43 +03:00
|
|
|
}
|
2000-07-06 02:23:05 +04:00
|
|
|
|
|
|
|
if (XS_CMD_WDOG_P(xs)) {
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGDEBUG1,
|
|
|
|
"recursive watchdog (handle 0x%x)", handle);
|
2000-08-14 11:08:12 +04:00
|
|
|
ISP_IUNLOCK(isp);
|
2000-07-06 02:23:05 +04:00
|
|
|
return;
|
1998-12-28 22:10:43 +03:00
|
|
|
}
|
2000-07-06 02:23:05 +04:00
|
|
|
|
|
|
|
XS_CMD_S_WDOG(xs);
|
|
|
|
|
|
|
|
i = 0;
|
|
|
|
do {
|
|
|
|
r = ISP_READ(isp, BIU_ISR);
|
2000-08-02 03:55:09 +04:00
|
|
|
USEC_DELAY(1);
|
2000-07-06 02:23:05 +04:00
|
|
|
r1 = ISP_READ(isp, BIU_ISR);
|
|
|
|
} while (r != r1 && ++i < 1000);
|
|
|
|
|
|
|
|
if (INT_PENDING(isp, r) && isp_intr(isp) && XS_CMD_DONE_P(xs)) {
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGDEBUG1, "watchdog cleanup (%x, %x)",
|
|
|
|
handle, r);
|
2000-07-06 02:23:05 +04:00
|
|
|
XS_CMD_C_WDOG(xs);
|
|
|
|
isp_done(xs);
|
|
|
|
} else if (XS_CMD_GRACE_P(xs)) {
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGDEBUG1, "watchdog timeout (%x, %x)",
|
|
|
|
handle, r);
|
2000-07-06 02:23:05 +04:00
|
|
|
/*
|
|
|
|
* Make sure the command is *really* dead before we
|
|
|
|
* release the handle (and DMA resources) for reuse.
|
|
|
|
*/
|
|
|
|
(void) isp_control(isp, ISPCTL_ABORT_CMD, arg);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* After this point, the comamnd is really dead.
|
|
|
|
*/
|
|
|
|
if (XS_XFRLEN(xs)) {
|
|
|
|
ISP_DMAFREE(isp, xs, handle);
|
|
|
|
}
|
|
|
|
isp_destroy_handle(isp, handle);
|
|
|
|
XS_SETERR(xs, XS_TIMEOUT);
|
|
|
|
XS_CMD_S_CLEAR(xs);
|
|
|
|
isp_done(xs);
|
|
|
|
} else {
|
|
|
|
u_int16_t iptr, optr;
|
|
|
|
ispreq_t *mp;
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGDEBUG2,
|
|
|
|
"possible command timeout (%x, %x)", handle, r);
|
2000-07-06 02:23:05 +04:00
|
|
|
XS_CMD_C_WDOG(xs);
|
|
|
|
callout_reset(&xs->xs_callout, hz, isp_dog, xs);
|
|
|
|
if (isp_getrqentry(isp, &iptr, &optr, (void **) &mp)) {
|
2000-12-09 11:06:31 +03:00
|
|
|
ISP_UNLOCK(isp);
|
2000-07-06 02:23:05 +04:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
XS_CMD_S_GRACE(xs);
|
|
|
|
MEMZERO((void *) mp, sizeof (*mp));
|
|
|
|
mp->req_header.rqs_entry_count = 1;
|
|
|
|
mp->req_header.rqs_entry_type = RQSTYPE_MARKER;
|
|
|
|
mp->req_modifier = SYNC_ALL;
|
|
|
|
mp->req_target = XS_CHANNEL(xs) << 7;
|
|
|
|
ISP_SWIZZLE_REQUEST(isp, mp);
|
|
|
|
ISP_ADD_REQUEST(isp, iptr);
|
1998-12-28 22:10:43 +03:00
|
|
|
}
|
2000-08-14 11:08:12 +04:00
|
|
|
} else {
|
|
|
|
isp_prt(isp, ISP_LOGDEBUG0, "watchdog with no command");
|
1998-12-28 22:10:43 +03:00
|
|
|
}
|
2000-08-14 11:08:12 +04:00
|
|
|
ISP_IUNLOCK(isp);
|
1998-12-28 22:10:43 +03:00
|
|
|
}
|
|
|
|
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
/*
|
|
|
|
* Fibre Channel state cleanup thread
|
|
|
|
*/
|
|
|
|
static void
|
|
|
|
isp_create_fc_worker(void *arg)
|
|
|
|
{
|
|
|
|
struct ispsoftc *isp = arg;
|
|
|
|
|
|
|
|
if (kthread_create1(isp_fc_worker, isp, &isp->isp_osinfo.thread,
|
|
|
|
"%s:fc_thrd", isp->isp_name)) {
|
|
|
|
isp_prt(isp, ISP_LOGERR, "unable to create FC worker thread");
|
|
|
|
panic("isp_create_fc_worker");
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
isp_fc_worker(void *arg)
|
|
|
|
{
|
|
|
|
void scsipi_run_queue(struct scsipi_channel *);
|
|
|
|
struct ispsoftc *isp = arg;
|
|
|
|
|
|
|
|
for (;;) {
|
|
|
|
int s;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Note we do *not* use the ISP_LOCK/ISP_UNLOCK macros here.
|
|
|
|
*/
|
|
|
|
s = splbio();
|
|
|
|
while (isp->isp_osinfo.threadwork) {
|
|
|
|
isp->isp_osinfo.threadwork = 0;
|
|
|
|
if (isp_fc_runstate(isp, 10 * 1000000) == 0) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
isp->isp_osinfo.threadwork = 1;
|
|
|
|
splx(s);
|
|
|
|
delay(500 * 1000);
|
|
|
|
s = splbio();
|
|
|
|
}
|
|
|
|
if (FCPARAM(isp)->isp_fwstate != FW_READY ||
|
|
|
|
FCPARAM(isp)->isp_loopstate != LOOP_READY) {
|
|
|
|
isp_prt(isp, ISP_LOGINFO, "isp_fc_runstate in vain");
|
|
|
|
isp->isp_osinfo.threadwork = 1;
|
|
|
|
splx(s);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (isp->isp_osinfo.blocked) {
|
|
|
|
isp->isp_osinfo.blocked = 0;
|
|
|
|
isp_prt(isp, /* ISP_LOGDEBUG0 */ ISP_LOGALL, "restarting queues (freeze count %d)", isp->isp_chanA.chan_qfreeze);
|
|
|
|
|
|
|
|
scsipi_channel_thaw(&isp->isp_chanA, 1);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (isp->isp_osinfo.thread == NULL)
|
|
|
|
break;
|
|
|
|
|
|
|
|
(void) tsleep(&isp->isp_osinfo.thread, PRIBIO, "fcclnup", 0);
|
|
|
|
|
|
|
|
splx(s);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* In case parent is waiting for us to exit. */
|
|
|
|
wakeup(&isp->isp_osinfo.thread);
|
|
|
|
|
|
|
|
kthread_exit(0);
|
|
|
|
}
|
|
|
|
|
1998-12-28 22:10:43 +03:00
|
|
|
/*
|
|
|
|
* Free any associated resources prior to decommissioning and
|
|
|
|
* set the card to a known state (so it doesn't wake up and kick
|
|
|
|
* us when we aren't expecting it to).
|
|
|
|
*
|
|
|
|
* Locks are held before coming here.
|
|
|
|
*/
|
|
|
|
void
|
2001-03-14 08:44:21 +03:00
|
|
|
isp_uninit(struct ispsoftc *isp)
|
1998-12-28 22:10:43 +03:00
|
|
|
{
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_lock(isp);
|
1998-12-28 22:10:43 +03:00
|
|
|
/*
|
|
|
|
* Leave with interrupts disabled.
|
|
|
|
*/
|
|
|
|
DISABLE_INTS(isp);
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_unlock(isp);
|
1998-12-28 22:10:43 +03:00
|
|
|
}
|
1999-01-30 10:31:50 +03:00
|
|
|
|
|
|
|
int
|
2001-03-14 08:44:21 +03:00
|
|
|
isp_async(struct ispsoftc *isp, ispasync_t cmd, void *arg)
|
1999-01-30 10:31:50 +03:00
|
|
|
{
|
1999-05-12 22:59:23 +04:00
|
|
|
int bus, tgt;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
|
1999-01-30 10:31:50 +03:00
|
|
|
switch (cmd) {
|
|
|
|
case ISPASYNC_NEW_TGT_PARAMS:
|
1999-10-14 06:31:11 +04:00
|
|
|
if (IS_SCSI(isp) && isp->isp_dblev) {
|
|
|
|
sdparam *sdp = isp->isp_param;
|
2001-04-25 21:53:04 +04:00
|
|
|
int flags;
|
|
|
|
struct scsipi_xfer_mode xm;
|
1999-10-14 06:31:11 +04:00
|
|
|
|
|
|
|
tgt = *((int *) arg);
|
|
|
|
bus = (tgt >> 16) & 0xffff;
|
|
|
|
tgt &= 0xffff;
|
1999-12-16 08:35:42 +03:00
|
|
|
sdp += bus;
|
1999-10-14 06:31:11 +04:00
|
|
|
flags = sdp->isp_devparam[tgt].cur_dflags;
|
1999-12-16 08:35:42 +03:00
|
|
|
|
2001-04-25 21:53:04 +04:00
|
|
|
xm.xm_mode = 0;
|
|
|
|
xm.xm_period = sdp->isp_devparam[tgt].cur_period;
|
|
|
|
xm.xm_offset = sdp->isp_devparam[tgt].cur_offset;
|
|
|
|
xm.xm_target = tgt;
|
|
|
|
|
|
|
|
if ((flags & DPARM_SYNC) && xm.xm_period && xm.xm_offset)
|
|
|
|
xm.xm_mode |= PERIPH_CAP_SYNC;
|
|
|
|
if (flags & DPARM_WIDE)
|
|
|
|
xm.xm_mode |= PERIPH_CAP_WIDE16;
|
|
|
|
if (flags & DPARM_TQING)
|
|
|
|
xm.xm_mode |= PERIPH_CAP_TQING;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
scsipi_async_event(bus? &isp->isp_chanB : &isp->isp_chanA,
|
|
|
|
ASYNC_EVENT_XFER_MODE, &xm);
|
1999-01-30 10:31:50 +03:00
|
|
|
break;
|
1999-10-14 06:31:11 +04:00
|
|
|
}
|
1999-03-17 09:15:47 +03:00
|
|
|
case ISPASYNC_BUS_RESET:
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
bus = *((int *) arg);
|
|
|
|
scsipi_async_event(bus? &isp->isp_chanB : &isp->isp_chanA,
|
|
|
|
ASYNC_EVENT_RESET, NULL);
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGINFO, "SCSI bus %d reset detected", bus);
|
1999-03-17 09:15:47 +03:00
|
|
|
break;
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
case ISPASYNC_LIP:
|
|
|
|
/*
|
|
|
|
* Don't do queue freezes or blockage until we have the
|
|
|
|
* thread running that can unfreeze/unblock us.
|
|
|
|
*/
|
|
|
|
if (isp->isp_osinfo.blocked == 0) {
|
|
|
|
if (isp->isp_osinfo.thread) {
|
|
|
|
isp->isp_osinfo.blocked = 1;
|
|
|
|
scsipi_channel_freeze(&isp->isp_chanA, 1);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
isp_prt(isp, ISP_LOGINFO, "LIP Received");
|
|
|
|
break;
|
|
|
|
case ISPASYNC_LOOP_RESET:
|
|
|
|
/*
|
|
|
|
* Don't do queue freezes or blockage until we have the
|
|
|
|
* thread running that can unfreeze/unblock us.
|
|
|
|
*/
|
|
|
|
if (isp->isp_osinfo.blocked == 0) {
|
|
|
|
if (isp->isp_osinfo.thread) {
|
|
|
|
isp->isp_osinfo.blocked = 1;
|
|
|
|
scsipi_channel_freeze(&isp->isp_chanA, 1);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
isp_prt(isp, ISP_LOGINFO, "Loop Reset Received");
|
|
|
|
break;
|
1999-03-17 09:15:47 +03:00
|
|
|
case ISPASYNC_LOOP_DOWN:
|
|
|
|
/*
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
* Don't do queue freezes or blockage until we have the
|
|
|
|
* thread running that can unfreeze/unblock us.
|
1999-03-17 09:15:47 +03:00
|
|
|
*/
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
if (isp->isp_osinfo.blocked == 0) {
|
|
|
|
if (isp->isp_osinfo.thread) {
|
|
|
|
isp->isp_osinfo.blocked = 1;
|
|
|
|
scsipi_channel_freeze(&isp->isp_chanA, 1);
|
|
|
|
}
|
|
|
|
}
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGINFO, "Loop DOWN");
|
1999-03-17 09:15:47 +03:00
|
|
|
break;
|
|
|
|
case ISPASYNC_LOOP_UP:
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
/*
|
|
|
|
* Let the subsequent ISPASYNC_CHANGE_NOTIFY invoke
|
|
|
|
* the FC worker thread. When the FC worker thread
|
|
|
|
* is done, let *it* call scsipi_channel_thaw...
|
|
|
|
*/
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGINFO, "Loop UP");
|
1999-03-17 09:15:47 +03:00
|
|
|
break;
|
2001-02-13 02:30:12 +03:00
|
|
|
case ISPASYNC_PROMENADE:
|
1999-10-14 06:31:11 +04:00
|
|
|
if (IS_FC(isp) && isp->isp_dblev) {
|
2000-12-29 01:27:46 +03:00
|
|
|
const char fmt[] = "Target %d (Loop 0x%x) Port ID 0x%x "
|
2001-02-13 02:30:12 +03:00
|
|
|
"(role %s) %s\n Port WWN 0x%08x%08x\n Node WWN 0x%08x%08x";
|
1999-07-06 00:31:35 +04:00
|
|
|
const static char *roles[4] = {
|
2001-05-16 07:52:10 +04:00
|
|
|
"None", "Target", "Initiator", "Target/Initiator"
|
1999-03-17 09:15:47 +03:00
|
|
|
};
|
1999-07-06 00:31:35 +04:00
|
|
|
fcparam *fcp = isp->isp_param;
|
|
|
|
int tgt = *((int *) arg);
|
|
|
|
struct lportdb *lp = &fcp->portdb[tgt];
|
|
|
|
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGINFO, fmt, tgt, lp->loopid, lp->portid,
|
2001-02-13 02:30:12 +03:00
|
|
|
roles[lp->roles & 0x3],
|
|
|
|
(lp->valid)? "Arrived" : "Departed",
|
1999-07-06 00:31:35 +04:00
|
|
|
(u_int32_t) (lp->port_wwn >> 32),
|
|
|
|
(u_int32_t) (lp->port_wwn & 0xffffffffLL),
|
|
|
|
(u_int32_t) (lp->node_wwn >> 32),
|
|
|
|
(u_int32_t) (lp->node_wwn & 0xffffffffLL));
|
1999-03-17 09:15:47 +03:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
case ISPASYNC_CHANGE_NOTIFY:
|
2001-05-16 07:52:10 +04:00
|
|
|
if (arg == ISPASYNC_CHANGE_PDB) {
|
|
|
|
isp_prt(isp, ISP_LOGINFO, "Port Database Changed");
|
|
|
|
} else if (arg == ISPASYNC_CHANGE_SNS) {
|
2001-01-09 21:54:53 +03:00
|
|
|
isp_prt(isp, ISP_LOGINFO,
|
|
|
|
"Name Server Database Changed");
|
|
|
|
}
|
Create a kernel thread for Fibre Channel cards. This is the new
way of doing business- modulo some startup spasms and peculiarities
of the way kthreads are started (*after* configuration, weird) and
some strangeness with the freeze/thaw code, what now happens is
that any of Loop Down, LIP, Loop Reset or Port Datbase or Name
Server Database Changed ASYNC events cause the queues to freeze
for this channel. The arrival of a Loop UP is not relevant.
What *is* relevant is that the Port Datbase or Name Server Changed
async event indicate that it's okay to go and (re)evaluate the
state of the FC link and (re)probe local loop and fabric membership.
We have a kthread do this because it's *sooooo* much nicer to be
able to sleep while doing the 130-250 mailbox commands it'll take
to re-evaluate things.
When the state is well known again, we can unfreeze the channel
queues. Then, as commands start arriving, we simply can start them
or bounce them with XS_SELTIMEOUT (if the device in question has
gone away). Previously, we did lazy evaluation, which meant that
if a change occurred, we would wait until the very *next* command
to go rebuild stuff.
The reason this is not sensible is:
a) Even with sleeping, you can hang up your system because you might be
making some poor stat(2) call pay the price of re-evaluating the whole
fabric.
b) If we ever really want to get to dynamic attachment/detachment, we
should find out sooner, rather than later, where things get to.
Split off ispminphys_1020 from ispminphys- a 1020 has a 24 bit limit-
not anything newer.
Re-enable LIPs and Loop Resets as async events- this allows the outer
layer to set policy about them.
Roll platform major && minor. Remove bogus waitq (no longer used).
Remove callout entry in softc (no longer used). Define some shorthands
for channels. Clean up a variety of cruft left over from the
thorpej_scsipi changeover.
2001-05-26 01:45:55 +04:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We can set blocked here because we know it's now okay
|
|
|
|
* to try and run isp_fc_runstate (in order to build loop
|
|
|
|
* state). But we don't try and freeze the midlayer's queue
|
|
|
|
* if we have no thread that we can wake to later unfreeze
|
|
|
|
* it.
|
|
|
|
*/
|
|
|
|
if (isp->isp_osinfo.blocked == 0) {
|
|
|
|
isp->isp_osinfo.blocked = 1;
|
|
|
|
if (isp->isp_osinfo.thread) {
|
|
|
|
scsipi_channel_freeze(&isp->isp_chanA, 1);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
* Note that we have work for the thread to do, and
|
|
|
|
* if the thread is here already, wake it up.
|
|
|
|
*/
|
|
|
|
isp->isp_osinfo.threadwork++;
|
|
|
|
if (isp->isp_osinfo.thread) {
|
|
|
|
wakeup(&isp->isp_osinfo.thread);
|
|
|
|
} else {
|
|
|
|
isp_prt(isp, ISP_LOGDEBUG1, "no FC thread yet");
|
|
|
|
}
|
1999-03-17 09:15:47 +03:00
|
|
|
break;
|
1999-07-06 00:31:35 +04:00
|
|
|
case ISPASYNC_FABRIC_DEV:
|
|
|
|
{
|
2001-02-13 02:30:12 +03:00
|
|
|
int target, lrange;
|
|
|
|
struct lportdb *lp = NULL;
|
|
|
|
char *pt;
|
|
|
|
sns_ganrsp_t *resp = (sns_ganrsp_t *) arg;
|
1999-07-06 00:31:35 +04:00
|
|
|
u_int32_t portid;
|
2001-02-13 02:30:12 +03:00
|
|
|
u_int64_t wwpn, wwnn;
|
1999-07-06 00:31:35 +04:00
|
|
|
fcparam *fcp = isp->isp_param;
|
|
|
|
|
|
|
|
portid =
|
|
|
|
(((u_int32_t) resp->snscb_port_id[0]) << 16) |
|
|
|
|
(((u_int32_t) resp->snscb_port_id[1]) << 8) |
|
|
|
|
(((u_int32_t) resp->snscb_port_id[2]));
|
2001-02-13 02:30:12 +03:00
|
|
|
|
|
|
|
wwpn =
|
1999-07-06 00:31:35 +04:00
|
|
|
(((u_int64_t)resp->snscb_portname[0]) << 56) |
|
|
|
|
(((u_int64_t)resp->snscb_portname[1]) << 48) |
|
|
|
|
(((u_int64_t)resp->snscb_portname[2]) << 40) |
|
|
|
|
(((u_int64_t)resp->snscb_portname[3]) << 32) |
|
|
|
|
(((u_int64_t)resp->snscb_portname[4]) << 24) |
|
|
|
|
(((u_int64_t)resp->snscb_portname[5]) << 16) |
|
|
|
|
(((u_int64_t)resp->snscb_portname[6]) << 8) |
|
|
|
|
(((u_int64_t)resp->snscb_portname[7]));
|
2000-10-16 09:15:55 +04:00
|
|
|
|
2001-02-13 02:30:12 +03:00
|
|
|
wwnn =
|
|
|
|
(((u_int64_t)resp->snscb_nodename[0]) << 56) |
|
|
|
|
(((u_int64_t)resp->snscb_nodename[1]) << 48) |
|
|
|
|
(((u_int64_t)resp->snscb_nodename[2]) << 40) |
|
|
|
|
(((u_int64_t)resp->snscb_nodename[3]) << 32) |
|
|
|
|
(((u_int64_t)resp->snscb_nodename[4]) << 24) |
|
|
|
|
(((u_int64_t)resp->snscb_nodename[5]) << 16) |
|
|
|
|
(((u_int64_t)resp->snscb_nodename[6]) << 8) |
|
|
|
|
(((u_int64_t)resp->snscb_nodename[7]));
|
|
|
|
if (portid == 0 || wwpn == 0) {
|
|
|
|
break;
|
|
|
|
}
|
2000-10-16 09:15:55 +04:00
|
|
|
|
2001-02-13 02:30:12 +03:00
|
|
|
switch (resp->snscb_port_type) {
|
|
|
|
case 1:
|
|
|
|
pt = " N_Port";
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
pt = " NL_Port";
|
|
|
|
break;
|
|
|
|
case 3:
|
|
|
|
pt = "F/NL_Port";
|
|
|
|
break;
|
|
|
|
case 0x7f:
|
|
|
|
pt = " Nx_Port";
|
|
|
|
break;
|
|
|
|
case 0x81:
|
|
|
|
pt = " F_port";
|
|
|
|
break;
|
|
|
|
case 0x82:
|
|
|
|
pt = " FL_Port";
|
|
|
|
break;
|
|
|
|
case 0x84:
|
|
|
|
pt = " E_port";
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
pt = "?";
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
isp_prt(isp, ISP_LOGINFO,
|
|
|
|
"%s @ 0x%x, Node 0x%08x%08x Port %08x%08x",
|
|
|
|
pt, portid, ((u_int32_t) (wwnn >> 32)), ((u_int32_t) wwnn),
|
|
|
|
((u_int32_t) (wwpn >> 32)), ((u_int32_t) wwpn));
|
|
|
|
/*
|
|
|
|
* We're only interested in SCSI_FCP types (for now)
|
|
|
|
*/
|
|
|
|
if ((resp->snscb_fc4_types[2] & 1) == 0) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
if (fcp->isp_topo != TOPO_F_PORT)
|
|
|
|
lrange = FC_SNS_ID+1;
|
|
|
|
else
|
|
|
|
lrange = 0;
|
|
|
|
/*
|
|
|
|
* Is it already in our list?
|
|
|
|
*/
|
|
|
|
for (target = lrange; target < MAX_FC_TARG; target++) {
|
|
|
|
if (target >= FL_PORT_ID && target <= FC_SNS_ID) {
|
|
|
|
continue;
|
|
|
|
}
|
1999-07-06 00:31:35 +04:00
|
|
|
lp = &fcp->portdb[target];
|
2001-02-13 02:30:12 +03:00
|
|
|
if (lp->port_wwn == wwpn && lp->node_wwn == wwnn) {
|
|
|
|
lp->fabric_dev = 1;
|
1999-07-06 00:31:35 +04:00
|
|
|
break;
|
2001-02-13 02:30:12 +03:00
|
|
|
}
|
1999-07-06 00:31:35 +04:00
|
|
|
}
|
|
|
|
if (target < MAX_FC_TARG) {
|
|
|
|
break;
|
|
|
|
}
|
2001-02-13 02:30:12 +03:00
|
|
|
for (target = lrange; target < MAX_FC_TARG; target++) {
|
|
|
|
if (target >= FL_PORT_ID && target <= FC_SNS_ID) {
|
|
|
|
continue;
|
|
|
|
}
|
1999-07-06 00:31:35 +04:00
|
|
|
lp = &fcp->portdb[target];
|
2001-02-13 02:30:12 +03:00
|
|
|
if (lp->port_wwn == 0) {
|
1999-07-06 00:31:35 +04:00
|
|
|
break;
|
2001-02-13 02:30:12 +03:00
|
|
|
}
|
1999-07-06 00:31:35 +04:00
|
|
|
}
|
|
|
|
if (target == MAX_FC_TARG) {
|
2000-08-02 03:55:09 +04:00
|
|
|
isp_prt(isp, ISP_LOGWARN,
|
|
|
|
"no more space for fabric devices");
|
2001-02-13 02:30:12 +03:00
|
|
|
break;
|
1999-07-06 00:31:35 +04:00
|
|
|
}
|
2001-02-13 02:30:12 +03:00
|
|
|
lp->node_wwn = wwnn;
|
|
|
|
lp->port_wwn = wwpn;
|
1999-07-06 00:31:35 +04:00
|
|
|
lp->portid = portid;
|
2001-02-13 02:30:12 +03:00
|
|
|
lp->fabric_dev = 1;
|
1999-07-06 00:31:35 +04:00
|
|
|
break;
|
|
|
|
}
|
1999-01-30 10:31:50 +03:00
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
return (0);
|
|
|
|
}
|
2000-08-02 03:55:09 +04:00
|
|
|
|
|
|
|
#include <machine/stdarg.h>
|
|
|
|
void
|
|
|
|
isp_prt(struct ispsoftc *isp, int level, const char *fmt, ...)
|
|
|
|
{
|
|
|
|
va_list ap;
|
|
|
|
if (level != ISP_LOGALL && (level & isp->isp_dblev) == 0) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
printf("%s: ", isp->isp_name);
|
|
|
|
va_start(ap, fmt);
|
|
|
|
vprintf(fmt, ap);
|
|
|
|
va_end(ap);
|
|
|
|
printf("\n");
|
|
|
|
}
|