From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH kernel] powerpc/init: Do not advertise radix during client-architecture-support
Date: Thu, 15 Feb 2018 16:44:25 +1100 [thread overview]
Message-ID: <111a5e87-2336-c107-74be-af0330be48eb@ozlabs.ru> (raw)
In-Reply-To: <20180109054520.31704-1-aik@ozlabs.ru>
On 09/01/18 16:45, Alexey Kardashevskiy wrote:
> Currently the pseries kernel advertises radix MMU support even if
> the actual support is disabled via the CONFIG_PPC_RADIX_MMU option.
>
> This adds a check for CONFIG_PPC_RADIX_MMU to avoid advertising radix
> to the hypervisor.
>
> Suggested-by: Paul Mackerras <paulus@ozlabs.org>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Ping?
> ---
> arch/powerpc/kernel/prom_init.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
> index 02190e9..65879df 100644
> --- a/arch/powerpc/kernel/prom_init.c
> +++ b/arch/powerpc/kernel/prom_init.c
> @@ -1109,7 +1109,8 @@ static void __init prom_check_platform_support(void)
> }
> }
>
> - if (supported.radix_mmu && supported.radix_gtse) {
> + if (supported.radix_mmu && supported.radix_gtse &&
> + IS_ENABLED(CONFIG_PPC_RADIX_MMU)) {
> /* Radix preferred - but we require GTSE for now */
> prom_debug("Asking for radix with GTSE\n");
> ibm_architecture_vec.vec5.mmu = OV5_FEAT(OV5_MMU_RADIX);
>
--
Alexey
next prev parent reply other threads:[~2018-02-15 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 5:45 [PATCH kernel] powerpc/init: Do not advertise radix during client-architecture-support Alexey Kardashevskiy
2018-02-15 5:44 ` Alexey Kardashevskiy [this message]
2018-03-28 14:13 ` [kernel] " Michael Ellerman
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=111a5e87-2336-c107-74be-af0330be48eb@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.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.