From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "Víctor Colombo" <victor.colombo@eldorado.org.br>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: clg@kaod.org, david@gibson.dropbear.id.au, groug@kaod.org,
richard.henderson@linaro.org, cohuck@redhat.com,
farosas@linux.ibm.com
Subject: Re: [PATCH v4 0/3] Implement Power ISA 3.1B hash insns
Date: Tue, 6 Sep 2022 15:44:07 -0300 [thread overview]
Message-ID: <966684c0-d41e-a54a-7c48-27b728dafe4a@gmail.com> (raw)
In-Reply-To: <20220715205439.161110-1-victor.colombo@eldorado.org.br>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 7/15/22 17:54, Víctor Colombo wrote:
> This patch series implements the 4 instructions added in Power ISA
> 3.1B:
>
> - hashchk
> - hashst
> - hashchkp
> - hashstp
>
> It's built on top of ppc-next. Working branch for ease of use can be
> found here:
> https://github.com/PPC64/qemu/tree/vccolombo-hash-to-send-v4
>
> What do you think about the choice to implement the hash algorithm
> from the ground up, following the SIMON-like algorithm presented in
> Power ISA? IIUC, this algorithm is not the same as the original[1].
> Other options would be to use other algorithm already implemented
> in QEMU, or even make this instruction a nop for all Power versions.
>
> v1->v2:
> - Split the patch in 2
> - Rebase to master
>
> v2->v3:
> - Split patches in 3
> - the new patch (patch 1) is separating the kvm header
> changes [Cornelia]
>
> v3->v4:
> - Remove Patch 1 (linux-headers/asm-powerpc/kvm.h:
> Add HASHKEYR and HASHPKEYR in headers)
> - Daniel recommended drop the kvm part:
> https://lists.nongnu.org/archive/html/qemu-ppc/2022-07/msg00213.html
> - Substitute Patch 1 with a separated patch setting up the registers
> for TCG only. Also, now setup it with a random value in linux-user.
> - Change the registers naming:
> - SPR_POWER_HASHKEYR -> SPR_HASHKEYR
> - Drop RFC tag
>
> [1] https://eprint.iacr.org/2013/404.pdf
>
> Víctor Colombo (3):
> target/ppc: Add HASHKEYR and HASHPKEYR SPRs
> target/ppc: Implement hashst and hashchk
> target/ppc: Implement hashstp and hashchkp
>
> target/ppc/cpu.h | 2 +
> target/ppc/cpu_init.c | 28 ++++++++
> target/ppc/excp_helper.c | 84 ++++++++++++++++++++++
> target/ppc/helper.h | 4 ++
> target/ppc/insn32.decode | 10 +++
> target/ppc/translate.c | 5 ++
> target/ppc/translate/fixedpoint-impl.c.inc | 34 +++++++++
> 7 files changed, 167 insertions(+)
>
prev parent reply other threads:[~2022-09-06 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 20:54 [PATCH v4 0/3] Implement Power ISA 3.1B hash insns Víctor Colombo
2022-07-15 20:54 ` [PATCH v4 1/3] target/ppc: Add HASHKEYR and HASHPKEYR SPRs Víctor Colombo
2022-07-18 18:08 ` Lucas Mateus Martins Araujo e Castro
2022-07-15 20:54 ` [PATCH v4 2/3] target/ppc: Implement hashst and hashchk Víctor Colombo
2022-07-18 18:23 ` Lucas Mateus Martins Araujo e Castro
2022-07-15 20:54 ` [PATCH v4 3/3] target/ppc: Implement hashstp and hashchkp Víctor Colombo
2022-07-18 18:23 ` Lucas Mateus Martins Araujo e Castro
2022-09-06 18:44 ` Daniel Henrique Barboza [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=966684c0-d41e-a54a-7c48-27b728dafe4a@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=farosas@linux.ibm.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=victor.colombo@eldorado.org.br \
/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).