From: Andrew Morton <akpm@zip.com.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] per-cpu areas for 2.5.3-pre6
Date: Tue, 29 Jan 2002 01:22:30 -0800 [thread overview]
Message-ID: <3C5669D6.B81E0B4@zip.com.au> (raw)
In-Reply-To: <E16VU8j-0006Hm-00@wagner.rustcorp.com.au>
Rusty Russell wrote:
>
> This patch introduces the __per_cpu_data tag for data, and the
> per_cpu() & this_cpu() macros to go with it.
>
> This allows us to get rid of all those special case structures
> springing up all over the place for CPU-local data.
Am I missing something? smp_init() is called quite late in
the boot process, and if any code touches per-cpu data before
this, it'll get a null pointer deref, won't it?
You could possibly do:
unsigned long __per_cpu_offset[NR_CPUS] = { (unsigned long *)&__per_cpu_start, };
which takes care of the boot processor. You lose the ability
to put statically initialised data into the per-cpu area, but
that's not too bad.
Also the boot processor won't be able to initialise stuff which
belongs to other CPUs.
Or the whole thing needs to be moved super-early into the boot
process.
Or I missed something :)
-
next prev parent reply other threads:[~2002-01-29 9:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 9:01 [PATCH] per-cpu areas for 2.5.3-pre6 Rusty Russell
2002-01-29 9:22 ` Andrew Morton [this message]
2002-01-29 22:09 ` Rusty Russell
2002-01-29 22:21 ` Andrew Morton
2002-01-30 0:48 ` Rusty Russell
2002-01-30 0:49 ` Andrew Morton
2002-01-30 2:00 ` Rusty Russell
2002-01-30 2:12 ` Linus Torvalds
2002-01-30 4:13 ` Rusty Russell
2002-01-30 8:22 ` Richard Henderson
2002-01-30 22:45 ` Rusty Russell
2002-01-31 5:49 ` Richard Henderson
2002-02-01 8:56 ` Rusty Russell
2002-02-01 16:52 ` Richard Henderson
2002-01-29 23:17 ` Oliver Xymoron
2002-01-29 23:36 ` Linus Torvalds
2002-01-30 0:20 ` Oliver Xymoron
2002-01-30 0:44 ` Rusty Russell
2002-01-30 7:00 ` Oliver Xymoron
2002-01-30 19:43 ` Oliver Xymoron
2002-01-30 23:00 ` Rusty Russell
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=3C5669D6.B81E0B4@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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