All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Balbir Singh <bsingharora@gmail.com>,
	paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/mm: Use jump label to speed up radix_enabled check
Date: Fri, 10 Jun 2016 14:16:29 +1000	[thread overview]
Message-ID: <1465532189.26682.9.camel@ellerman.id.au> (raw)
In-Reply-To: <87oa7a8ica.fsf@skywalker.in.ibm.com>

On Thu, 2016-06-09 at 21:28 +0530, Aneesh Kumar K.V wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> > On Wed, 2016-04-27 at 12:30 +0530, Aneesh Kumar K.V wrote:
> 
> So how early can we call jump_label_init() ? What is the reason why we
> do the existing feature fixups in setup_system and not before that ?.
> The previous patch series did end up moving jump_label_init() to
> 
>  @@ -250,6 +250,8 @@ void __init early_setup(unsigned long dt_ptr)
>          /* Initialize lockdep early or else spinlocks will blow */
>          lockdep_init();
> 
>  	jump_label_init();
> 
>         /* -------- printk is now safe to use ------- */
> 
> is that safe to do ?
 
Maybe. Maybe not.

It depends what that function does. It might work now, but it could break later
when someone changes the jump label code, and it might work on some platforms
but not others.

That is *really* early. We haven't looked at the device tree yet, we haven't
even enabled early debug.

So I'd rather we did it later, but that has other issues I guess.

cheers

  reply	other threads:[~2016-06-10  4:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 16:24 [PATCH] powerpc/mm: Use jump label to speed up radix_enabled check Aneesh Kumar K.V
2016-04-26 21:05 ` Benjamin Herrenschmidt
2016-04-26 22:16   ` Balbir Singh
2016-04-26 23:05     ` Benjamin Herrenschmidt
2016-04-27  1:00       ` Balbir Singh
2016-04-27  1:46         ` Benjamin Herrenschmidt
2016-04-27  7:00           ` Aneesh Kumar K.V
2016-04-27  9:30             ` Aneesh Kumar K.V
2016-06-09  4:12             ` Benjamin Herrenschmidt
2016-06-09  6:00               ` Aneesh Kumar K.V
2016-06-09 15:58               ` Aneesh Kumar K.V
2016-06-10  4:16                 ` Michael Ellerman [this message]
2016-06-10  5:46                   ` Benjamin Herrenschmidt

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=1465532189.26682.9.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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.