From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFC] KVM guest page swap out support - take2
Date: Tue, 05 Jun 2007 17:17:08 +0300 [thread overview]
Message-ID: <46657064.3090300@qumranet.com> (raw)
In-Reply-To: <1180924515.4257.16.camel-yAZKuqJtXNMXR+D7ky4Foa2pdiUAq4bhAL8bYrjMMd8@public.gmane.org>
Shaohua Li wrote:
> Hi,
> This is a updated patch set of swap out kvm guest pages.Changes are:
> 1. refresh against to kvm-26
> 2. clean up shadow page handling to make gfn_to_page not be called
> within kmap_atomic/kunamp_atomic.
> 3. variant bug fixing. Now the patch is quite stable in my test.
> 4. make swap out optional. A compile option can completely close swap
> out. There should be no performance impact if swapout isn't enabled.
>
> There are still a lot of unresolved issues:
> 1. just work for one vm. waiting for kvm hook into scheduler
> 2. Not work for mp guest and can't swap out pages which shadow page
> table point to, this require kvm .flush_tlb can send ipi to vcpu.
> 3. swapoff isn't supported. We need a hook to sys_swapoff for kvm.
>
> Please review, suggests and comments are welcome.
>
>
The patch rmaps read-only guest pages. While this is of course
required, it will make unshadowing ptes pointing to shared library pages
very expensive. If we have a guest with 200 processes, all mapping
glibc, then an exit() will have to walk a linear list of size 200 per
shadowed pte.
Do you know how the Linux rmap implementation handles this?
An idea that comes to mind is to allocate an extra mm_struct for the
guest and use the normal Linux vma management there. I don't know how
practical this is.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-05 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 2:35 [RFC] KVM guest page swap out support - take2 Shaohua Li
[not found] ` <1180924515.4257.16.camel-yAZKuqJtXNMXR+D7ky4Foa2pdiUAq4bhAL8bYrjMMd8@public.gmane.org>
2007-06-04 10:18 ` Avi Kivity
2007-06-05 14:17 ` Avi Kivity [this message]
[not found] ` <46657064.3090300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-06 1:18 ` Shaohua Li
[not found] ` <1181092735.18478.4.camel-yAZKuqJtXNMXR+D7ky4Foa2pdiUAq4bhAL8bYrjMMd8@public.gmane.org>
2007-06-07 9:10 ` Shaohua Li
[not found] ` <1181207441.25189.5.camel-yAZKuqJtXNMXR+D7ky4Foa2pdiUAq4bhAL8bYrjMMd8@public.gmane.org>
2007-06-11 8:24 ` Shaohua Li
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=46657064.3090300@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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