From: Rebecca Cran <rebecca@nuviainc.com>
To: peter.maydell@linaro.org, richard.henderson@linaro.org
Cc: Rebecca Cran <rebecca@nuviainc.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Subject: [PATCH v7 0/4] Add support for FEAT_TLBIOS and FEAT_TLBIRANGE
Date: Wed, 14 Apr 2021 14:32:27 -0600 [thread overview]
Message-ID: <20210414203231.824-1-rebecca@nuviainc.com> (raw)
ARMv8.4 adds the mandatory FEAT_TLBIOS and FEAT_TLBIRANGE.
They provides TLBI maintenance instructions that extend to the Outer
Shareable domain and that apply to a range of input addresses.
Changes from v6 to v7:
o Fixed the tlbi_aa64_rvae1_write the tlbi_aa64_rvae1is_write functions
to pass the correct value into functions which use an ARMMMUIdx.
o Fixed comments in helper.c which referred to non-existent instructions.
Testing:
o Booted Linux 5.11 - verified the previous assert failure in qemu is
resolved.
o Ran checkpatch.pl.
Rebecca Cran (4):
accel/tcg: Add TLB invalidation support for ranges of addresses
target/arm: Add support for FEAT_TLBIRANGE
target/arm: Add support for FEAT_TLBIOS
target/arm: set ID_AA64ISAR0.TLB to 2 for max AARCH64 CPU type
accel/tcg/cputlb.c | 130 ++++++-
include/exec/exec-all.h | 46 +++
target/arm/cpu.h | 10 +
target/arm/cpu64.c | 1 +
target/arm/helper.c | 371 ++++++++++++++++++++
5 files changed, 555 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2021-04-14 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 20:32 Rebecca Cran [this message]
2021-04-14 20:32 ` [PATCH v7 1/4] accel/tcg: Add TLB invalidation support for ranges of addresses Rebecca Cran
2021-04-14 20:32 ` [PATCH v7 2/4] target/arm: Add support for FEAT_TLBIRANGE Rebecca Cran
2021-04-14 20:32 ` [PATCH v7 3/4] target/arm: Add support for FEAT_TLBIOS Rebecca Cran
2021-04-14 20:32 ` [PATCH v7 4/4] target/arm: set ID_AA64ISAR0.TLB to 2 for max AARCH64 CPU type Rebecca Cran
2021-04-19 20:05 ` [PATCH v7 0/4] Add support for FEAT_TLBIOS and FEAT_TLBIRANGE 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=20210414203231.824-1-rebecca@nuviainc.com \
--to=rebecca@nuviainc.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).