From: Tal Shorer <tal.shorer@gmail.com>
To: tj@kernel.org
Cc: sfr@canb.auug.org.au, tglx@linutronix.de, mingo@elte.hu,
hpa@zytor.com, peterz@infradead.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, tal.shorer@gmail.com,
frederic@kernel.org
Subject: [PATCH v3 1/2] main: kernel_start: move housekeeping_init() before workqueue_init_early()
Date: Fri, 3 Nov 2017 17:27:49 +0200 [thread overview]
Message-ID: <1509722870-27618-1-git-send-email-tal.shorer@gmail.com> (raw)
In-Reply-To: <20171103135911.GS3252168@devbig577.frc2.facebook.com>
This is needed in order to allow the unbound workqueue to take
housekeeping cpus into accounty
Signed-off-by: Tal Shorer <tal.shorer@gmail.com>
---
init/main.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/init/main.c b/init/main.c
index 4610c99..af6ecd0 100644
--- a/init/main.c
+++ b/init/main.c
@@ -591,6 +591,12 @@ asmlinkage __visible void __init start_kernel(void)
radix_tree_init();
/*
+ * Set up housekeeping before setting up workqueues to allow the unbound
+ * workqueue to take non-housekeeping into account.
+ */
+ housekeeping_init();
+
+ /*
* Allow workqueue creation and work item queueing/cancelling
* early. Work item execution depends on kthreads and starts after
* workqueue_init().
@@ -607,7 +613,6 @@ asmlinkage __visible void __init start_kernel(void)
early_irq_init();
init_IRQ();
tick_init();
- housekeeping_init();
rcu_init_nohz();
init_timers();
hrtimers_init();
--
2.7.4
next prev parent reply other threads:[~2017-11-03 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 3:34 linux-next: build failure after merge of the workqueues tree Stephen Rothwell
2017-11-03 13:59 ` Tejun Heo
2017-11-03 15:27 ` Tal Shorer [this message]
2017-11-03 15:27 ` [PATCH v3 2/2] workqueue: respect isolated cpus when queueing an unbound work Tal Shorer
2017-11-06 15:26 ` Tejun Heo
2017-11-27 16:57 ` Tejun Heo
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=1509722870-27618-1-git-send-email-tal.shorer@gmail.com \
--to=tal.shorer@gmail.com \
--cc=frederic@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).