From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] More than 2G of memory on 64-bit hosts
Date: Mon, 25 Jun 2007 23:52:06 +0300 [thread overview]
Message-ID: <f43fc5580706251352p18b10d13ifac7b7b1fb9d52b6@mail.gmail.com> (raw)
In-Reply-To: <200706252226.50773.michal.schulz@gmx.de>
On 6/25/07, Michal Schulz <michal.schulz@gmx.de> wrote:
> On Monday 25 June 2007, Blue Swirl wrote:
> > This patch removes the restriction of 2G ram size on 64-bit hosts.
> > Theoretically Sparc32 on a SS-10 like machine could handle more than
> > 62GB of memory.
> >
> > There seems to be problems in the boot BIOSes to manage even >2G
> > memory sizes, I've found some in OpenBIOS but there are still many
> > left.
> >
> > Any comments?
>
> One from me, if you like... Just don't use the "unsigned long" type. The
> intptr_t type would be better (it's 32-bit on 32-bit systems and 64-bit on
> 64-bit systems).
Nice, I didn't know about that. But how is this any different from
unsigned long?
next prev parent reply other threads:[~2007-06-25 20:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 20:16 [Qemu-devel] [PATCH, RFC] More than 2G of memory on 64-bit hosts Blue Swirl
2007-06-25 20:26 ` Michal Schulz
2007-06-25 20:52 ` Blue Swirl [this message]
2007-06-25 21:08 ` Michal Schulz
2007-06-26 2:03 ` Karl Magdsick
2007-06-26 8:00 ` Thiemo Seufer
2007-06-26 13:54 ` Paul Brook
2007-06-27 10:26 ` Blue Swirl
2007-06-27 10:32 ` Julian Seward
2007-06-27 11:10 ` Thiemo Seufer
2007-06-27 11:20 ` Julian Seward
2007-06-27 12:18 ` Marius Groeger
2007-06-27 12:32 ` Thiemo Seufer
2007-07-06 19:20 ` Rob Landley
2007-06-29 14:26 ` Gwenole Beauchesne
2007-06-25 20:28 ` Thiemo Seufer
2007-06-25 20:53 ` 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=f43fc5580706251352p18b10d13ifac7b7b1fb9d52b6@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).