From: Doug Chapman <doug.chapman@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [REGRESSION] Minimize per_cpu reservations patch causes NULL
Date: Tue, 04 Nov 2008 20:35:30 +0000 [thread overview]
Message-ID: <1225830930.13942.10.camel@localhost.localdomain> (raw)
In-Reply-To: <1225830514.13942.8.camel@localhost.localdomain>
On Tue, 2008-11-04 at 15:28 -0500, Doug Chapman wrote:
> It appears the intent of calling per_cpu_scan_finalize() at the
> current
> location is that it needs to be called prior to find_memory(). The
> "Minimize
> per_cpu reservations." patch changes code in arch/ia64/mm/discontig.c
> which
> sets up the per-cpu datastructures to only set those up for CPUs in
> early_cpu_possible_map.
Correction on this bit, it isn't find_memory() it is cpu_init() which
calls per_cpu_init() however the general problem is the same.
- Doug
next prev parent reply other threads:[~2008-11-04 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 20:28 [REGRESSION] Minimize per_cpu reservations patch causes NULL ptr Doug Chapman
2008-11-04 20:35 ` Doug Chapman [this message]
2008-11-04 21:12 ` [REGRESSION] Minimize per_cpu reservations patch causes NULL Luck, Tony
2008-11-04 21:21 ` Doug Chapman
2008-11-05 23:07 ` Doug Chapman
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=1225830930.13942.10.camel@localhost.localdomain \
--to=doug.chapman@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.