From: Antoine Martin <antoine@nagafix.co.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] skas3 (almost) works on amd64?
Date: Mon, 19 Dec 2005 18:41:02 +0000 [thread overview]
Message-ID: <1135017662.15991.136.camel@ant.internal> (raw)
In-Reply-To: <200512191723.19829.blaisorblade@yahoo.it>
> And you saying "yes it works, I know this".
I can't remember! And I thought only my short term memory was bad... ;)
> SKAS64 support is implemented in the SKAS patch, but IIRC not in the guest
> kernel - there are just a few things to fix up (for instance
> using /proc/mm64), but I gave up as I hadn't found a solution to SKAS32-on-64
> problems, and the changes were boring to do, and impossible to get right
> without a testing possibility.
I suppose this isn't something I can help with?
That's a shame because I get the impression that skas3 is still much
faster than skas0... no hard figures though.
Antoine
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-12-19 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200504181134.53390.markc@renta.net>
[not found] ` <1113830263.11747.3.camel@cobra>
[not found] ` <1113841384.12075.6.camel@localhost>
[not found] ` <1113844082.11747.33.camel@cobra>
2005-12-18 19:03 ` [uml-devel] skas3 (almost) works on amd64? Antoine Martin
2005-12-19 16:23 ` Blaisorblade
2005-12-19 18:41 ` Antoine Martin [this message]
2005-12-19 18:49 ` Blaisorblade
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=1135017662.15991.136.camel@ant.internal \
--to=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.