public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix generic build when CONFIG_SMP=n
Date: Tue, 17 Aug 2004 01:10:24 +0000	[thread overview]
Message-ID: <200408161810.24682.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200408131559.59229.jbarnes@engr.sgi.com>

On Sunday, August 15, 2004 8:29 pm, dann frazier wrote:
> On Fri, Aug 13, 2004 at 03:59:59PM -0700, Jesse Barnes wrote:
> > This patch fixes the issues I saw with CONFIG_SMP=n when building a
> > generic kernel with CONFIG_NUMA=y and CONFIG_DISCONTIGMEM=y.  It's still
> > pretty rough, but I'd appreciate comments and testing on other platforms.
> >  The per-cpu fixes are still pretty ugly--I'm sure I'm missing something
> > that would make abstracting out per_cpu(cpu_info, cpu).node_data > > mem_data[node].node_data much nicer looking.
> >
> > Fixing the build of generic kernels w/o CONFIG_NUMA or
> > CONFIG_DISCONTIGMEM is left as an exercise for the reader. :)
>
> Here's the results of some 2.6.8 boot testing:
>
> ---------------------------------------------------------------------------
>-- generic-no-smp-2    generic_defconfig
>     patch?                delta               machine           results
> ---------------------------------------------------------------------------
>-- No               ITANIUM=y                HP i2000            OK
> ---------------------------------------------------------------------------
>-- Yes              ITANIUM=y                HP i2000            OK
> ---------------------------------------------------------------------------
>-- Yes              ITANIUM=y                   N/A         build fails [1]
> SMP=n
> ---------------------------------------------------------------------------
>-- Yes              ITANIUM=y                   N/A         build fails [2]
> SMP=n
>                       CYCLONE=n
> ---------------------------------------------------------------------------
>-- Yes              ITANIUM=y                   N/A              OK SMP=n
>                       CYCLONE=n                HP i2000
>                       SERIAL_SGI_L1_CONSOLE=n
> ---------------------------------------------------------------------------
>-- Yes                                       HP rx2600           OK
> ---------------------------------------------------------------------------
>-- Yes              SMP=n                    HP rx2600           OK
> CYCLONE=n
>                       SERIAL_SGI_L1_CONSOLE=n

I posted fixes for cyclone and the sgi console driver separately.  They should 
get in soon.

Jesse

  parent reply	other threads:[~2004-08-17  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 22:59 [PATCH] fix generic build when CONFIG_SMP=n Jesse Barnes
2004-08-16  3:29 ` dann frazier
2004-08-16 22:23 ` Randy.Dunlap
2004-08-17  1:10 ` Jesse Barnes [this message]
2004-08-24 18:25 ` Jesse Barnes

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=200408161810.24682.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