From: Jeremy Fitzhardinge <jeremy@goop.org>
To: jan.oravec@6com.sk
Cc: xen-devel@lists.xensource.com,
Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: Xen domU support merged into upstream Linux
Date: Mon, 30 Jul 2007 09:14:30 -0700 [thread overview]
Message-ID: <46AE0E66.1070607@goop.org> (raw)
In-Reply-To: <1185810053.13739.11.camel@soyuz.6com.net>
Jan Oravec wrote:
> I tend to believe there are more pre-HVM 64-bit guests than 32-bit
> guests. 64-bit CPUs are mainstream for a few years and 32-bit-only
> server systems are getting old. Almost everyone I know with 64-bit CPUs
> prefers to run 64-bit Linux over 32-bit.
>
> So, I think it is worth to support pre-HVM 64-bit guests.
Well, traditionally 64-bit guests have suffered a particularly steep
performance hit under Xen, so I suspect that a lot of people with 64-bit
hosts are still tending to use 32-bit guests. But I'm just handwaving
really.
J
prev parent reply other threads:[~2007-07-30 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 19:58 Xen domU support merged into upstream Linux Jeremy Fitzhardinge
2007-07-24 17:07 ` Mark Williamson
2007-07-25 0:15 ` Jeremy Fitzhardinge
2007-07-30 15:40 ` Jan Oravec
2007-07-30 16:14 ` Jeremy Fitzhardinge [this message]
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=46AE0E66.1070607@goop.org \
--to=jeremy@goop.org \
--cc=jan.oravec@6com.sk \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.