From: Shaohua Li <shaohua.li@intel.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC 7/8]KVM: swap out guest pages
Date: Tue, 24 Jul 2007 09:51:48 +0800 [thread overview]
Message-ID: <1185241908.24201.22.camel@sli10-conroe.sh.intel.com> (raw)
In-Reply-To: <46A491C4.8010302@qumranet.com>
On Mon, 2007-07-23 at 19:32 +0800, Avi Kivity wrote:
> Shaohua Li wrote:
> > Make KVM guest pages be allocated dynamically and able to be swaped
> out.
> >
> > One issue: all inodes returned from anon_inode_getfd are shared,
> > if one module changes field of the inode, other moduels might break.
> > Should we introduce a new API to not share inode?
> >
> > Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> > ---
> > drivers/kvm/kvm.h | 8 +
> > drivers/kvm/kvm_main.c | 220
> +++++++++++++++++++++++++++++++++++++++++++++----
> > 2 files changed, 211 insertions(+), 17 deletions(-)
> >
> > +
> > + /*
> > + * We just zap vcpu 0's page table. For a SMP guest, we should
> zap all
> > + * vcpus'. It's better shadow page table is per-vm.
> > + */
> > + if (PagePrivate(page))
> > + kvm_mmu_zap_pagetbl(&kvm->vcpus[0], page->index);
> > +
> >
>
> You're not removing any shadows of the page, in case that page is a
> guest page table. But I don't see anything wrong with it -- the page
> won't change while it's in swap.
You are right. Should we?
next prev parent reply other threads:[~2007-07-24 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 6:51 [RFC 7/8]KVM: swap out guest pages Shaohua Li
2007-07-23 11:32 ` Avi Kivity
2007-07-24 1:51 ` Shaohua Li [this message]
2007-07-24 5:38 ` Avi Kivity
2007-07-24 14:55 ` Avi Kivity
2007-07-25 11:55 ` [kvm-devel] " Shaohua Li
2007-07-25 13:20 ` Shaohua Li
2007-07-25 13:25 ` 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=1185241908.24201.22.camel@sli10-conroe.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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