From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [PATCH 4/5] target/arm: Support more GM blocksizes
Date: Thu, 10 Aug 2023 12:10:57 -0700 [thread overview]
Message-ID: <8793650b-4e48-c4c1-be75-1f79692496d7@linaro.org> (raw)
In-Reply-To: <CAFEAcA8YcX0qq392chnpVdB2-qjk7Jb-4gBEu-e2uDGka3Ccvg@mail.gmail.com>
On 8/10/23 07:23, Peter Maydell wrote:
>> + case 4:
>> + /* 64 bytes -> 4 tags -> 16 result bits */
>> + ret = cpu_to_le16(*(uint16_t *)tag_mem);
>
> Does this really make a difference compared to ldw_le_p() ?
ldw_le_p uses memcpy, though only mips and sparc hosts do not have unaligned reads, so
perhaps it doesn't make much difference.
I had originally been thinking about atomicity, but then noticed that the pseudocode uses
a loop and so the instruction is therefore non-atomic.
> Is it worth having an assert in CPU realize for an invalid
> blocksize, so that we can catch duff ID register values
> without having to rely on there being a test run that
> uses ldgm/stgm ?
Yes, that's a good idea.
r~
next prev parent reply other threads:[~2023-08-10 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 2:35 [PATCH for-8.2 0/5] target/arm: Implement cortex-a710 Richard Henderson
2023-08-10 2:35 ` [PATCH 1/5] target/arm: Disable FEAT_TRF in neoverse-v1 Richard Henderson
2023-08-10 9:16 ` Peter Maydell
2023-08-10 2:35 ` [PATCH 2/5] target/arm: Reduce dcz_blocksize to uint8_t Richard Henderson
2023-08-10 14:09 ` Peter Maydell
2023-08-10 19:02 ` Richard Henderson
2023-08-10 2:35 ` [PATCH 3/5] target/arm: Allow cpu to configure GM blocksize Richard Henderson
2023-08-10 14:13 ` Peter Maydell
2023-08-10 2:35 ` [PATCH 4/5] target/arm: Support more GM blocksizes Richard Henderson
2023-08-10 14:23 ` Peter Maydell
2023-08-10 19:10 ` Richard Henderson [this message]
2023-08-10 2:35 ` [PATCH 5/5] target/arm: Implement cortex-a710 Richard Henderson
2023-08-10 4:11 ` Richard Henderson
2023-08-10 15:49 ` Peter Maydell
2023-08-10 17:05 ` Richard Henderson
2023-08-10 17:12 ` Peter Maydell
2023-08-14 8:49 ` Marcin Juszkiewicz
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=8793650b-4e48-c4c1-be75-1f79692496d7@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).