From: Jamie Lokier <jamie@shareable.org>
To: Andre Przywara <andre.przywara@amd.com>
Cc: kvm@vger.kernel.org, avi@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] introduce kvm64 CPU
Date: Sat, 22 Aug 2009 02:45:15 +0100 [thread overview]
Message-ID: <20090822014515.GA23926@shareable.org> (raw)
In-Reply-To: <4A8EADC9.3090106@amd.com>
Andre Przywara wrote:
> If you happen to stuck with 32bit
> (pity you!) then I agree that a kvm32 would be nice to have.
> Will think about it...
I know that 32-bit is a bit slower for some things due to register
pressure (but it's a bit faster for some things due to less memory
needed for pointers), and it's RAM is limited to about 3GB in
practice, which affects some things but is plenty for others.
I know it's a pain for KVM developers to support 32-bit hosts.
And yes, it would be nice to run a 64-bit guest from time to time.
But apart from being a bit slower, is there anything wrong with 32-bit
x86s compared with 64-bit that justifies pity?
The 32-bitness doesn't seem to be a handicap, only perhaps the
expected amount of slowness for a laptop that's 2-3 years old, or a
current netbook, compared with current desktops and servers.
So I'm having a hard time understanding why 32-bitness is considered
bad for KVM - why "pity"? Does it have any other real problems than
not being able to emulate 64-bit guests that I should know about, or
is it just a matter of distaste?
-- Jamie
next prev parent reply other threads:[~2009-08-22 1:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 21:34 [Qemu-devel] [PATCH] introduce kvm64 CPU Andre Przywara
2009-08-21 13:33 ` [Qemu-devel] " Jamie Lokier
2009-08-21 14:23 ` Andre Przywara
2009-08-22 1:45 ` Jamie Lokier [this message]
2009-08-21 15:41 ` Avi Kivity
2009-08-21 16:01 ` Glauber Costa
2009-08-21 21:53 ` Andre Przywara
2009-08-23 9:03 ` Avi Kivity
2009-08-23 13:20 ` Amit Shah
2009-08-21 21:59 ` Andre Przywara
2009-08-23 9:05 ` Avi Kivity
2009-08-23 12:47 ` Jamie Lokier
2009-08-22 1:03 ` Jamie Lokier
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=20090822014515.GA23926@shareable.org \
--to=jamie@shareable.org \
--cc=andre.przywara@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).