All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	x86@kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Will Deacon <will@kernel.org>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Borislav Petkov <bp@suse.de>, Heiko Carstens <hca@linux.ibm.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Harald Freudenberger <freude@linux.ibm.com>
Subject: Re: [PATCH v2] random: handle archrandom in plural words
Date: Mon, 18 Jul 2022 16:31:11 +1000	[thread overview]
Message-ID: <87a697dj9s.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220717200356.75060-1-Jason@zx2c4.com>

"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> The archrandom interface was originally designed for x86, which supplies
> RDRAND/RDSEED for receiving random words into registers, resulting in
> one function to generate an int and another to generate a long. However,
> other architectures don't follow this.
>
> On arm64, the SMCCC TRNG interface can return between 1 and 3 words. On
> s390, the CPACF TRNG interface can return between 1 and 32 words for the
> same cost as for one word. On UML, the os_getrandom() interface can return
> arbitrary amounts.
>
> So change the api signature to take a "words" parameter designating the
> maximum number of words requested, and then return the number of words
> generated.

On powerpc a word is 32-bits and a doubleword is 64-bits (at least
according to the ISA). I think that's also true on other 64-bit
architectures.

You could avoid any confusion by defining the API in terms of "longs"
rather than "words".

But that's just a comment, see what others think.

>  arch/powerpc/include/asm/archrandom.h |  30 ++------
>  arch/powerpc/kvm/book3s_hv.c          |   2 +-

Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	x86@kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Harald Freudenberger <freude@linux.ibm.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Borislav Petkov <bp@suse.de>, Will Deacon <will@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] random: handle archrandom in plural words
Date: Mon, 18 Jul 2022 16:31:11 +1000	[thread overview]
Message-ID: <87a697dj9s.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220717200356.75060-1-Jason@zx2c4.com>

"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> The archrandom interface was originally designed for x86, which supplies
> RDRAND/RDSEED for receiving random words into registers, resulting in
> one function to generate an int and another to generate a long. However,
> other architectures don't follow this.
>
> On arm64, the SMCCC TRNG interface can return between 1 and 3 words. On
> s390, the CPACF TRNG interface can return between 1 and 32 words for the
> same cost as for one word. On UML, the os_getrandom() interface can return
> arbitrary amounts.
>
> So change the api signature to take a "words" parameter designating the
> maximum number of words requested, and then return the number of words
> generated.

On powerpc a word is 32-bits and a doubleword is 64-bits (at least
according to the ISA). I think that's also true on other 64-bit
architectures.

You could avoid any confusion by defining the API in terms of "longs"
rather than "words".

But that's just a comment, see what others think.

>  arch/powerpc/include/asm/archrandom.h |  30 ++------
>  arch/powerpc/kvm/book3s_hv.c          |   2 +-

Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
	x86@kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Will Deacon <will@kernel.org>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Borislav Petkov <bp@suse.de>, Heiko Carstens <hca@linux.ibm.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Harald Freudenberger <freude@linux.ibm.com>
Subject: Re: [PATCH v2] random: handle archrandom in plural words
Date: Mon, 18 Jul 2022 16:31:11 +1000	[thread overview]
Message-ID: <87a697dj9s.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220717200356.75060-1-Jason@zx2c4.com>

"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> The archrandom interface was originally designed for x86, which supplies
> RDRAND/RDSEED for receiving random words into registers, resulting in
> one function to generate an int and another to generate a long. However,
> other architectures don't follow this.
>
> On arm64, the SMCCC TRNG interface can return between 1 and 3 words. On
> s390, the CPACF TRNG interface can return between 1 and 32 words for the
> same cost as for one word. On UML, the os_getrandom() interface can return
> arbitrary amounts.
>
> So change the api signature to take a "words" parameter designating the
> maximum number of words requested, and then return the number of words
> generated.

On powerpc a word is 32-bits and a doubleword is 64-bits (at least
according to the ISA). I think that's also true on other 64-bit
architectures.

You could avoid any confusion by defining the API in terms of "longs"
rather than "words".

But that's just a comment, see what others think.

>  arch/powerpc/include/asm/archrandom.h |  30 ++------
>  arch/powerpc/kvm/book3s_hv.c          |   2 +-

Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)

