From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org,
Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: [kvm-devel] [PATCH 1/6] Use correct types to enable > 2G support
Date: Fri, 01 Feb 2008 09:33:26 -0600 [thread overview]
Message-ID: <47A33BC6.3060705@us.ibm.com> (raw)
In-Reply-To: <47A33721.4020600@qumranet.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> I think I'll change this too into a single qemu_ram_alloc. That will
>> fix the bug with KVM when using -kernel and large memory anyway :-)
>>
>
> Won't that cause all of the memory in the hole to be wasted?
>
> You could munmap() it, but it's hardly elegant.
>
It only gets wasted if it gets faulted in. Any it won't get faulted in,
so it won't increase the RSS size. We could madvise(MADV_DONTNEED) just
to ensure that it's not occupying swap space if you were really paranoid
about it. I don't think munmap()'ing malloc()'d memory is a very good
idea. glibc may freak out.
The alternative is to change all the places that assume phys_ram_base +
PA which I don't like very much.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-02-01 15:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 22:36 [Qemu-devel] [PATCH 0/6] Support for the Kernel Virtual Machine interface Anthony Liguori
2008-01-31 22:36 ` [Qemu-devel] [PATCH 1/6] Use correct types to enable > 2G support Anthony Liguori
2008-01-31 23:54 ` [Qemu-devel] " Paul Brook
2008-02-01 0:25 ` Anthony Liguori
2008-02-01 0:37 ` Paul Brook
2008-02-01 0:40 ` Anthony Liguori
2008-02-01 10:26 ` Fabrice Bellard
2008-02-01 14:35 ` Anthony Liguori
2008-02-01 15:13 ` Avi Kivity
2008-02-01 11:56 ` Robert William Fuller
2008-02-01 16:09 ` M. Warner Losh
2008-02-01 16:47 ` Philip Boulain
2008-02-01 17:35 ` Jamie Lokier
2008-02-01 15:33 ` Anthony Liguori [this message]
2008-02-01 15:40 ` [Qemu-devel] Re: [kvm-devel] " Ian Jackson
2008-02-01 17:53 ` [kvm-devel] [Qemu-devel] " Anthony Liguori
2008-02-01 17:57 ` Daniel P. Berrange
2008-02-01 20:31 ` Anthony Liguori
2008-02-01 21:33 ` Paul Brook
2008-02-01 16:00 ` Paul Brook
2008-02-01 16:21 ` Fabrice Bellard
2008-02-05 11:34 ` Ian Jackson
2008-02-01 17:49 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2008-02-03 8:58 ` Izik Eidus
2008-01-31 22:36 ` [Qemu-devel] [PATCH 2/6] SCI fixes Anthony Liguori
2008-01-31 22:36 ` [Qemu-devel] [PATCH 3/6] Fix daemonize options Anthony Liguori
2008-01-31 22:36 ` [Qemu-devel] [PATCH 4/6] Tell BIOS about the number of CPUs Anthony Liguori
2008-02-01 0:14 ` [Qemu-devel] " Paul Brook
2008-02-01 0:28 ` Anthony Liguori
2008-02-01 0:40 ` Paul Brook
2008-01-31 22:36 ` [Qemu-devel] [PATCH 5/6] Refactor option ROM loading Anthony Liguori
2008-01-31 22:36 ` [Qemu-devel] [PATCH 6/6] QEMU support for the Kernel Virtual Machine interface Anthony Liguori
2008-02-01 9:49 ` [Qemu-devel] " Fabrice Bellard
2008-02-01 14:18 ` Anthony Liguori
2008-01-31 22:53 ` [qemu-devel] [PATCH 0/6] Support " Anthony Liguori
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=47A33BC6.3060705@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=paul@codesourcery.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).