From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, "J. Mayer" <l_indien@magic.fr>
Subject: Re: [Qemu-devel] Updated >2G memory patch
Date: Sat, 29 Sep 2007 23:43:17 +0100 [thread overview]
Message-ID: <200709292343.19562.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580709290854s61c11a5cicccf7961cb8f4b1c@mail.gmail.com>
> > Also note that changing variables from int to long have strictly no
> > impact on 32 bits host machines, then won't help emulating more than 2
> > GB of RAM. Another variable type (target_phys_addr_t ?) should be used
> > instead.
>
> This patch should be restricted to 64-bit hosts. I don't think it's
> useful to emulate a 64-bit target with huge amounts of virtual and
> physical address space on a 32-bit host.
IMHO Huge amounts of virtual address space can definitely be useful, even if
you don't have ram to back it.
Huge amounts of physical address space is less immediately useful, though in
practice you have to emulate whatever real hardware provides. If you're
emulating a machine with a 40+ bit physical address space, there's a fair
chance your guest OS will decide to scatter a relatively small set of
resources over the whole address space.
I agree there's no point trying to emulate >2G ram on a 32-bit host, but
physical address space and ram are two very different things.
For example I have a cpu that has a "bitbanded" memory region. This expands
each bit of real ram to a whole 32-bit word, effectively turning a word
load/store into an atomic bit operation. Currently it's only used for
relatively small address ranges, but it's a good example of a situation where
the physical address space is much larger than ram.
Paul
next prev parent reply other threads:[~2007-09-29 22:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 13:04 [Qemu-devel] Updated >2G memory patch Blue Swirl
2007-09-29 13:33 ` [Qemu-devel] " Izik Eidus
2007-09-29 13:40 ` Izik Eidus
2007-09-29 13:34 ` [Qemu-devel] " J. Mayer
2007-09-29 15:54 ` Blue Swirl
2007-09-29 22:43 ` Paul Brook [this message]
2007-09-29 23:16 ` J. Mayer
2007-09-30 0:02 ` Paul Brook
2007-09-30 0:34 ` J. Mayer
2007-09-30 15:43 ` Paul Brook
2007-09-30 7:15 ` Blue Swirl
2007-09-30 12:31 ` J. Mayer
2007-09-30 14:37 ` Avi Kivity
2007-09-30 15:30 ` Blue Swirl
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=200709292343.19562.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@gmail.com \
--cc=l_indien@magic.fr \
--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).