From: Daniel Walker <dwalker@fifo99.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Mel Gorman <mel@csn.ul.ie>, Nick Piggin <npiggin@suse.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>,
heiko.carstens@de.ibm.com, sachinp@in.ibm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Tejun Heo <tj@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH 1/3] powerpc: Allocate per-cpu areas for node IDs for SLQB to use as per-node areas
Date: Mon, 21 Sep 2009 10:29:41 -0700 [thread overview]
Message-ID: <1253554181.9654.238.camel@desktop> (raw)
In-Reply-To: <20090921102418.4692d62c.rdunlap@xenotime.net>
On Mon, 2009-09-21 at 10:24 -0700, Randy Dunlap wrote:
> On Mon, 21 Sep 2009 10:17:52 -0700 Daniel Walker wrote:
>
> > On Mon, 2009-09-21 at 17:10 +0100, Mel Gorman wrote:
> > > SLQB uses DEFINE_PER_CPU to define per-node areas. An implicit
> > > assumption is made that all valid node IDs will have matching valid CPU
> > > ids. In memoryless configurations, it is possible to have a node ID with
> > > no CPU having the same ID. When this happens, a per-cpu are is not
> > > created and the value of paca[cpu].data_offset is some random value.
> > > This is later deferenced and the system crashes after accessing some
> > > invalid address.
> > >
> > > This patch hacks powerpc to allocate per-cpu areas for node IDs that
> > > have no corresponding CPU id. This gets around the immediate problem but
> > > it should be discussed if there is a requirement for a DEFINE_PER_NODE
> > > and how it should be implemented.
> > >
> > > Signed-off-by: Mel Gorman <mel@csn.ul.ie>
> > > ---
> > > arch/powerpc/kernel/setup_64.c | 20 ++++++++++++++++++++
> > > 1 files changed, 20 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
> > > index 1f68160..a5f52d4 100644
> > > --- a/arch/powerpc/kernel/setup_64.c
> > > +++ b/arch/powerpc/kernel/setup_64.c
> > > @@ -588,6 +588,26 @@ void __init setup_per_cpu_areas(void)
> > > paca[i].data_offset = ptr - __per_cpu_start;
> > > memcpy(ptr, __per_cpu_start, __per_cpu_end - __per_cpu_start);
> > > }
> > > +#ifdef CONFIG_SLQB
> > > + /*
> > > + * SLQB abuses DEFINE_PER_CPU to setup a per-node area. This trick
> > > + * assumes that ever node ID will have a CPU of that ID to match.
> > > + * On systems with memoryless nodes, this may not hold true. Hence,
> > > + * we take a second pass initialising a "per-cpu" area for node-ids
> > > + * that SLQB can use
> > > + */
> >
> > Very trivial, but there's a little trailing whitespace in the first line
> > of the comment (checkpatch warns on it.) You also spelled initializing
> > wrong.
>
> re: spelling. Not really. Think internationally.
Yeah, I realized that after I sent it .. So misspelled in the American
sense I guess.
Daniel
--
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>
next prev parent reply other threads:[~2009-09-21 17:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 16:10 [RFC PATCH 0/3] Fix SLQB on memoryless configurations V2 Mel Gorman
2009-09-21 16:10 ` [PATCH 1/3] powerpc: Allocate per-cpu areas for node IDs for SLQB to use as per-node areas Mel Gorman
2009-09-21 17:17 ` Daniel Walker
2009-09-21 17:24 ` Randy Dunlap
2009-09-21 17:29 ` Daniel Walker [this message]
2009-09-21 17:42 ` Mel Gorman
2009-09-22 0:01 ` Tejun Heo
2009-09-22 9:32 ` Mel Gorman
2009-09-21 16:10 ` [PATCH 2/3] slqb: Record what node is local to a kmem_cache_cpu Mel Gorman
2009-09-21 16:10 ` [PATCH 3/3] slqb: Allow SLQB to be used on PPC Mel Gorman
2009-09-22 9:30 ` Heiko Carstens
2009-09-22 9:32 ` Mel Gorman
2009-09-21 17:46 ` [RFC PATCH 0/3] Fix SLQB on memoryless configurations V2 Mel Gorman
2009-09-21 17:54 ` Christoph Lameter
2009-09-21 18:05 ` Pekka Enberg
2009-09-21 18:07 ` Mel Gorman
2009-09-21 18:17 ` Christoph Lameter
2009-09-22 10:05 ` Mel Gorman
2009-09-22 10:21 ` Pekka Enberg
2009-09-22 10:24 ` Mel Gorman
2009-09-22 5:03 ` Sachin Sant
2009-09-22 10:07 ` Mel Gorman
2009-09-22 12:55 ` Mel Gorman
2009-09-22 13:05 ` Sachin Sant
2009-09-22 13:20 ` Mel Gorman
[not found] ` <363172900909220629j2f5174cbo9fe027354948d37@mail.gmail.com>
2009-09-22 13:38 ` Mel Gorman
2009-09-22 23:07 ` Christoph Lameter
2009-09-22 0:00 ` Benjamin Herrenschmidt
2009-09-22 0:19 ` David Rientjes
2009-09-22 6:30 ` Christoph Lameter
2009-09-22 7:59 ` David Rientjes
2009-09-22 8:11 ` Benjamin Herrenschmidt
2009-09-22 8:44 ` David Rientjes
2009-09-22 15:26 ` Mel Gorman
2009-09-22 17:31 ` David Rientjes
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=1253554181.9654.238.camel@desktop \
--to=dwalker@fifo99.com \
--cc=benh@kernel.crashing.org \
--cc=cl@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
--cc=sachinp@in.ibm.com \
--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).