From: Antonio Vargas <windenntw@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: i686 requirements
Date: Fri, 7 Jan 2005 13:34:47 +0100 [thread overview]
Message-ID: <69304d11050107043464a38412@mail.gmail.com> (raw)
Regarding XEN requirements to run, I'd like to know if there is any
important reason to require i686-class cpus (ie: ppro, p2, etc.. and
k7...). In my limited understanding of 386 arch, ppro added
conditional moves and PAE, perhaps even huge-pages (have to check this
one). Is XEN explicitely (as in, used directly on assembler code)
using any of these?
My motivation is getting XEN to run on my (aging) k6 server machine.
Greets anyways :)
--
Greetz, Antonio Vargas aka winden of network
http://wind.codepixel.com/
Las cosas no son lo que parecen, excepto cuando parecen lo que si son.
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next reply other threads:[~2005-01-07 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 12:34 Antonio Vargas [this message]
2005-01-07 14:36 ` i686 requirements Mark Williamson
2005-01-07 14:42 ` Ian Pratt
2005-01-07 18:03 ` Adam Sulmicki
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=69304d11050107043464a38412@mail.gmail.com \
--to=windenntw@gmail.com \
--cc=xen-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.