From: Haren Myneni <haren@linux.vnet.ibm.com>
To: Stewart Smith <stewart@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto/nx: Initialize 842 high and normal RxFIFO control registers
Date: Thu, 31 May 2018 23:30:32 -0700 [thread overview]
Message-ID: <5B10E808.3030502@linux.vnet.ibm.com> (raw)
In-Reply-To: <87sh672mf7.fsf@linux.vnet.ibm.com>
On 05/31/2018 08:52 PM, Stewart Smith wrote:
> Haren Myneni <haren@linux.vnet.ibm.com> writes:
>> NX increments readOffset by FIFO size in receive FIFO control register
>> when CRB is read. But the index in RxFIFO has to match with the
>> corresponding entry in FIFO maintained by VAS in kernel. Otherwise NX
>> may be processing incorrect CRBs and can cause CRB timeout.
>>
>> VAS FIFO offset is 0 when the receive window is opened during
>> initialization. When the module is reloaded or in kexec boot, readOffset
>> in FIFO control register may not match with VAS entry. This patch adds
>> nx_coproc_init OPAL call to reset readOffset and queued entries in FIFO
>> control register for both high and normal FIFOs.
>>
>> Signed-off-by: Haren Myneni <haren@us.ibm.com>
>
> I've yet to go and check out the skiboot patch properly, but should this
> be both:
> Fixes: b0d6c9bab crypto/nx: Add P9 NX support for 842 compression engine
> CC: stable # v4.14+
>
> as otherwise "rmmod ; insmod" will crash, and possibly even issues over kexec?
>
Correct, P9 NX support is included in 4.14. We also need fix in stable trees (4.14+). But this patch will not apply cleanly. I will post different patch for 4.14 and 4.16 stable trees.
Thanks
Haren
WARNING: multiple messages have this Message-ID (diff)
From: Haren Myneni <haren@linux.vnet.ibm.com>
To: Stewart Smith <stewart@linux.ibm.com>
Cc: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto/nx: Initialize 842 high and normal RxFIFO control registers
Date: Thu, 31 May 2018 23:30:32 -0700 [thread overview]
Message-ID: <5B10E808.3030502@linux.vnet.ibm.com> (raw)
In-Reply-To: <87sh672mf7.fsf@linux.vnet.ibm.com>
On 05/31/2018 08:52 PM, Stewart Smith wrote:
> Haren Myneni <haren@linux.vnet.ibm.com> writes:
>> NX increments readOffset by FIFO size in receive FIFO control register
>> when CRB is read. But the index in RxFIFO has to match with the
>> corresponding entry in FIFO maintained by VAS in kernel. Otherwise NX
>> may be processing incorrect CRBs and can cause CRB timeout.
>>
>> VAS FIFO offset is 0 when the receive window is opened during
>> initialization. When the module is reloaded or in kexec boot, readOffset
>> in FIFO control register may not match with VAS entry. This patch adds
>> nx_coproc_init OPAL call to reset readOffset and queued entries in FIFO
>> control register for both high and normal FIFOs.
>>
>> Signed-off-by: Haren Myneni <haren@us.ibm.com>
>
> I've yet to go and check out the skiboot patch properly, but should this
> be both:
> Fixes: b0d6c9bab crypto/nx: Add P9 NX support for 842 compression engine
> CC: stable # v4.14+
>
> as otherwise "rmmod ; insmod" will crash, and possibly even issues over kexec?
>
Correct, P9 NX support is included in 4.14. We also need fix in stable trees (4.14+). But this patch will not apply cleanly. I will post different patch for 4.14 and 4.16 stable trees.
Thanks
Haren
next prev parent reply other threads:[~2018-06-01 6:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 17:54 [PATCH] crypto/nx: Initialize 842 high and normal RxFIFO control registers Haren Myneni
2018-05-31 17:54 ` Haren Myneni
2018-06-01 3:52 ` Stewart Smith
2018-06-01 6:30 ` Haren Myneni [this message]
2018-06-01 6:30 ` Haren Myneni
2018-06-01 7:41 ` Stewart Smith
2018-06-01 16:50 ` Haren Myneni
2018-06-01 16:50 ` Haren Myneni
2018-06-04 0:41 ` Stewart Smith
2018-06-04 0:41 ` Stewart Smith
2018-06-04 2:44 ` Haren Myneni
2018-06-04 2:44 ` Haren Myneni
2018-06-04 4:08 ` Stewart Smith
2018-06-04 4:08 ` Stewart Smith
2018-06-04 4:52 ` Haren Myneni
2018-06-04 4:59 ` Oliver
2018-06-04 4:59 ` Oliver
-- strict thread matches above, loose matches on Subject: below --
2018-04-21 11:19 Haren Myneni
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=5B10E808.3030502@linux.vnet.ibm.com \
--to=haren@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stewart@linux.ibm.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.