From: Raphael Moreira Zinsly <rzinsly@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org,
dja@axtens.net
Cc: rzinsly@linux.ibm.com, herbert@gondor.apana.org.au,
mpe@ellerman.id.au, haren@linux.ibm.com, abali@us.ibm.com
Subject: [PATCH V3 0/5] selftests/powerpc: Add NX-GZIP engine testcase
Date: Mon, 13 Apr 2020 12:59:11 -0300 [thread overview]
Message-ID: <20200413155916.16900-1-rzinsly@linux.ibm.com> (raw)
This patch series are intended to test the POWER9 Nest
Accelerator (NX) GZIP engine that is being introduced by
https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-March/205659.html
More information about how to access the NX can be found in that patch, also a
complete userspace library and more documentation can be found at:
https://github.com/libnxz/power-gzip
Changes in V3:
- Defined a macro and increased the number of retries for page faults
to work in system with less memory, mentioning the issue on README.
- Returned to use volatile on the touch pages routine and a few structs
on inc/nxu.h as they are handled by hardware and some compilers could
optmize it wrongly.
- Moved common functions to gzip_vas.c.
next reply other threads:[~2020-04-13 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 15:59 Raphael Moreira Zinsly [this message]
2020-04-13 15:59 ` [PATCH V3 1/5] selftests/powerpc: Add header files for GZIP engine test Raphael Moreira Zinsly
2020-04-17 5:05 ` Michael Ellerman
2020-04-13 15:59 ` [PATCH V3 2/5] selftests/powerpc: Add header files for NX compresion/decompression Raphael Moreira Zinsly
2020-04-13 15:59 ` [PATCH V3 3/5] selftests/powerpc: Add NX-GZIP engine compress testcase Raphael Moreira Zinsly
2020-04-17 5:05 ` Michael Ellerman
2020-04-13 15:59 ` [PATCH V3 4/5] selftests/powerpc: Add NX-GZIP engine decompress testcase Raphael Moreira Zinsly
2020-04-13 15:59 ` [PATCH V3 5/5] selftests/powerpc: Add README for GZIP engine tests Raphael Moreira Zinsly
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=20200413155916.16900-1-rzinsly@linux.ibm.com \
--to=rzinsly@linux.ibm.com \
--cc=abali@us.ibm.com \
--cc=dja@axtens.net \
--cc=haren@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).