linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens.net>
To: linuxppc-dev@lists.ozlabs.org
Cc: ajd@linux.ibm.com
Subject: Re: [PATCH] powerpc: setup_64: hack around kcov + devicetree limitations
Date: Wed, 12 Feb 2020 16:15:00 +1100	[thread overview]
Message-ID: <875zgcgze3.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <20200212045014.1678-1-dja@axtens.net>

> So: create a fake task and preload it into our fake PACA. Load the paca
> just into r13 (local_paca) before we call into dt_cpu_ftrs_init. This fake
> task persists just for the first part of the setup process before we set
> up the real PACAs.

mpe has asked for this to be fixed in a different way, so I'll respin
with that change.

Daniel

>
> Translations get switched on once we leave early_setup, so I think we'd
> already catch any other cases where the PACA or task aren't set up.
>
> Fixes: fb0b0a73b223 ("powerpc: Enable kcov")
> Cc: Andrew Donnellan <ajd@linux.ibm.com>
> Signed-off-by: Daniel Axtens <dja@axtens.net>
>
> ---
>
> I haven't made the setup conditional on kcov being compiled in, but I
> guess I could if we think it's worth it?
> ---
>  arch/powerpc/kernel/setup_64.c | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
> index e05e6dd67ae6..26f1b8539f8e 100644
> --- a/arch/powerpc/kernel/setup_64.c
> +++ b/arch/powerpc/kernel/setup_64.c
> @@ -281,7 +281,18 @@ void __init record_spr_defaults(void)
>  
>  void __init early_setup(unsigned long dt_ptr)
>  {
> -	static __initdata struct paca_struct boot_paca;
> +	/*
> +	 * We need to get something valid into local_paca/r13 asap if we
> +	 * are using kcov. dt_cpu_ftrs_init will call coverage-enabled code
> +	 * in the generic dt library, and that will try to call in_task().
> +	 * We need a minimal paca that at least provides a valid __current.
> +	 * We can't use the usual initialise/setup/fixup path as that relies
> +	 * on a CPU feature.
> +	 */
> +	static __initdata struct task_struct task = {};
> +	static __initdata struct paca_struct boot_paca = { .__current = &task };
> +
> +	local_paca = &boot_paca;
>  
>  	/* -------- printk is _NOT_ safe to use here ! ------- */
>  
> -- 
> 2.20.1

      reply	other threads:[~2020-02-12  5:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12  4:50 [PATCH] powerpc: setup_64: hack around kcov + devicetree limitations Daniel Axtens
2020-02-12  5:15 ` Daniel Axtens [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=875zgcgze3.fsf@dja-thinkpad.axtens.net \
    --to=dja@axtens.net \
    --cc=ajd@linux.ibm.com \
    --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 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).