From: Fabiano Rosas <farosas@linux.ibm.com>
To: Leandro Lupori <leandro.lupori@eldorado.org.br>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: clg@kaod.org, danielhb413@gmail.com, david@gibson.dropbear.id.au,
groug@kaod.org, richard.henderson@linaro.org,
Leandro Lupori <leandro.lupori@eldorado.org.br>
Subject: Re: [PATCH v2 2/3] target/ppc: Improve Radix xlate level validation
Date: Fri, 24 Jun 2022 15:34:43 -0300 [thread overview]
Message-ID: <87czexc3lo.fsf@linux.ibm.com> (raw)
In-Reply-To: <20220624171653.143740-3-leandro.lupori@eldorado.org.br>
Leandro Lupori <leandro.lupori@eldorado.org.br> writes:
> Check if the number and size of Radix levels are valid on
> POWER9/POWER10 CPUs, according to the supported Radix Tree
> Configurations described in their User Manuals.
>
> Signed-off-by: Leandro Lupori <leandro.lupori@eldorado.org.br>
> ---
> target/ppc/mmu-radix64.c | 51 +++++++++++++++++++++++++++++++---------
> 1 file changed, 40 insertions(+), 11 deletions(-)
>
> diff --git a/target/ppc/mmu-radix64.c b/target/ppc/mmu-radix64.c
> index 9a8a2e2875..339cf5b4d8 100644
> --- a/target/ppc/mmu-radix64.c
> +++ b/target/ppc/mmu-radix64.c
> @@ -236,17 +236,39 @@ 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)
> +{
> + /*
> + * 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:
> + * Supported Radix Tree Configurations and Resulting Page Sizes.
> + *
> + * NOTE: these checks are valid for POWER9 and POWER10 CPUs only. If
> + * new CPUs that support other Radix configurations are added
> + * (e.g., Microwatt), then a new method should be added to
> + * PowerPCCPUClass, with this function being the POWER9/POWER10
> + * implementation.
> + */
Sorry, this got too specific now. I could not respond in time before you
sent the v2. Let's cut the mentions to the code:
Note: these checks are specific to POWER9 and POWER10 CPUs. Any future
CPUs that supports a different Radix MMU configuration will need their
own implementation.
> + switch (level) {
> + case 0: /* Root Page Dir */
> + return psize == 52 && nls == 13;
> + case 1:
> + case 2:
> + return nls == 9;
> + case 3:
> + return nls == 9 || nls == 5;
> + default:
> + qemu_log_mask(LOG_GUEST_ERROR, "invalid radix level: %d\n", level);
> + return false;
> + }
> +}
> +
> static int ppc_radix64_next_level(AddressSpace *as, vaddr eaddr,
> uint64_t *pte_addr, uint64_t *nls,
> int *psize, uint64_t *pte, int *fault_cause)
> {
> uint64_t index, pde;
>
> - if (*nls < 5) { /* Directory maps less than 2**5 entries */
> - *fault_cause |= DSISR_R_BADCONFIG;
> - return 1;
> - }
> -
> /* Read page <directory/table> entry from guest address space */
> pde = ldq_phys(as, *pte_addr);
> if (!(pde & R_PTE_VALID)) { /* Invalid Entry */
> @@ -270,12 +292,8 @@ static int ppc_radix64_walk_tree(AddressSpace *as, vaddr eaddr,
> hwaddr *raddr, int *psize, uint64_t *pte,
> int *fault_cause, hwaddr *pte_addr)
> {
> - uint64_t index, pde, rpn , mask;
> -
> - if (nls < 5) { /* Directory maps less than 2**5 entries */
> - *fault_cause |= DSISR_R_BADCONFIG;
> - return 1;
> - }
> + uint64_t index, pde, rpn, mask;
> + int level = 0;
>
> index = eaddr >> (*psize - nls); /* Shift */
> index &= ((1UL << nls) - 1); /* Mask */
> @@ -283,6 +301,11 @@ static int ppc_radix64_walk_tree(AddressSpace *as, vaddr eaddr,
> do {
> int ret;
>
> + if (!ppc_radix64_is_valid_level(level++, *psize, nls)) {
> + *fault_cause |= DSISR_R_BADCONFIG;
> + return 1;
> + }
> +
> ret = ppc_radix64_next_level(as, eaddr, pte_addr, &nls, psize, &pde,
> fault_cause);
> if (ret) {
> @@ -456,6 +479,7 @@ static int ppc_radix64_process_scoped_xlate(PowerPCCPU *cpu,
> }
> } else {
> uint64_t rpn, mask;
> + int level = 0;
>
> index = (eaddr & R_EADDR_MASK) >> (*g_page_size - nls); /* Shift */
> index &= ((1UL << nls) - 1); /* Mask */
> @@ -475,6 +499,11 @@ static int ppc_radix64_process_scoped_xlate(PowerPCCPU *cpu,
> return ret;
> }
>
> + if (!ppc_radix64_is_valid_level(level++, *g_page_size, nls)) {
> + fault_cause |= DSISR_R_BADCONFIG;
> + return 1;
> + }
> +
> ret = ppc_radix64_next_level(cs->as, eaddr & R_EADDR_MASK, &h_raddr,
> &nls, g_page_size, &pte, &fault_cause);
> if (ret) {
next prev parent reply other threads:[~2022-06-24 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 17:16 [PATCH v2 0/3] ppc: Check for bad Radix configs Leandro Lupori
2022-06-24 17:16 ` [PATCH v2 1/3] ppc: Check partition and process table alignment Leandro Lupori
2022-06-24 18:35 ` Fabiano Rosas
2022-06-24 17:16 ` [PATCH v2 2/3] target/ppc: Improve Radix xlate level validation Leandro Lupori
2022-06-24 18:34 ` Fabiano Rosas [this message]
2022-06-24 17:16 ` [PATCH v2 3/3] target/ppc: Check page dir/table base alignment Leandro Lupori
2022-06-24 18:04 ` Richard Henderson
2022-06-24 20:10 ` Leandro Lupori
2022-06-24 18:47 ` Fabiano Rosas
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=87czexc3lo.fsf@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--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=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 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.