public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Kropelin <akropel1@rochester.rr.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Frank Davis <fdavis@si.rr.com>,
	linux-kernel@vger.kernel.org, davej@suse.de
Subject: Re: 2.5.8-dj1 : arch/i386/kernel/smpboot.c error
Date: Wed, 17 Apr 2002 08:30:44 -0400	[thread overview]
Message-ID: <20020417123044.GA8833@www.kroptech.com> (raw)
In-Reply-To: <20020417024707.GA24105@www.kroptech.com> <2635845054.1018994347@[10.10.2.3]>

On Tue, Apr 16, 2002 at 09:59:08PM -0700, Martin J. Bligh wrote:
> xquad_portio is indeed only for CONFIG_MULTIQUAD. However, you
> shouldn't need the #ifdef's in the code to make this work -
> clustered_apic_mode isn't a variable at all, it's a magic
> trick that's actually 1 or 0 depending on CONFIG_MULTIQUAD.
> 
> Look at 2.5.8 virgin, it has the same code.

Not quite.

As I said, -dj has an optimization in asm-i386/io.o:

> #ifdef CONFIG_MULTIQUAD
> extern void *xquad_portio;    /* Where the IO area was mapped */
> #else
> #define xquad_portio (0)
> #endif

So the preprocessed smpboot.c contains gems like:

> void *(0) = ((void *)0);

...and...

> (0) = ioremap (0xfe400000,
>         numnodes * 0x80000);

Even though clustered_apic_mode is 0, the compiler still complains
about the second one and the first one doesn't depend on
clustered_apic_mode at all.

I don't like spreading around more #ifdef's, but the spirit of the
changes seemed to be to get rid of the declaration of xquad_portio
when !CONFIG_MULTIQUAD. Suggestions for improvement welcome.

--Adam


  reply	other threads:[~2002-04-17 12:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16  2:19 2.5.8-dj1 : arch/i386/kernel/smpboot.c error Frank Davis
2002-04-17  2:47 ` Adam Kropelin
2002-04-17  4:59   ` Martin J. Bligh
2002-04-17 12:30     ` Adam Kropelin [this message]
2002-04-17 12:40       ` Adam Kropelin
2002-04-17 15:28       ` Martin J. Bligh
2002-04-17 19:17         ` Adam Kropelin
2002-04-17 19:31           ` Rick Stevens
2002-04-17 20:53             ` Martin J. Bligh
2002-04-17 20:40               ` Adam Kropelin
2002-04-17 21:17                 ` Rick Stevens
2002-04-17 21:49                   ` Adam Kropelin
2002-04-17 22:06                     ` J.A. Magallon
2002-04-18  0:34                 ` Martin J. Bligh
2002-04-18  2:16                   ` Stevie O
2002-04-17 20:49           ` Martin J. Bligh
2002-04-17 22:56         ` Stevie O
2002-04-18  0:29           ` Martin J. Bligh
2002-04-21 13:37 ` [PATCH] " Brian Gerst

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=20020417123044.GA8833@www.kroptech.com \
    --to=akropel1@rochester.rr.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=davej@suse.de \
    --cc=fdavis@si.rr.com \
    --cc=linux-kernel@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