From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
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: Tue, 23 Feb 2010 15:07:20 -0600 [thread overview]
Message-ID: <4B844388.9080705@codemonkey.ws> (raw)
In-Reply-To: <8B153AFB-E0D5-406A-A360-389A8A9C9D69@suse.de>
On 02/23/2010 02:30 PM, Alexander Graf wrote:
> On 23.02.2010, at 18:02, 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.
>>
> Sounds like a perfect candidate for -stable then. For HEAD I agree that finding the cause would be the way to go.
>
No, it's wrong. A good candidate for -stable would be something that
fixes the SEGV :-)
Regards,
Anthony Liguori
> Alex--
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Ryan Harper <ryanh@us.ibm.com>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] Fix segfault with ram_size > 4095M without kvm
Date: Tue, 23 Feb 2010 15:07:20 -0600 [thread overview]
Message-ID: <4B844388.9080705@codemonkey.ws> (raw)
In-Reply-To: <8B153AFB-E0D5-406A-A360-389A8A9C9D69@suse.de>
On 02/23/2010 02:30 PM, Alexander Graf wrote:
> On 23.02.2010, at 18:02, 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.
>>
> Sounds like a perfect candidate for -stable then. For HEAD I agree that finding the cause would be the way to go.
>
No, it's wrong. A good candidate for -stable would be something that
fixes the SEGV :-)
Regards,
Anthony Liguori
> Alex--
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-02-23 21:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 15:13 [PATCH] Fix segfault with ram_size > 4095M without kvm Ryan Harper
2010-02-23 15:13 ` [Qemu-devel] " Ryan Harper
2010-02-23 17:02 ` Aurelien Jarno
2010-02-23 17:02 ` [Qemu-devel] " Aurelien Jarno
2010-02-23 20:30 ` Alexander Graf
2010-02-23 21:07 ` Anthony Liguori [this message]
2010-02-23 21:07 ` Anthony Liguori
2010-02-23 21:24 ` Aurelien Jarno
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
2010-03-04 21:34 ` Ryan Harper
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=4B844388.9080705@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.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.