From: Mel Gorman <mgorman@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: numa: Initialse numa balancing after jump label initialisation
Date: Tue, 28 Jan 2014 08:49:11 +0000 [thread overview]
Message-ID: <20140128084911.GM4963@suse.de> (raw)
In-Reply-To: <20140127144336.6e9428d317bc2f476fa8de3e@linux-foundation.org>
On Mon, Jan 27, 2014 at 02:43:36PM -0800, Andrew Morton wrote:
> On Mon, 27 Jan 2014 15:51:27 +0000 Mel Gorman <mgorman@suse.de> wrote:
>
> > The command line parsing takes place before jump labels are initialised which
> > generates a warning if numa_balancing= is specified and CONFIG_JUMP_LABEL
> > is set. On older kernls before commit c4b2c0c5 (static_key: WARN on
> > usage before jump_label_init was called) the kernel would have crashed.
> > This patch enables automatic numa balancing later in the initialisation
> > process if numa_balancing= is specified.
> >
> > ...
> >
> > @@ -2666,9 +2666,14 @@ static void __init check_numabalancing_enable(void)
> > if (IS_ENABLED(CONFIG_NUMA_BALANCING_DEFAULT_ENABLED))
> > numabalancing_default = true;
> >
> > + /* Parsed by setup_numabalancing. override == 1 enables, -1 disables */
> > + if (numabalancing_override)
> > + set_numabalancing_state(numabalancing_override == 1);
> > +
> > if (nr_node_ids > 1 && !numabalancing_override) {
> > - printk(KERN_INFO "Enabling automatic NUMA balancing. "
> > - "Configure with numa_balancing= or sysctl");
> > + printk(KERN_INFO "%s automatic NUMA balancing. "
> > + "Configure with numa_balancing= or sysctl",
> > + numabalancing_default ? "Enabling" : "Disabling");
> > set_numabalancing_state(numabalancing_default);
> > }
> > }
>
> Current mainline is a bit different from this:
>
> printk(KERN_INFO "Enabling automatic NUMA balancing. "
> "Configure with numa_balancing= or the kernel.numa_balancing sysctl");
>
> So this won't apply as-is to -stable.
>
That's ok.
> I assume you suggested the -stable backport to fix the
> it-crashes-before-c4b2c0c5 thing, so it isn't really needed in 3.12.x.
>
I am recommending this patch for -stable because 3.12.x crashes. c4b2c0c5
prevents a crash but it is still the case that the parameter is not handled
properly so backporting c4b2c0c5 is not a suitable alternative.
> Or something. Please sort all that out when Greg comes back with
> a hey-that-didnt-apply.
I will.
--
Mel Gorman
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-01-28 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 15:51 Mel Gorman
2014-01-27 22:12 ` Rik van Riel
2014-01-27 22:43 ` Andrew Morton
2014-01-28 8:49 ` Mel Gorman [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=20140128084911.GM4963@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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