From: Daniel Axtens <dja@axtens.net>
To: Haren Myneni <haren@linux.vnet.ibm.com>,
herbert@gondor.apana.org.au, davem@davemloft.net,
ddstreet@ieee.org, mpe@ellerman.id.au, pair@us.ibm.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: crypto/nx842: Ignore queue overflow informative error
Date: Mon, 07 Dec 2015 09:57:14 +1100 [thread overview]
Message-ID: <87bna36v91.fsf@gamma.ozlabs.ibm.com> (raw)
In-Reply-To: <1449388004.2096.12.camel@hbabu-laptop>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
Haren Myneni <haren@linux.vnet.ibm.com> writes:
> NX842 coprocessor sets bit 3 if queue is overflow. It is just for
> information to the user. So the driver prints this informative message
> and ignores it.
What queue, and what happens when the queue overflows? It seems like
*something* would need to be done, somewhere, by someone?
I realise that as a piece of IBM hardware this is probably an incredibly
optimistic question, but is this behaviour documented publically anywhere?
(As a distant second best, is it documented internally anywhere that I
can read?)
> --- a/drivers/crypto/nx/nx-842-powernv.c
> +++ b/drivers/crypto/nx/nx-842-powernv.c
> @@ -442,6 +442,15 @@ static int nx842_powernv_function(const unsigned char *in, unsigned int inlen,
> (unsigned int)ccw,
> (unsigned int)be32_to_cpu(crb->ccw));
>
> + /*
> + * NX842 coprocessor uses 3rd bit to report queue overflow which is
> + * not an error, just for information to user. So, ignore this bit.
> + */
> + if (ret & ICSWX_BIT3) {
> + pr_info_ratelimited("842 coprocessor queue overflow\n");
It doesn't look like this is done anywhere else in the file, but should
this be prefixed with something? Something like "nx-842: Coprocessor
queue overflow"?
Regards,
Daniel
> + ret &= ~ICSWX_BIT3;
> + }
> +
> switch (ret) {
> case ICSWX_INITIATED:
> ret = wait_for_csb(wmem, csb);
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 859 bytes --]
next prev parent reply other threads:[~2015-12-06 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 7:46 crypto/nx842: Ignore queue overflow informative error Haren Myneni
2015-12-06 7:46 ` Haren Myneni
2015-12-06 22:57 ` Daniel Axtens [this message]
2015-12-07 19:39 ` Dan Streetman
2015-12-07 19:34 ` Dan Streetman
2015-12-12 2:02 ` 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=87bna36v91.fsf@gamma.ozlabs.ibm.com \
--to=dja@axtens.net \
--cc=davem@davemloft.net \
--cc=ddstreet@ieee.org \
--cc=haren@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=pair@us.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.