cheers

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-07-18  6:31 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 11:24 [PATCH] random: handle archrandom in plural words Jason A. Donenfeld
2022-07-17 11:43 ` Jason A. Donenfeld
2022-07-17 20:03   ` [PATCH v2] " Jason A. Donenfeld
2022-07-17 20:03     ` Jason A. Donenfeld
2022-07-17 20:03     ` Jason A. Donenfeld
2022-07-17 20:03     ` Jason A. Donenfeld
2022-07-18  6:31     ` Michael Ellerman [this message]
2022-07-18  6:31       ` Michael Ellerman
2022-07-18  6:31       ` Michael Ellerman
2022-07-18  6:46       ` Gabriel Paubert
2022-07-18  6:46         ` Gabriel Paubert
2022-07-18  6:46         ` Gabriel Paubert
2022-07-20  3:03         ` Michael Ellerman
2022-07-20  3:03           ` Michael Ellerman
2022-07-20  3:03           ` Michael Ellerman
2022-07-19 12:42     ` Mark Rutland
2022-07-19 12:42       ` Mark Rutland
2022-07-19 12:42       ` Mark Rutland
2022-07-19 12:46       ` Jason A. Donenfeld
2022-07-19 12:46         ` Jason A. Donenfeld
2022-07-19 12:46         ` Jason A. Donenfeld
2022-07-19 13:02         ` [PATCH v3] random: handle archrandom with multiple longs Jason A. Donenfeld
2022-07-19 13:02           ` Jason A. Donenfeld
2022-07-19 13:02           ` Jason A. Donenfeld
2022-07-19 13:17           ` Mark Rutland
2022-07-19 13:17             ` Mark Rutland
2022-07-19 13:17             ` Mark Rutland
2022-07-19 13:48           ` Catalin Marinas
2022-07-19 13:48             ` Catalin Marinas
2022-07-19 13:48             ` Catalin Marinas
2022-07-22 12:06           ` Heiko Carstens
2022-07-22 12:06             ` Heiko Carstens
2022-07-22 12:06             ` Heiko Carstens
2022-07-24 22:47           ` Jason A. Donenfeld
2022-07-25  9:19           ` Borislav Petkov
2022-07-25  9:19             ` Borislav Petkov
2022-07-25  9:19             ` Borislav Petkov
2022-07-25  9:26             ` Jason A. Donenfeld
2022-07-25  9:26               ` Jason A. Donenfeld
2022-07-25  9:26               ` Jason A. Donenfeld
2022-07-25  9:36               ` David Laight
2022-07-25  9:36                 ` David Laight
2022-07-25  9:36                 ` David Laight
2022-07-25  9:37                 ` Jason A. Donenfeld
2022-07-25  9:37                   ` Jason A. Donenfeld
2022-07-25  9:37                   ` Jason A. Donenfeld
2022-07-25 11:10               ` [PATCH] random: discourage use of archrandom outside of rng Jason A. Donenfeld
2022-07-25 11:25                 ` Borislav Petkov
2022-07-25 11:33                 ` Heiko Carstens
2022-07-25 13:02                 ` Mark Rutland
2022-07-25 11:25           ` [PATCH v3] random: handle archrandom with multiple longs Borislav Petkov
2022-07-25 11:25             ` Borislav Petkov
2022-07-25 11:25             ` Borislav Petkov
2022-08-01 14:46           ` Harald Freudenberger
2022-08-01 14:46             ` Harald Freudenberger
2022-08-01 14:46             ` Harald Freudenberger
2022-08-01 14:50             ` Jason A. Donenfeld
2022-08-01 14:50               ` Jason A. Donenfeld
2022-08-01 14:50               ` Jason A. Donenfeld
2022-07-22  8:08     ` [PATCH v2] random: handle archrandom in plural words Holger Dengler
2022-07-22  8:08       ` Holger Dengler
2022-07-22  8:08       ` Holger Dengler
2022-07-22 11:22       ` Jason A. Donenfeld
2022-07-22 11:22         ` Jason A. Donenfeld
2022-07-22 11:22         ` Jason A. Donenfeld
2022-08-03 12:01         ` Holger Dengler
2022-08-03 12:01           ` Holger Dengler
2022-08-03 12:01           ` Holger Dengler

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=87a697dj9s.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=Jason@zx2c4.com \
    --cc=agordeev@linux.ibm.com \
    --cc=bp@suse.de \
    --cc=catalin.marinas@arm.com \
    --cc=freude@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    --cc=x86@kernel.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 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.