Re: [Devel] Re: [RFC] Virtualization steps

[Eric W. Biederman]

Andi Kleen <ak@xxxxxxx> writes:

> Kirill Korotaev <dev@xxxxx> writes:
>> 
>> -------------- cut ---------------
>> Changing PAGE_OFFSET this way would break at least Valgrind (the latest
>> release 3.1.0 by default is statically linked at address 0xb0000000, and
>> PIE support does not seem to be present in that release).  I remember
>> that similar changes were also breaking Lisp implementations (cmucl,
>> sbcl), however, I am not really sure about this.
>> -------------- cut ---------------
>
> valgrind only breaks when you decrease TASK_SIZE to 2GB, not when you
> enlarge it. In general 2GB VM breaks a lot of apps, that is why
> the new CONFIGs that were added for this were a very bad idea imho.
>
> Obviously the x86-64 kernel doesn't support such things.
>
>> Also, why would one expect 4GB of VM on x86-64 if normally have 3GB on
>> i686? Anyway, as it is tunable, people can select which one they
>> prefer.
>
> Because near all programs that need can actually take advance of it.

So back to the core aim of this thread.

i386 -> x86_64: 32bit migration should work, but may be a little
confusing with the increase in VM space.  (I wonder how this
interacts with the kernels vdso).  

x86_64 -> i386 is likely to use addresses between 3GB and 4GB
and thus the migration probably will not work.  Unless the VM
accessible to user space is capped at 3G.

Odd.  But address space layout looks like one of the easiest migraion
problem to solve.

Eric

-
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/