public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch 0/3] Modify how per_cpu allocations are done. -V8
Date: Tue, 18 Mar 2008 09:40:31 +0000	[thread overview]
Message-ID: <20080318094031.GB18194@sgi.com> (raw)
In-Reply-To: <20080213175519.892353127@attica.americas.sgi.com>

On Mon, Mar 17, 2008 at 07:22:03AM -0500, Robin Holt wrote:
> On Mon, Mar 17, 2008 at 07:12:40AM -0500, holt@sgi.com wrote:
> > This patchset cleans up how per_cpu reservations are done.
> 
> Argh, this should have been a better description and really only
> and RFC instead of a patch.
> 
> I updated the patch to have the early_cpu_possible_mask in both
> the contig and discontig cases.  This allows the mca stack allocator
> to use that for preallocation instead of cpu_possible_map.  In the
> case of !CONFIG_ACPI, the early_cpu_possible_mask = cpu_possible_mask.
> 
> I did find a tiger box (that is the same as a McKinnley SDV, correct?) to
> try this on, but the serial console is messed up on that machine and it
> so I will test this out when I get to the office.  If you get a chance
> first, please let me know if it works.

The machine in question is in fairly bad disrepair.  I believe we will
finally get it booting again today, but it may not be until tomorrow.

Have you had a chance to test this revised patchset on your tiger box?

Thanks,
Robin

  parent reply	other threads:[~2008-03-18  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 17:55 [Patch 0/3] Modify how per_cpu allocations are done holt
2008-02-21 21:08 ` [Patch 0/3] Modify how per_cpu allocations are done. -V7 repost holt
2008-03-17 12:12 ` [Patch 0/3] Modify how per_cpu allocations are done. -V8 holt
2008-03-17 12:22 ` Robin Holt
2008-03-18  9:40 ` Robin Holt [this message]
2008-03-18 17:46 ` Luck, Tony
2008-03-20  1:40 ` Robin Holt
2008-03-31 14:48 ` Robin Holt
2008-04-03 18:42 ` 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=20080318094031.GB18194@sgi.com \
    --to=holt@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