amd64 questions
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Paul Wagland
Quoted 3 lines · Andi Kleen
A few programs (namely iptables and ipsec tools) need to be used as 64bit programs because the 32bit emulation doesn't work for them. ipchains works though.
I seem to recall reading that the DM based programs also need to be 64 bit, since their 32 bit stuff was also broken?
That was already fixed, but the fix may not be in mainline yet [and I think it broke ppc64 too]. But right, DM has problems too.
Quoted 4 lines
The question I have is whether or not this is a kernel bug that should be fixed? As I understand the DM case, fixing it so that 32bit works, then breaks the 64bit interfaces, requiring re-compiles of the DM programs.
It is a subsystem bug really. These subsystems were all designed to not require emulation, but the designers weren't aware of all the requirements for this and broke it for AMD64/IA64. Unfortunately the interfaces were done in a way that it would be very complicated and a lot of work to write an emulation layer, because they're extremly emulation unfriendly. Maybe it would be still possible to write an emulation layer, but easier is it to just use static 64bit executables or hacked 32bit executables.
I don't have any plans to write emulation layers for such hopeless cases on my own, but just declared these subsystems as broken.
The problem is always the long long alignment. AMD64/IA64 have different alignment for long long than i386. The emulation was originally tested on some RISC port, where the alignment is the same.
-Andi
Quoted 3 lines · Andi Kleen
The problem is always the long long alignment. AMD64/IA64 have different alignment for long long than i386. The emulation was originally tested on some RISC port, where the alignment is the same.
What about a compiler flag to emit i386 code with the more strenuous long long alignment?
Chris
Quoted 8 lines · Chris Friesen
Quoted 3 lines · Andi Kleen
The problem is always the long long alignment. AMD64/IA64 have different alignment for long long than i386. The emulation was originally tested on some RISC port, where the alignment is the same.
What about a compiler flag to emit i386 code with the more strenuous long long alignment?
That would break other things, glibc uses long long heavily too. The only simple way would be to add the necessary alignment by hand and create a special 32bit on 64bit kernel iptables or ipsec.
-Andi
Quoted 8 lines · Andi Kleen
It is a subsystem bug really. These subsystems were all designed to
not require emulation, but the designers weren't aware of all the
requirements for this and broke it for AMD64/IA64. Unfortunately the
interfaces were done in a way that it would be very complicated and a
lot of work to write an emulation layer, because they're extremly
emulation unfriendly. Maybe it would be still possible to write an
emulation layer, but easier is it to just use static 64bit executables or hacked 32bit executables.
Quoted 4 lines
I don't have any plans to write emulation layers for such hopeless cases on my own, but just declared these subsystems as broken.
So let me get this straight, we can't use LVM with AMD64 under the 2.6 line either? Or we can if we use AMD64 [DM] libraries with a AMD64 kernel? DM = Device Mapper right?
-ryan
Quoted 1 line
So let me get this straight, we can't use LVM with AMD64 under the 2.6
No, you completely misunderstood.
Quoted 2 lines
line either? Or we can if we use AMD64 [DM] libraries with a AMD64 kernel? DM = Device Mapper right?
You can't use Device Mapper with 32bit user tools on a 64bit kernel right now.
-Andi
Quoted 9 lines · Andi Kleen
Quoted 1 line
So let me get this straight, we can't use LVM with AMD64 under the 2.6
No, you completely misunderstood.
Quoted 2 lines
line either? Or we can if we use AMD64 [DM] libraries with a AMD64 kernel? DM = Device Mapper right?
You can't use Device Mapper with 32bit user tools on a 64bit kernel right now.
Well, you can, because that's what I'm doing on this machine. Joe
Thornber posted a patch[1] here a few weeks ago which fixes the problem in a "sealing-wax-and-string" kind of way. It Works For Me(tm), which is about all you can say about it -- it's not the prettiest piece of code, even to my non-kernel eyes. :)
Hugo.
[1] http://marc.theaimsgroup.com/?l=linux-kernel&m=107908531723751&w=2
Signature · 3 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Ceci est un travail pour l'Australien. --- Quoted 4 lines · Hugo Mills
Quoted 3 lines · Andi Kleen
Quoted 2 lines
line either? Or we can if we use AMD64 [DM] libraries with a AMD64 kernel? DM = Device Mapper right?
Quoted 8 lines
Quoted 2 lines
You can't use Device Mapper with 32bit user tools on a 64bit kernel right now.
Well, you can, because that's what I'm doing on this machine. Joe
Thornber posted a patch[1] here a few weeks ago which fixes the problem in a "sealing-wax-and-string" kind of way. It Works For Me(tm), which is about all you can say about it -- it's not the prettiest piece of code, even to my non-kernel eyes. :)
Ah, yes, but you missed the bit slightly later in the thread where Andi requested that this not be added to the kernel since it would then break all currently existing 64bit DM user tools. Newly compiled ones would, of course, work, but you introduce a DM user tool versioning problem, where the old 64 bit utils need to be used with old kernels, and the new tools need to be used with the new kernels. As far as I understood, this is the "official" line for the mainstream kernel. It is my hope that the disties all decide to use Thornbers patch when they do release, but only time will tell...
Of course, this also means that you can't "dual boot" your linux partition based if you use DM on the fact that you cannot use the same DM tools. For this reason I would like the problem to be fixed in the mainline kernel, but that is primarily a selfish concern ;-) as it makes my own migration harder.
Cheers,
Paul
Quoted 16 lines · Paul Wagland
Quoted 4 lines · Hugo Mills
Quoted 3 lines · Andi Kleen
Quoted 2 lines
line either? Or we can if we use AMD64 [DM] libraries with a AMD64 kernel? DM = Device Mapper right?
Quoted 8 lines
Quoted 2 lines
You can't use Device Mapper with 32bit user tools on a 64bit kernel right now.
Well, you can, because that's what I'm doing on this machine. Joe
Thornber posted a patch[1] here a few weeks ago which fixes the problem in a "sealing-wax-and-string" kind of way. It Works For Me(tm), which is about all you can say about it -- it's not the prettiest piece of code, even to my non-kernel eyes. :)
Quoted 9 lines
Ah, yes, but you missed the bit slightly later in the thread where Andi requested that this not be added to the kernel since it would then break all currently existing 64bit DM user tools. Newly compiled ones would, of course, work, but you introduce a DM user tool versioning problem, where the old 64 bit utils need to be used with old kernels, and the new tools need to be used with the new kernels. As far as I understood, this is the "official" line for the mainstream kernel. It is my hope that the disties all decide to use Thornbers patch when they do release, but only time will tell...
Sorry, I probably wasn't making myself clear.
I'm well aware of the issues surrounding this patch, and the fact
that it's never going to get into mainline kernels. However, it _does_ allow you to use DM with 32-bit user-space + 64-bit kernel, which was my only point.
Hugo.
Signature · 3 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- The English language has the mot juste for every occasion. ---
Quoted 7 lines · Andi Kleen
Quoted 3 lines
So let me get this straight, we can't use LVM with AMD64 under the 2.6
No, you completely misunderstood.
It was ambiguous, I saw more than one valid interpretation.
Quoted 8 lines
Quoted 3 lines
line either? Or we can if we use AMD64 [DM] libraries with a AMD64 kernel? DM = Device Mapper right?
You can't use Device Mapper with 32bit user tools on a 64bit kernel right now.
Which doesn't say we can use 64bit user tools with a 64bit kernel, but I assume this is what you mean.
-ryan