From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Leandro Lupori <leandro.lupori@eldorado.org.br>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Cc: clg@kaod.org, david@gibson.dropbear.id.au, groug@kaod.org,
Victor Colombo <victor.colombo@eldorado.org.br>
Subject: Re: [PATCH] target/ppc: Fix regression in Radix MMU
Date: Fri, 28 Oct 2022 17:20:22 -0300 [thread overview]
Message-ID: <22dcc32d-bf42-00a6-e7c6-08c98ea0b3f4@gmail.com> (raw)
In-Reply-To: <20221028183617.121786-1-leandro.lupori@eldorado.org.br>
On 10/28/22 15:36, Leandro Lupori wrote:
> Commit 47e83d9107 ended up unintentionally changing the control flow
> of ppc_radix64_process_scoped_xlate(). When guest_visible is false,
> it must not raise an exception, even if the radix configuration is
> not valid.
>
> This regression prevented Linux boot in a nested environment with
> L1 using TCG and emulating KVM (cap-nested-hv=on) and L2 using
> KVM. L2 would hang on Linux's futex_init(), when it tested how a
> futex_atomic_cmpxchg_inatomic() handled a fault, because L1 would
> start a loop of trying to perform partition scoped translations
> and raising exceptions.
>
> Fixes: 47e83d9107 ("target/ppc: Improve Radix xlate level validation")
> Reported-by: Victor Colombo <victor.colombo@eldorado.org.br>
> Signed-off-by: Leandro Lupori <leandro.lupori@eldorado.org.br>
> ---
> target/ppc/mmu-radix64.c | 28 ++++++++++++++++++++--------
> 1 file changed, 20 insertions(+), 8 deletions(-)
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
I'll queue this up in the pending pull request.
Thanks,
Daniel
>
> diff --git a/target/ppc/mmu-radix64.c b/target/ppc/mmu-radix64.c
> index 00f2e9fa2e..171379db69 100644
> --- a/target/ppc/mmu-radix64.c
> +++ b/target/ppc/mmu-radix64.c
> @@ -238,6 +238,8 @@ static void ppc_radix64_set_rc(PowerPCCPU *cpu, MMUAccessType access_type,
>
> static bool ppc_radix64_is_valid_level(int level, int psize, uint64_t nls)
> {
> + bool ret;
> +
> /*
> * Check if this is a valid level, according to POWER9 and POWER10
> * Processor User's Manuals, sections 4.10.4.1 and 5.10.6.1, respectively:
> @@ -249,16 +251,24 @@ static bool ppc_radix64_is_valid_level(int level, int psize, uint64_t nls)
> */
> switch (level) {
> case 0: /* Root Page Dir */
> - return psize == 52 && nls == 13;
> + ret = psize == 52 && nls == 13;
> + break;
> case 1:
> case 2:
> - return nls == 9;
> + ret = nls == 9;
> + break;
> case 3:
> - return nls == 9 || nls == 5;
> + ret = nls == 9 || nls == 5;
> + break;
> default:
> - qemu_log_mask(LOG_GUEST_ERROR, "invalid radix level: %d\n", level);
> - return false;
> + ret = false;
> + }
> +
> + if (unlikely(!ret)) {
> + qemu_log_mask(LOG_GUEST_ERROR, "invalid radix configuration: "
> + "level %d size %d nls %ld\n", level, psize, nls);
> }
> + return ret;
> }
>
> static int ppc_radix64_next_level(AddressSpace *as, vaddr eaddr,
> @@ -519,11 +529,13 @@ static int ppc_radix64_process_scoped_xlate(PowerPCCPU *cpu,
>
> if (!ppc_radix64_is_valid_level(level++, *g_page_size, nls)) {
> fault_cause |= DSISR_R_BADCONFIG;
> - return 1;
> + ret = 1;
> + } else {
> + ret = ppc_radix64_next_level(cs->as, eaddr & R_EADDR_MASK,
> + &h_raddr, &nls, g_page_size,
> + &pte, &fault_cause);
> }
>
> - ret = ppc_radix64_next_level(cs->as, eaddr & R_EADDR_MASK, &h_raddr,
> - &nls, g_page_size, &pte, &fault_cause);
> if (ret) {
> /* No valid pte */
> if (guest_visible) {
prev parent reply other threads:[~2022-10-28 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 18:36 [PATCH] target/ppc: Fix regression in Radix MMU Leandro Lupori
2022-10-28 18:53 ` Víctor Colombo
2022-10-28 20:20 ` Daniel Henrique Barboza [this message]
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=22dcc32d-bf42-00a6-e7c6-08c98ea0b3f4@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=leandro.lupori@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=victor.colombo@eldorado.org.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.