From: Ryan Harper <ryanh@us.ibm.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Ryan Harper <ryanh@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] Fix segfault with ram_size > 4095M without kvm
Date: Thu, 4 Mar 2010 15:34:34 -0600 [thread overview]
Message-ID: <20100304213434.GA17350@us.ibm.com> (raw)
In-Reply-To: <20100304212724.GH5860@hall.aurel32.net>
* Aurelien Jarno <aurelien@aurel32.net> [2010-03-04 15:27]:
> On Tue, Feb 23, 2010 at 06:02:15PM +0100, Aurelien Jarno wrote:
> > Ryan Harper a écrit :
> > > Currently, x86_64-softmmu qemu segfaults when trying to use > 4095M memsize.
> > > This patch adds a simple check and error message (much like the 2047 limit on
> > > 32-bit hosts) on ram_size in the control path after we determine we're
> > > not using kvm
> > >
> > > Upstream qemu-kvm is affected if using the -no-kvm option; this patch address
> > > the segfault there as well.
> >
> > It looks like workarounding the real bug. At some point both
> > i386-softmmu (via PAE) and x86_64-softmmu were able to support > 4GB of
> > memory. I remember adding the support long time ago, and testing it with
> > 32GB of emulated RAM.
>
> I have looked into that, and actually one patch to get full support for
> > 4GB of memory was not merged:
Thanks for looking into this.
>
> diff --git a/exec.c b/exec.c
> index 8389c54..b0bb058 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -166,7 +166,7 @@ typedef struct PhysPageDesc {
> */
> #define L1_BITS (TARGET_VIRT_ADDR_SPACE_BITS - L2_BITS - TARGET_PAGE_BITS)
> #else
> -#define L1_BITS (32 - L2_BITS - TARGET_PAGE_BITS)
> +#define L1_BITS (TARGET_PHYS_ADDR_SPACE_BITS - L2_BITS - TARGET_PAGE_BITS)
> #endif
>
> #define L1_SIZE (1 << L1_BITS)
>
> While this patch is acceptable for qemu i386, it creates a big L1 table
> for x86_64 or other 64-bit architectures, resulting in huge memory
> overhead.
>
> The recent multilevel tables patches from Richard Henderson should fix
> the problem for HEAD (I haven't found time to look at them in details).
>
> As this is not something we really want to backport, your patch makes
> sense in stable-0.12.
Anthony, do you want me to resend and rebase against 0.12-stable?
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2010-03-04 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 15:13 [Qemu-devel] [PATCH] Fix segfault with ram_size > 4095M without kvm Ryan Harper
2010-02-23 17:02 ` Aurelien Jarno
2010-02-23 20:30 ` Alexander Graf
2010-02-23 21:07 ` Anthony Liguori
2010-02-23 21:24 ` Aurelien Jarno
2010-02-23 22:55 ` Ryan Harper
2010-03-04 21:27 ` Aurelien Jarno
2010-03-04 21:34 ` Ryan Harper [this message]
2010-03-06 21:31 ` Aurelien Jarno
-- strict thread matches above, loose matches on Subject: below --
2010-12-08 18:01 Luiz Capitulino
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=20100304213434.GA17350@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=aurelien@aurel32.net \
--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).