From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] fix per-CPU MCA mess and make UP kernels work again
Date: Wed, 26 Jan 2005 17:53:55 +0000 [thread overview]
Message-ID: <200501260953.55632.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <16887.1203.470842.161249@napali.hpl.hp.com>
On Wednesday, January 26, 2005 9:48 am, David Mosberger wrote:
> The patch just removes per_cpu_init() in the non-SMP-case. That would
> have to be changed to be in sync with the contig.c per_cpu_init().
It doesn't totally remove it, I tried to keep the MCA initialization.
per_cpu_init for discontig is different than contig, since the memory has
already been allocated. All we need to do is assign the pointers.
> Perhaps a better solution would be to disassociate the MCA allocations
> from per_cpu_init(). For example, we could have a separate
> alloc_per_cpu_mca_data() in {dis,}contig.c.
That might be clearer.
Jesse
next prev parent reply other threads:[~2005-01-26 17:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 2:47 [patch] fix per-CPU MCA mess and make UP kernels work again David Mosberger
2005-01-26 16:25 ` Jesse Barnes
2005-01-26 17:13 ` Russ Anderson
2005-01-26 17:48 ` David Mosberger
2005-01-26 17:53 ` Jesse Barnes [this message]
2005-01-26 18:05 ` David Mosberger
2005-01-26 18:11 ` Jesse Barnes
2005-01-26 19:01 ` Russ Anderson
2005-01-26 19:23 ` Luck, Tony
2005-01-26 20:07 ` David Mosberger
2005-01-26 21:40 ` Russ Anderson
2005-01-26 21:50 ` David Mosberger
2005-01-26 22:13 ` Luck, Tony
2005-01-26 22:16 ` David Mosberger
2005-01-26 22:19 ` Jesse Barnes
2005-01-26 22:33 ` Luck, Tony
2005-01-27 0:40 ` David Mosberger
2005-01-27 0:55 ` Luck, Tony
2005-01-28 22:54 ` Russ Anderson
2005-02-02 1:04 ` Luck, Tony
2005-02-02 20:25 ` Russ Anderson
2005-02-03 22:48 ` Luck, Tony
2005-02-03 23:48 ` Russ Anderson
2005-02-04 2:09 ` Jack Steiner
2005-02-04 3:00 ` Keith Owens
2005-02-04 16:24 ` Jack Steiner
2005-02-04 16:34 ` Russ Anderson
2005-02-06 15:58 ` Russ Anderson
2005-02-07 22:58 ` Luck, Tony
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=200501260953.55632.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.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