From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexei Fedotov <alexei.fedotov@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: qemu/kvm memory allocation
Date: Fri, 11 Jul 2014 16:58:07 +0200 [thread overview]
Message-ID: <53BFFB7F.2000907@redhat.com> (raw)
In-Reply-To: <CAGc_3jFT4CUkAXmtSjL6WpfOGBy-641zJyo5HEA9bB+sLfyEkA@mail.gmail.com>
Il 11/07/2014 16:35, Alexei Fedotov ha scritto:
> Hi Paolo, all,
>
> could anyone advise which source file implements memory allocation in
> KVM? I want to check the source of the corresponding malloc. A simple
> search says that
> KVM source tree contains three malloc implementations.
I'm not even sure what you're talking about, since I already told you
that the KVM hypervisor does not do any memory allocation.
Paolo
next prev parent reply other threads:[~2014-07-11 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 14:49 qemu/kvm memory allocation Alexei Fedotov
2014-07-04 16:17 ` Paolo Bonzini
2014-07-07 9:35 ` Alexei Fedotov
2014-07-11 14:35 ` Alexei Fedotov
2014-07-11 14:58 ` Paolo Bonzini [this message]
2014-07-11 15:27 ` Anshul Makkar
2014-07-11 15:28 ` Alexei Fedotov
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=53BFFB7F.2000907@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexei.fedotov@gmail.com \
--cc=kvm@vger.kernel.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