From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Chris Smart <chris.smart@humanservices.gov.au>,
<linuxppc-dev@lists.ozlabs.org>
Cc: distroguy@gmail.com, Chris Smart <chris.smart@humanservices.gov.au>
Subject: Re: [PATCH 1/1] powerpc/crypto: Add cond_resched() in crc-vpmsum self-test
Date: Thu, 14 Nov 2019 20:08:17 +1100 (AEDT) [thread overview]
Message-ID: <47DFyC0KRXz9sSW@ozlabs.org> (raw)
In-Reply-To: <20191103233356.5472-1-chris.smart@humanservices.gov.au>
On Sun, 2019-11-03 at 23:33:56 UTC, Chris Smart wrote:
> The stress test for vpmsum implementations executes a long for loop in
> the kernel. This blocks the scheduler, which prevents other tasks from
> running, resulting in a warning.
>
> This fix adds a call to cond_reshed() at the end of each loop, which
> allows the scheduler to run other tasks as required.
>
> Signed-off-by: Chris Smart <chris.smart@humanservices.gov.au>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9f0acf9f80ad504573e6482fb00b53866a9b9d2f
cheers
prev parent reply other threads:[~2019-11-14 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 23:33 [PATCH 1/1] powerpc/crypto: Add cond_resched() in crc-vpmsum self-test Chris Smart
2019-11-14 9:08 ` Michael Ellerman [this message]
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=47DFyC0KRXz9sSW@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=chris.smart@humanservices.gov.au \
--cc=distroguy@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).