From: Jeff Dike <jdike@addtoit.com>
To: linux-kernel@vger.kernel.org, user-mode-linux-devel@sourceforge.net
Subject: [PATCH] UML/x86_64
Date: Sat, 1 May 2004 13:09:05 -0400 [thread overview]
Message-ID: <20040501170905.GA7655@ccure.user-mode-linux.org> (raw)
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
reply other threads:[~2004-05-01 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040501170905.GA7655@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox