From: Richard Henderson <richard.henderson@linaro.org>
To: Rebecca Cran <rebecca@nuviainc.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v8 2/4] target/arm: Add support for FEAT_TLBIRANGE
Date: Sat, 8 May 2021 09:39:33 -0700 [thread overview]
Message-ID: <a4e9c32f-7812-1ed8-37a0-60612bda7c52@linaro.org> (raw)
In-Reply-To: <20210505030443.25310-3-rebecca@nuviainc.com>
On 5/4/21 8:04 PM, Rebecca Cran wrote:
> +static uint64_t tlbi_aa64_range_get_length(CPUARMState *env,
> + uint64_t value)
> +{
> + unsigned int page_shift;
> + unsigned int page_size_granule;
> + uint64_t num;
> + uint64_t scale;
> + uint64_t exponent;
> + uint64_t length;
> +
> + num = extract64(value, 39, 4);
> + scale = extract64(value, 44, 2);
> + page_size_granule = extract64(value, 46, 2);
> +
> + page_shift = page_size_granule * 2 + 10;
Should be + 12, for the sequence 12, 14, 16 (4k, 16k, 64k).
> +static void tlbi_aa64_rvae1_write(CPUARMState *env, const ARMCPRegInfo *ri,
> + uint64_t value)
> +{
> + /*
> + * Invalidate by VA range, EL1&0.
> + * Currently handles all of RVAE1, RVAAE1, RVAALE1 and RVALE1,
> + * since we don't support flush-for-specific-ASID-only or
> + * flush-last-level-only.
> + */
> + ARMMMUIdx mmu_idx;
> + int mask;
> + int bits;
> + uint64_t pageaddr;
> + uint64_t length;
> +
> + CPUState *cs = env_cpu(env);
> + mask = vae1_tlbmask(env);
> + mmu_idx = ARM_MMU_IDX_A | ctz32(mask);
> + if (regime_has_2_ranges(mmu_idx)) {
> + pageaddr = sextract64(value, 0, 37) << TARGET_PAGE_BITS;
> + } else {
> + pageaddr = extract64(value, 0, 37) << TARGET_PAGE_BITS;
> + }
Let's extract the base address via a helper as well. Add
/* TODO: ARMv8.7 FEAT_LPA2 */
as that will change the extracted base address.
I think there's enough replicated between these functions to want a common
function. Something like
static void do_rvae_write(CPUARMState *env, uint64_t value,
int idxmap, bool synced)
{
ARMMMUIdx one_idx = ARM_MMU_IDX_A | ctz32(idxmap);
bool two_ranges = regime_has_2_ranges(one_idx);
uint64_t baseaddr, length;
int bits;
baseaddr = tlbi_aa64_range_get_base(env, value, two_ranges);
length = tlb_aa64_range_get_length(env, value);
bits = tlbbits_for_regime(env, one_idx, baseaddr);
if (synced) {
tlb_flush_range_by_mmuidx_all_cpus_synced(...);
} else {
tlb_flush_range_by_mmuidx(...);
}
}
static void tlbi_aa64_rvae1_write(...)
{
do_rvae_write(env, value, vae1_tlbmask(env),
tlb_force_broadcast(env));
}
static void tlbi_aa64_rvae1is_write(...)
{
do_rvae_write(env, value, vae1_tlbmask(env), true);
}
static int vae2_tlbmask(CPUARMState *env)
{
return (arm_is_secure_below_el3(env)
? ARMMMUIdxBit_SE2 : ARMMMUIdxBit_E2);
}
static void tlbi_aa64_rvae2_write(...)
{
do_rvae_write(env, value, vae2_tlbmask(env),
tlb_force_broadcast(env));
}
static void tlbi_aa64_rvae2is_write(...)
{
do_rvae_write(env, value, vae2_tlbmask(env), true);
}
static void tlbi_aa64_rvae3_write(...)
{
do_rvae_write(env, value, ARMMMUIdxBit_SE3,
tlb_force_broadcast(env));
}
static void tlbi_aa64_rvae3is_write(...)
{
do_rvae_write(env, value, ARMMMUIdxBit_SE3, true);
}
r~
next prev parent reply other threads:[~2021-05-08 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 3:04 [PATCH v8 0/4] aarch64: add support for FEAT_TLBIRANGE and FEAT_TLBIOS Rebecca Cran
2021-05-05 3:04 ` [PATCH v8 1/4] accel/tcg: Add TLB invalidation support for ranges of addresses Rebecca Cran
2021-05-08 15:55 ` Richard Henderson
2021-05-05 3:04 ` [PATCH v8 2/4] target/arm: Add support for FEAT_TLBIRANGE Rebecca Cran
2021-05-08 16:39 ` Richard Henderson [this message]
2021-05-05 3:04 ` [PATCH v8 3/4] target/arm: Add support for FEAT_TLBIOS Rebecca Cran
2021-05-08 16:46 ` Richard Henderson
2021-05-05 3:04 ` [PATCH v8 4/4] target/arm: set ID_AA64ISAR0.TLB to 2 for max AARCH64 CPU type Rebecca Cran
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=a4e9c32f-7812-1ed8-37a0-60612bda7c52@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rebecca@nuviainc.com \
/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).