Re: CONFIG_64_BIT

[Andi Kleen]

On Tue, 2 Sep 2003 18:44:36 +0100
Matthew Wilcox <willy@xxxxxxxxxx> wrote:

> On Tue, Sep 02, 2003 at 07:35:11PM +0200, Andi Kleen wrote:
> > Matthew Wilcox <willy@xxxxxxxxxx> writes:
> > 
> > > What do people think of CONFIG_64_BIT?  It saves us from using
> > > !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or
> > 
> > For Kconfigs it may make sense, but is there any Config rule that 
> > checks for all 64bit archs (opposed to checking for specific archs)?
> > I cannot thinkg of any.
> 
> ... that was what the patch added.

It added a symbol that means that, but are there any users for it?

Ok, I2O and ATM and WANPIPE maybe but I assume that both are getting fixed
Still all those are non 64bit safe, so it may be better to have an 
CONFIG_32BIT_ONLY or similar.

-Andi
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
On Tue, 2 Sep 2003 18:44:36 +0100
Matthew Wilcox <willy@xxxxxxxxxx> wrote:

> On Tue, Sep 02, 2003 at 07:35:11PM +0200, Andi Kleen wrote:
> > Matthew Wilcox <willy@xxxxxxxxxx> writes:
> > 
> > > What do people think of CONFIG_64_BIT?  It saves us from using
> > > !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or
> > 
> > For Kconfigs it may make sense, but is there any Config rule that 
> > checks for all 64bit archs (opposed to checking for specific archs)?
> > I cannot thinkg of any.
> 
> ... that was what the patch added.

It added a symbol that means that, but are there any users for it?

Ok, I2O and ATM and WANPIPE maybe but I assume that both are getting fixed
Still all those are non 64bit safe, so it may be better to have an 
CONFIG_32BIT_ONLY or similar.

-Andi
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/