From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Mikael Starvik <starvik@axis.com>,
David Howells <dhowells@redhat.com>,
Kyle McMartin <kyle@parisc-linux.org>,
Anton Blanchard <anton@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
William Lee Irwin III <wli@holomorphy.com>,
Andi Kleen <ak@muc.de>, Christian Zankel <chris@zankel.net>,
Philippe Elie <phil.el@wanadoo.fr>,
Nathan Scott <nathans@sgi.com>, Jens Axboe <axboe@suse.de>,
linux-arch@vger.kernel.org, Eric Dumazet <dada1@cosmosbay.com>
Subject: Re: percpu data changes
Date: Fri, 3 Feb 2006 10:51:48 +0100 [thread overview]
Message-ID: <200602031051.49816.ak@suse.de> (raw)
In-Reply-To: <20060203011748.6fe3fee3.akpm@osdl.org>
On Friday 03 February 2006 10:17, Andrew Morton wrote:
>
> It seems that powerpc has gone and changed their implementation of percpu
> data so that there is no memory allocated for not-possible CPUs. To save a
> bit of RAM.
>
> This means that any code which does
>
> for (i = 0; i < NR_CPUS; i++)
> touch(percpudata(i))
>
> will explode on powerpc.
It also explodes since some time on x86-64.
But I added a workaround now (or rather sent one and Linus dropped it)
to point the not possible CPUs to the reference data and not free it.
With that violating that protocol is mostly harmless.
Later the plan was to point it to unmapped data to catch all users.
-Andi
next prev parent reply other threads:[~2006-02-03 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 9:17 percpu data changes Andrew Morton
2006-02-03 9:18 ` Andrew Morton
2006-02-03 9:35 ` Andrew Morton
2006-02-03 9:38 ` David S. Miller
2006-02-03 9:36 ` William Lee Irwin III
2006-02-03 9:40 ` David S. Miller
2006-02-03 9:51 ` Andi Kleen [this message]
2006-02-03 11:01 ` Eric Dumazet
2006-02-03 11:07 ` Andi Kleen
2006-02-03 15:36 ` Kyle McMartin
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=200602031051.49816.ak@suse.de \
--to=ak@suse.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=axboe@suse.de \
--cc=benh@kernel.crashing.org \
--cc=chris@zankel.net \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kyle@parisc-linux.org \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=paulus@samba.org \
--cc=phil.el@wanadoo.fr \
--cc=schwidefsky@de.ibm.com \
--cc=starvik@axis.com \
--cc=wli@holomorphy.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