Skip to contentSkip to conversation

CONFIG_64_BIT

DISCUSSION Matthew Wilcox 3 participants 4 messages Sep 2, 2003 – Sep 3, 2003 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 20030902143424.GO13467@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel

#1 lore raw
Quoted 8 lines · Matthew Wilcox

What do people think of CONFIG_64_BIT? It saves us from using !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or the X86_64 people deciding their architecture is more important.

I also considered CONFIG_ILP32 vs CONFIG_LP64 (since that's the real problem with, eg, megaraid), but that requires more explanation and offers people several ways to get it wrong (should I depend on ILP32 or !LP64?)

At least for code BITS_PER_LONG == 64 is already good enough.

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.

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

Quoted 8 lines · Matthew Wilcox

What do people think of CONFIG_64_BIT? It saves us from using !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or the X86_64 people deciding their architecture is more important.

I also considered CONFIG_ILP32 vs CONFIG_LP64 (since that's the real problem with, eg, megaraid), but that requires more explanation and offers people several ways to get it wrong (should I depend on ILP32 or !LP64?)

At least for code BITS_PER_LONG == 64 is already good enough.

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.

-Andi

#2 lore raw
Quoted 8 lines · Andi Kleen
Quoted 2 lines · Matthew Wilcox

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.

Signature · 8 lines
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Quoted 8 lines · Andi Kleen
Quoted 2 lines · Matthew Wilcox

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.

Signature · 3 lines
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
#3 lore raw
Quoted 11 lines · On Tue, 2 Sep 2003 18:44:36 +0100 Matthew Wilcox <[email protected]> wrote:
Quoted 8 lines · Andi Kleen
Quoted 2 lines · Matthew Wilcox

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Quoted 11 lines · On Tue, 2 Sep 2003 18:44:36 +0100 Matthew Wilcox <[email protected]> wrote:
Quoted 8 lines · Andi Kleen
Quoted 2 lines · Matthew Wilcox

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

#4 lore raw
Quoted 3 lines · Andi Kleen

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.

I2O is currently unmaintained. I fixed some of the DMA issues but there are still a few bits of code that pass pointers in 32bit slots rather than using array indices.