[PATCH] UML/x86_64

[PATCH] UML/x86_64

[Jeff Dike]

UML has been ported to x86_64.  The patch for 2.6.4 is available at
	http://www.user-mode-linux.org/mirror/uml-patch-x86-64-2.6.4.bz2

Note that this is separate from the 2.6.4 UML patch, and must be
applied to a 2.6.4 + uml-patch-2.6.4 tree.  It will remain separate
until I get it all merged cleanly into my tree.  At that point, the
separate x86_64 patch will disappear.

This patch is fairly nasty in places, and the build is also fairly
unclean, so avert your eyes if you are squeamish.  This will get
better as I merge it into my pool.

The nastiness aside, it does build and you do get a robust UML.

My thanks go to PathScale (pathscale.com) for sponsoring this work and
providing access to hardware to make it possible.

Finally, as I do the merge (and afterwards), I need access to an
Opteron to make sure I don't break this port.  So, if anyone has such
a box that I can have access to, let me know.

				Jeff

[uml-devel] Re: [PATCH] UML/x86_64

[Martin Honermeyer]

Hi Jeff,

thanks for your work! I just tried the patch on my AMD64 machine. "make
linux ARCH=um" fails with

  CC      arch/um/kernel/ksyms.o
arch/um/kernel/ksyms.c:91: error: `dump_thread' undeclared here (not in a
function)
arch/um/kernel/ksyms.c:91: error: initializer element is not constant
arch/um/kernel/ksyms.c:91: error: (near initialization for
`__ksymtab_dump_thread.value')
arch/um/kernel/ksyms.c:91: error: __ksymtab_dump_thread causes a section
type conflict
make[1]: *** [arch/um/kernel/ksyms.o] Error 1


When commenting out that line in arch/um/kernel/ksyms.c and disabling module
support in the kernel configuration, it works! So, just a little correction
to your patch. Now I'll try and see if it works ;)


Greetings,
Martin


Jeff Dike wrote:

> UML has been ported to x86_64.  The patch for 2.6.4 is available at
> http://www.user-mode-linux.org/mirror/uml-patch-x86-64-2.6.4.bz2
> 
> Note that this is separate from the 2.6.4 UML patch, and must be
> applied to a 2.6.4 + uml-patch-2.6.4 tree.  It will remain separate
> until I get it all merged cleanly into my tree.  At that point, the
> separate x86_64 patch will disappear.
> 
> This patch is fairly nasty in places, and the build is also fairly
> unclean, so avert your eyes if you are squeamish.  This will get
> better as I merge it into my pool.
> 
> The nastiness aside, it does build and you do get a robust UML.
> 
> My thanks go to PathScale (pathscale.com) for sponsoring this work and
> providing access to hardware to make it possible.
> 
> Finally, as I do the merge (and afterwards), I need access to an
> Opteron to make sure I don't break this port.  So, if anyone has such
> a box that I can have access to, let me know.
> 
> Jeff





-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel