From: Roman Bolshakov <r.bolshakov@yadro.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
<linux-scsi@vger.kernel.org>, Quinn Tran <qutran@marvell.com>,
Himanshu Madhani <hmadhani@marvell.com>
Subject: Re: [PATCH] Revert "qla2xxx: Fix Nport ID display value"
Date: Wed, 4 Dec 2019 15:07:15 +0300 [thread overview]
Message-ID: <20191204120715.dgpr6xcdcckkae4q@SPB-NB-133.local> (raw)
In-Reply-To: <10e0c0c1-f3ad-7233-995d-59f1b748e39f@acm.org>
On Mon, Dec 02, 2019 at 06:34:43PM -0800, Bart Van Assche wrote:
> On 2019-12-02 12:55, Roman Bolshakov wrote:
> > On Mon, Dec 02, 2019 at 08:40:17AM -0800, Bart Van Assche wrote:
> >> diff --git a/drivers/scsi/qla2xxx/qla_iocb.c b/drivers/scsi/qla2xxx/qla_iocb.c
> >> index b25f87ff8cde..e2e91b3f2e65 100644
> >> --- a/drivers/scsi/qla2xxx/qla_iocb.c
> >> +++ b/drivers/scsi/qla2xxx/qla_iocb.c
> >> @@ -2656,10 +2656,16 @@ qla24xx_els_logo_iocb(srb_t *sp, struct els_entry_24xx *els_iocb)
> >> els_iocb->port_id[0] = sp->fcport->d_id.b.al_pa;
> >> els_iocb->port_id[1] = sp->fcport->d_id.b.area;
> >> els_iocb->port_id[2] = sp->fcport->d_id.b.domain;
> >> - /* For SID the byte order is different than DID */
> >> - els_iocb->s_id[1] = vha->d_id.b.al_pa;
> >> - els_iocb->s_id[2] = vha->d_id.b.area;
> >> - els_iocb->s_id[0] = vha->d_id.b.domain;
> >> + if (IS_QLA23XX(vha->hw) || IS_QLA24XX(vha->hw) || IS_QLA25XX(vha->hw)) {
> >> + els_iocb->s_id[0] = vha->d_id.b.al_pa;
> >> + els_iocb->s_id[1] = vha->d_id.b.area;
> >> + els_iocb->s_id[2] = vha->d_id.b.domain;
> >> + } else {
> >> + /* For SID the byte order is different than DID */
> >> + els_iocb->s_id[1] = vha->d_id.b.al_pa;
> >> + els_iocb->s_id[2] = vha->d_id.b.area;
> >> + els_iocb->s_id[0] = vha->d_id.b.domain;
> >> + }
> >>
> >> if (elsio->u.els_logo.els_cmd == ELS_DCMD_PLOGI) {
> >> els_iocb->control_flags = 0;
> >
> > Hi Bart,
> >
> > I'm fine as long as it works for old and new HBAs. I don't have docs to
> > 2300/2400 series and the HBAs. Are you sure it follows the same S_ID
> > order as 2500?
> >
> > Regardless of that, it should work for the last 4 series of the HBAs,
> > Reviewed-by: Roman Bolshakov <r.bolshakov@yadro.com>
>
> Hi Roman,
>
> Thanks for the review. In my copy of the 25xx firmware manual the s_id[]
> field has been marked as RESERVED. I have tried not to write into s_id[]
> but that was not sufficient to restore point-to-point mode.
>
Hi Bart,
IMO that means the field is undocumented rather than RESERVED on 2500
series chips.
> Older versions of the qla2xxx driver did not initialize s_id[]. I think
> that commit edd05de19759 ("scsi: qla2xxx: Changes to support N2N
> logins") is the commit that introduced initialization of s_id[]. Is that
> value passed to the target port? Did that commit perhaps introduce code
> that checks the value received by the target?
>
Firmware can do implicit login, and this is how it worked for a while.
Then explicit login was introduced in the commit you referenced by
setting bit 8 in IFCB fimwrare options 3 for 2600/2700 series and
issuing ELS IOCB. However, for 2500 series, bit 7 should be set to
disable implicit logins.
The latest commits that touches the bit is 8777e4314d397 ("scsi: qla2xxx:
Migrate NVME N2N handling into state machine"). It sets the bit in
qla24xx_nvram_config regadless of chip.
Does it help to set bit 7 in IFCB, firmware options 3 for 2500 series
and leave the RESERVED S_ID field untouched?
Thanks,
Roman
next prev parent reply other threads:[~2019-12-04 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 4:21 [PATCH] Revert "qla2xxx: Fix Nport ID display value" Bart Van Assche
2019-11-11 11:28 ` Roman Bolshakov
2019-11-12 2:48 ` Bart Van Assche
2019-11-13 15:29 ` Himanshu Madhani
2019-11-14 2:34 ` Bart Van Assche
2019-11-20 0:15 ` Bart Van Assche
2019-11-20 21:39 ` Himanshu Madhani
2019-11-21 3:26 ` Bart Van Assche
2019-12-02 16:40 ` Bart Van Assche
2019-12-02 20:55 ` Roman Bolshakov
2019-12-03 2:34 ` Bart Van Assche
2019-12-04 12:07 ` Roman Bolshakov [this message]
2019-12-06 6:03 ` Bart Van Assche
2019-12-09 23:18 ` Martin K. Petersen
2019-12-10 19:38 ` [EXT] " Himanshu Madhani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191204120715.dgpr6xcdcckkae4q@SPB-NB-133.local \
--to=r.bolshakov@yadro.com \
--cc=bvanassche@acm.org \
--cc=hmadhani@marvell.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qutran@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox