From: Jan Kiszka <jan.kiszka@siemens.com>
To: Laurent Desnogues <laurent.desnogues@gmail.com>,
nicolas prochazka <prochazka.nicolas@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Remove qemu_alloc_physram()
Date: Wed, 27 May 2009 11:48:41 +0200 [thread overview]
Message-ID: <4A1D0C79.801@siemens.com> (raw)
In-Reply-To: <761ea48b0905270236p1da826f1t97a10fa25528acf@mail.gmail.com>
Laurent Desnogues wrote:
> On Wed, May 27, 2009 at 11:29 AM, nicolas prochazka
> <prochazka.nicolas@gmail.com> wrote:
>> Hello,
>> Since this patch :
>> http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=0e8d16ba06486ebf79f131f28121774715975248
>> Remove qemu_alloc_physram()
>> Obsolete.
>>
>> function alloc_mem_area(memory, &map_len, mem_path); is never calling in code,
>> and it seems that's -mem-path ( or -mempath) /hugepages does not
>> work for me now.
>> before this patch, i can see for example in /proc/meminfo :
>> HugePages_Total: 2560
>> HugePages_Free: 2301
>> when i start one kvm/qemu
>>
>> now , HupePages_Free never down , hugepages_free = hugepages_total.
>
> Are you sure you're pointing at the right commit? How could the
> removal of an unused function change the behavior?
>
I bet Nicolas is looking at qemu-kvm, right? So please post this valid
question to the kvm list.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2009-05-27 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 9:29 [Qemu-devel] Remove qemu_alloc_physram() nicolas prochazka
2009-05-27 9:36 ` Laurent Desnogues
2009-05-27 9:48 ` Jan Kiszka [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=4A1D0C79.801@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=laurent.desnogues@gmail.com \
--cc=prochazka.nicolas@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).