From: Anthony Liguori <anthony@codemonkey.ws>
To: Sukanto Ghosh <sukanto@cse.iitb.ac.in>
Cc: kvm@vger.kernel.org
Subject: Re: Scheduling of VCPUs and allocation of Guest Physical Memory
Date: Thu, 05 Jun 2008 07:54:29 -0500 [thread overview]
Message-ID: <4847E205.4060605@codemonkey.ws> (raw)
In-Reply-To: <484795C3.8030603@cse.iitb.ac.in>
Sukanto Ghosh wrote:
> Hi all,
>
> I have two questions regarding KVM:
>
> i) Is a VCPU scheduled like a normal Linux process
A normal process.
> or there is some mechanism by which performance guarantees can be
> provided to the VCPUs ?
FWIW, there are various mechanisms to do scheduler tuning in Linux.
cpusets and cgroups both provide mechanisms to ensure "performance
guarantees".
> ii) Who does the allocation of host physical memory to the guest, is
> it KVM module or the associated QEmu process ?
The QEMU process allocates the memory via malloc().
> Also, I would be glad if you can provide me pointers to some
> documentation/paper/literature which discusses KVM in greater detail
> than what the paper "kvm: The Linux Virtual Machine Monitor" presents.
The only other reference is the code itself.
Regards,
Anthony Liguori
> Thanks,
> Sukanto
> --
> 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:[~2008-06-05 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 7:29 Scheduling of VCPUs and allocation of Guest Physical Memory Sukanto Ghosh
2008-06-05 12:54 ` Anthony Liguori [this message]
2008-06-06 14:22 ` Sukanto Ghosh
2008-06-06 14:40 ` Anthony Liguori
2008-06-09 11:10 ` Sukanto Ghosh
2008-06-09 16:19 ` Avi Kivity
2008-06-16 14:23 ` Sukanto Ghosh
2008-06-18 14:12 ` Avi Kivity
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=4847E205.4060605@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=sukanto@cse.iitb.ac.in \
/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.