From: John Garry <john.garry@huawei.com>
To: <Ajish.Koshy@microchip.com>, <damien.lemoal@opensource.wdc.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<jinpu.wang@cloud.ionos.com>, <Viswas.G@microchip.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vishakhavc@google.com>, <ipylypiv@google.com>,
<Ruksar.devadi@microchip.com>,
<Vasanthalakshmi.Tharmarajan@microchip.com>
Subject: Re: [PATCH RFT] scsi: pm8001: Fix FW crash for maxcpus=1
Date: Thu, 6 Jan 2022 15:32:52 +0000 [thread overview]
Message-ID: <c19c2b0b-d502-b393-db8a-cb5c57c00feb@huawei.com> (raw)
In-Reply-To: <PH0PR11MB5112F9E9BB9F029DB9A67739EC4C9@PH0PR11MB5112.namprd11.prod.outlook.com>
On 06/01/2022 13:03, Ajish.Koshy@microchip.com wrote:
>> only a specific vector and, also, why we check at all in
>> an interrupt handler.
> Here is my initial understanding so far based on the code
> and data sheet
>
> 1. Controller has the capability to communicate
> to the host about fatal error condition via configured
> interrupt vector MSI/MSI-X.
> 2. This capability is achieved by setting two fields
> a. Enable Controller Fatal error notification
> Dowrd 0x1C, Bit[0].
> 1 - Enable; 0 - Disable
> Code: pm8001_ha->main_cfg_tbl.pm80xx_tbl.
> fatal_err_interrupt = 0x01;
> b. Fatal Error Interrupt Vector Dword 0x1C, bit[15:8]
> This parameter configures which interrupt vector
> is used to notify the host of the fatal error.
> Code: /* Update Fatal error interrupt vector */
> pm8001_ha->main_cfg_tbl.pm80xx_tbl.
> fatal_err_interrupt |=
> ((pm8001_ha->max_q_num - 1) << 8);
>
> Probably this will be the reason why we check
> the vector in process_oq() for processing
> controller fatal error
>
> if (vec == (pm8001_ha->max_q_num - 1)) {
>
> Please do let me know if it helped in clarification.
>
Sounds reasonable. And we only discover the issue for 8008/8009 now as
we have that (pm8001_ha->max_q_num - 1) vector being used for standard IO.
So let me know of any other issue, otherwise I'll send a v2 with the
coding style fixup.
Thanks,
John
next prev parent reply other threads:[~2022-01-06 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 18:26 [PATCH RFT] scsi: pm8001: Fix FW crash for maxcpus=1 John Garry
2022-01-05 4:03 ` Damien Le Moal
2022-01-05 11:28 ` John Garry
2022-01-06 13:03 ` Ajish.Koshy
2022-01-06 15:32 ` John Garry [this message]
2022-01-06 23:59 ` Damien Le Moal
2022-01-07 11:05 ` Ajish.Koshy
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=c19c2b0b-d502-b393-db8a-cb5c57c00feb@huawei.com \
--to=john.garry@huawei.com \
--cc=Ajish.Koshy@microchip.com \
--cc=Ruksar.devadi@microchip.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ipylypiv@google.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vishakhavc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.