public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jack Steiner <steiner@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] cpumask: Change cpumask_of_cpu to use cpumask_of_cpu_map V2
Date: Sat, 26 Jul 2008 16:41:33 +0200	[thread overview]
Message-ID: <20080726144133.GA27011@elte.hu> (raw)
In-Reply-To: <20080725012128.805332000@polaris-admin.engr.sgi.com>


* Mike Travis <travis@sgi.com> wrote:

> V2: Use Rusty's cpumask initializer to statically initialize the
>     cpumask_of_cpu_map[].  In addition, create this map in the init
>     data section using NR_CPUS but replace it during boot up with
>     one sized by nr_cpu_ids (num possible cpus).
> 
> The following patch is submitted to resolve this problem...
> 
> (Based on tip/master.  I will generate a linux-next version if 
> requested since it now has generic code that will be executed for 
> non-x86 arch's.)

i've applied it to tip/cpus4096 and started testing it. This is the 
topic where the problem originates from, so we can reuse it for 
linux-next.

	Ingo

  parent reply	other threads:[~2008-07-26 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  1:21 [PATCH 0/3] cpumask: Change cpumask_of_cpu to use cpumask_of_cpu_map V2 Mike Travis
2008-07-25  1:21 ` [PATCH 1/3] cpumask: Make cpumask_of_cpu_map generic Mike Travis
2008-07-25  1:21 ` [PATCH 2/3] cpumask: Put cpumask_of_cpu_map in the initdata section Mike Travis
2008-07-25  1:21 ` [PATCH 3/3] cpumask: Change cpumask_of_cpu_ptr to use new cpumask_of_cpu Mike Travis
2008-07-26 14:41 ` Ingo Molnar [this message]
2008-07-26 14:49   ` [PATCH 0/3] cpumask: Change cpumask_of_cpu to use cpumask_of_cpu_map V2 Ingo Molnar

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=20080726144133.GA27011@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=steiner@sgi.com \
    --cc=travis@sgi.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