mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>, Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jack Steiner <steiner@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] cpumask: Change cpumask_of_cpu to use cpumask_of_cpu_map V2
Date: Thu, 24 Jul 2008 18:21:28 -0700	[thread overview]
Message-ID: <20080725012128.805332000@polaris-admin.engr.sgi.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3545 bytes --]


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.)

> * Rusty Russell <rusty@rustcorp.com.au> wrote:
> 
> >> > > I wouldn't mind it at all, and since it's almost always calling a 
> >> > > function that requires a cpumask_t pointer (like the cpu_* ops or 
> >> > > set_cpus_allowed_ptr) then there shouldn't be too many "pointer 
> >> > > dereference" penalties.  I'm just always a bit hesitant to make too 
> >> > > many generic changes since I have only x86 and ia64 machines to test 
> >> > > with.
> > > 
> > > The simple version is just a static array of [NR_CPUS] cpumask_t's.  
> > > Do that, with an override for smarter archs?
> > > 
> > > I really REALLY prefer that over the fairly tortuous macros.
> 
> a fresh commit in -git has exposed the topology.h mess - see the hack 
> below. We now have diverging versions of topology_core_siblings() 
> semantics - that sure cannot be right. Mike?
> 
> 	Ingo
> 
> ------->
> commit 695a6b456307455a10059512208e8ed0d376ecd3
> Author: Ingo Molnar <mingo@elte.hu>
> Date:   Wed Jul 23 13:19:44 2008 +0200
> 
>     topology: work around topology_core_siblings() breakage
>     
>     work around:
>     
>     drivers/net/sfc/efx.c: In function â??efx_probe_interrupts':
>     drivers/net/sfc/efx.c:845: error: lvalue required as unary â??&' operand
>     
>     the topology API is a mess right now ...
>     
>     Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---

Signed-off-by: Mike Travis <travis@sgi.com>

---
The following cross built successfully:

    x86_64-default
    x86_64-single
    x86_64-8psmp
    x86_64-debug
    x86_64-numa
    i386-default
    i386-single
    i386-smp
    ia64-sn2
    ia64-default
    ia64-nosmp
    ia64-zx1
    s390-default
    arm-default
    sparc-default
    sparc64-default
    sparc64-smp
    mips-default
    ppc-pmac32

These had problems:

    ppc-iseries
	 Build failed Wed Jul 23 10:10:10 PDT 2008
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
    ppc64
	 Build failed Wed Jul 23 10:10:19 PDT 2008
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
    ppc-pseries
	 Build failed Wed Jul 23 10:10:29 PDT 2008
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
    ppc-smp
	 Build failed Wed Jul 23 10:12:03 PDT 2008
	  CC      drivers/scsi/scsi_error.o
	  BOOTCC  arch/powerpc/boot/libfdt/fdt_strerror.o
	make[1]: *** [arch/powerpc/boot/uImage] Error 127
    ps3_defconfig
	 Build failed Wed Jul 23 10:12:18 PDT 2008
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
    powerpc-allmodconfig
	 Build failed Wed Jul 23 10:12:31 PDT 2008
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration
	:0: error: -m64 not supported in this configuration

-- 

             reply	other threads:[~2008-07-25  1:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  1:21 Mike Travis [this message]
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 ` [PATCH 0/3] cpumask: Change cpumask_of_cpu to use cpumask_of_cpu_map V2 Ingo Molnar
2008-07-26 14:49   ` 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=20080725012128.805332000@polaris-admin.engr.sgi.com \
    --to=travis@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=steiner@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

all inboxes | Powered by JetHome®