From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org
Subject: [PATCH 0/2] target/arm: Fix issue 1078
Date: Sat, 18 Jun 2022 17:15:39 -0700 [thread overview]
Message-ID: <20220619001541.131672-1-richard.henderson@linaro.org> (raw)
Nicely summarized by the reporter, but I thought it would be
nicer to pull all of the logic into arm_pamax, rather than
leave it separated.
r~
Richard Henderson (2):
target/arm: Extend arm_pamax to more than aarch64
target/arm: Check V7VE as well as LPAE in arm_pamax
hw/arm/virt.c | 10 +---------
target/arm/ptw.c | 26 ++++++++++++++++++++------
2 files changed, 21 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2022-06-19 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 0:15 Richard Henderson [this message]
2022-06-19 0:15 ` [PATCH 1/2] target/arm: Extend arm_pamax to more than aarch64 Richard Henderson
2022-06-24 16:25 ` Peter Maydell
2022-06-19 0:15 ` [PATCH 2/2] target/arm: Check V7VE as well as LPAE in arm_pamax Richard Henderson
2022-06-24 16:27 ` Peter Maydell
2022-06-24 17:42 ` Richard Henderson
2022-06-21 2:57 ` [PATCH 0/2] target/arm: Fix issue 1078 He Zhe
2022-06-24 16:32 ` Peter Maydell
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=20220619001541.131672-1-richard.henderson@linaro.org \
--to=richard.henderson@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).