From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v5 22/24] target/arm: Implement ARMv8.5-RNG
Date: Fri, 10 May 2019 09:17:13 -0700 [thread overview]
Message-ID: <dd180f6d-27e8-2f2b-a7ac-ed1d8bbc9498@linaro.org> (raw)
In-Reply-To: <CAFEAcA9uwaev+Q=BgLBz+fgO6C7VGmw4Nxcozg2vm6TOm+LJww@mail.gmail.com>
On 5/10/19 9:01 AM, Peter Maydell wrote:
> On Fri, 10 May 2019 at 02:25, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> Cc: qemu-arm@nongnu.org
>> Cc: Peter Maydell <peter.maydell@linaro.org>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>> v3: Log errors with -d unimp, for lack of a better flag.
>> ---
>> target/arm/cpu.h | 5 +++++
>> target/arm/cpu64.c | 1 +
>> target/arm/helper.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 50 insertions(+)
>
>> +/* We do not support re-seeding, so the two registers operate the same. */
>> +static const ARMCPRegInfo rndr_reginfo[] = {
>> + { .name = "RNDR", .state = ARM_CP_STATE_AA64,
>> + .type = ARM_CP_NO_RAW | ARM_CP_SUPPRESS_TB_END,
>> + .opc0 = 3, .opc1 = 3, .crn = 2, .crm = 4, .opc2 = 0,
>> + .access = PL0_R, .readfn = rndr_readfn },
>> + { .name = "RNDRRS", .state = ARM_CP_STATE_AA64,
>> + .type = ARM_CP_NO_RAW | ARM_CP_SUPPRESS_TB_END,
>> + .opc0 = 3, .opc1 = 3, .crn = 2, .crm = 4, .opc2 = 1,
>> + .access = PL0_R, .readfn = rndr_readfn },
>
> Don't these need to be marked ARM_CP_IO for the benefit
> of -icount ?
I don't think so. There's no lock taken, as for mmio devices. It's not not
related to time, virtual or otherwise. There are no possible exceptions. I
can't think of anything that would make icount care.
Have I missed something?
r~
next prev parent reply other threads:[~2019-05-10 16:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 1:24 [Qemu-devel] [PATCH v5 00/24] Add qemu_getrandom and ARMv8.5-RNG etc Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 01/24] configure: Link test before auto-enabling crypto libraries Richard Henderson
2019-05-10 8:52 ` Daniel P. Berrangé
2019-05-10 9:50 ` Laurent Vivier
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 02/24] crypto: Merge crypto-obj-y into libqemuutil.a Richard Henderson
2019-05-10 8:55 ` Daniel P. Berrangé
2019-05-10 9:57 ` Laurent Vivier
2019-05-10 15:27 ` Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 03/24] crypto: Reverse code blocks in random-platform.c Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 04/24] crypto: Do not fail for EINTR during qcrypto_random_bytes Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 05/24] crypto: Use O_CLOEXEC in qcrypto_random_init Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 06/24] crypto: Use getrandom for qcrypto_random_bytes Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 07/24] crypto: Change the qcrypto_random_bytes buffer type to void* Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 08/24] ui/vnc: Split out authentication_failed Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 09/24] ui/vnc: Use gcrypto_random_bytes for start_auth_vnc Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 10/24] util: Add qemu_guest_getrandom and associated routines Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 11/24] cpus: Initialize pseudo-random seeds for all guest cpus Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 12/24] linux-user: " Richard Henderson
2019-05-10 8:31 ` Laurent Vivier
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 13/24] linux-user: Call qcrypto_init if not using -seed Richard Henderson
2019-05-10 10:03 ` Laurent Vivier
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 14/24] linux-user: Use qemu_guest_getrandom_nofail for AT_RANDOM Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 15/24] linux-user/aarch64: Use qemu_guest_getrandom for PAUTH keys Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 16/24] linux-user: Remove srand call Richard Henderson
2019-05-10 8:32 ` Laurent Vivier
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 17/24] aspeed/scu: Use qemu_guest_getrandom_nofail Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 18/24] hw/misc/nrf51_rng: " Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 19/24] hw/misc/bcm2835_rng: " Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 20/24] hw/misc/exynos4210_rng: Use qemu_guest_getrandom Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 21/24] target/arm: Put all PAC keys into a structure Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 22/24] target/arm: Implement ARMv8.5-RNG Richard Henderson
2019-05-10 16:01 ` Peter Maydell
2019-05-10 16:17 ` Richard Henderson [this message]
2019-05-10 16:20 ` Peter Maydell
2019-05-10 16:21 ` Richard Henderson
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 23/24] target/ppc: Use qemu_guest_getrandom for DARN Richard Henderson
2019-05-10 8:33 ` Laurent Vivier
2019-05-10 1:24 ` [Qemu-devel] [PATCH v5 24/24] target/i386: Implement CPUID_EXT_RDRAND Richard Henderson
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=dd180f6d-27e8-2f2b-a7ac-ed1d8bbc9498@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).