From: Anthony Liguori <anthony@codemonkey.ws>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] pc: unbreak vhost
Date: Fri, 16 Jul 2010 08:04:00 -0500 [thread overview]
Message-ID: <4C4058C0.8030709@codemonkey.ws> (raw)
In-Reply-To: <1279283952.20397.293.camel@x201>
On 07/16/2010 07:39 AM, Alex Williamson wrote:
> On Fri, 2010-07-16 at 14:00 +0300, Michael S. Tsirkin wrote:
>
>> Commit 44ae28f3152138e71ccad66c201d730b93374bc2 breaks vhost
>> on small guests as we get a zero-sized memory slot at>4G,
>> which that code does not expect.
>> The removal of if (above_4g_size> 0) seems unintentional
>> (commit log only mentions allocation memory in a single chunk)
>> so just put it back in.
>>
> Yep, I already submitted an identical patch too:
>
> http://lists.nongnu.org/archive/html/qemu-devel/2010-07/msg00364.html
>
Sorry Alex, I apparently forgot to push yesterday. Let me do a quick
merge and build and I'll push.
Regards,
Anthony Liguori
> Alex
>
>
>> Signed-off-by: Michael S. Tsirkin<mst@redhat.com>
>> ---
>> hw/pc.c | 6 ++++--
>> 1 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/pc.c b/hw/pc.c
>> index 89bd4af..77b1592 100644
>> --- a/hw/pc.c
>> +++ b/hw/pc.c
>> @@ -920,8 +920,10 @@ void pc_memory_init(ram_addr_t ram_size,
>> below_4g_mem_size - 0x100000,
>> ram_addr + 0x100000);
>> #if TARGET_PHYS_ADDR_BITS> 32
>> - cpu_register_physical_memory(0x100000000ULL, above_4g_mem_size,
>> - ram_addr + below_4g_mem_size);
>> + if (above_4g_mem_size> 0) {
>> + cpu_register_physical_memory(0x100000000ULL, above_4g_mem_size,
>> + ram_addr + below_4g_mem_size);
>> + }
>> #endif
>>
>> /* BIOS load */
>>
>
>
>
prev parent reply other threads:[~2010-07-16 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 11:00 [Qemu-devel] [PATCH] pc: unbreak vhost Michael S. Tsirkin
2010-07-16 12:39 ` [Qemu-devel] " Alex Williamson
2010-07-16 13:04 ` Anthony Liguori [this message]
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=4C4058C0.8030709@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alex.williamson@redhat.com \
--cc=mst@redhat.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).