From: Peter Zijlstra <peterz@infradead.org>
To: Nadav Amit <namit@vmware.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Kees Cook <keescook@chromium.org>,
Dave Hansen <dave.hansen@intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH v3 2/7] x86/jump_label: Use text_poke_early() during early_init
Date: Mon, 5 Nov 2018 14:33:47 +0100 [thread overview]
Message-ID: <20181105133347.GA22485@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20181105123953.GA22467@hirez.programming.kicks-ass.net>
On Mon, Nov 05, 2018 at 01:39:53PM +0100, Peter Zijlstra wrote:
> On Fri, Nov 02, 2018 at 04:29:41PM -0700, Nadav Amit wrote:
> > diff --git a/init/main.c b/init/main.c
> > index a664246450d1..b0fa26637496 100644
> > --- a/init/main.c
> > +++ b/init/main.c
> > @@ -117,6 +117,8 @@ extern void radix_tree_init(void);
> > */
> > bool early_boot_irqs_disabled __read_mostly;
> >
> > +u8 early_boot_done __read_mostly;
> > +
> > enum system_states system_state __read_mostly;
> > EXPORT_SYMBOL(system_state);
>
> Should this not be using system_state ^ ? The site is very close to
> SYSTEM_SCHEDULING, can we use that or should we add another state ?
We must be before kernel_init() -> kernel_init_freeable() -> smp_init().
So we need another state, something like SYSTEM_BOOTING_SMP I suppose ?
> > @@ -735,6 +737,8 @@ asmlinkage __visible void __init start_kernel(void)
> > efi_free_boot_services();
> > }
> >
> > + early_boot_done = true;
> > +
> > /* Do the rest non-__init'ed, we're now alive */
> > rest_init();
> > }
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2018-11-05 13:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 23:29 [PATCH v3 0/7] x86/alternatives: text_poke() fixes Nadav Amit
2018-11-02 23:29 ` [PATCH v3 1/7] Fix "x86/alternatives: Lockdep-enforce text_mutex in text_poke*()" Nadav Amit
2018-11-03 10:11 ` Jiri Kosina
2018-11-04 20:58 ` Thomas Gleixner
2018-11-05 18:14 ` Nadav Amit
2018-11-02 23:29 ` [PATCH v3 2/7] x86/jump_label: Use text_poke_early() during early_init Nadav Amit
2018-11-05 12:39 ` Peter Zijlstra
2018-11-05 13:33 ` Peter Zijlstra [this message]
2018-11-05 14:09 ` Peter Zijlstra
2018-11-05 17:22 ` Andy Lutomirski
2018-11-05 17:49 ` Nadav Amit
2018-11-05 19:03 ` Andy Lutomirski
2018-11-05 19:25 ` Nadav Amit
2018-11-05 20:05 ` Andy Lutomirski
2018-11-05 20:28 ` Thomas Gleixner
2018-11-05 21:31 ` Nadav Amit
2018-11-07 19:13 ` Nadav Amit
2018-11-08 10:41 ` Peter Zijlstra
2018-11-02 23:29 ` [PATCH v3 3/7] x86/mm: temporary mm struct Nadav Amit
2018-11-02 23:29 ` [PATCH v3 4/7] fork: provide a function for copying init_mm Nadav Amit
2018-11-02 23:29 ` [PATCH v3 5/7] x86/alternatives: initializing temporary mm for patching Nadav Amit
2018-11-02 23:29 ` [PATCH v3 6/7] x86/alternatives: use temporary mm for text poking Nadav Amit
2018-11-05 13:19 ` Peter Zijlstra
2018-11-05 13:30 ` Peter Zijlstra
2018-11-05 18:04 ` Nadav Amit
2018-11-06 8:20 ` Peter Zijlstra
2018-11-06 13:11 ` Peter Zijlstra
2018-11-06 18:11 ` Nadav Amit
2018-11-06 19:08 ` Peter Zijlstra
2018-11-02 23:29 ` [PATCH v3 7/7] x86/alternatives: remove text_poke() return value Nadav Amit
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=20181105133347.GA22485@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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