From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Marcelo Tosatti <mtosatti@redhat.com>,
Sheng Yang <sheng@linux.intel.com>,
KVM list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] KVM MMU: thinking of shadow page cache
Date: Thu, 01 Apr 2010 12:12:05 +0300 [thread overview]
Message-ID: <4BB46365.7020400@redhat.com> (raw)
In-Reply-To: <4BB461E7.9000109@cn.fujitsu.com>
On 04/01/2010 12:05 PM, Xiao Guangrong wrote:
>
>> We've considered this in the past, it makes sense. The big question is
>> whether any guests actually map the same page table through PDEs with
>> different permissions (mapping the same page table through multiple PDEs
>> is very common, but always with the same permissions). Do you know of
>> any such guest?
>>
> I also don't know whether have such guest.
> Maybe my idea is no good for current OS, thanks for your comments.
>
In fact there are plans to make kvm such a guest (when running in nested
mode) - when we perform live migration we write-protect all guest pages,
and it's reasonable to use the top-level shadow page to write protect
all memory at once instead of iterating over all mmu pages. When that
goes in, we should also implement your idea.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-04-01 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 1:59 [RFC] KVM MMU: thinking of shadow page cache Xiao Guangrong
2010-03-30 13:32 ` Avi Kivity
2010-04-01 9:05 ` Xiao Guangrong
2010-04-01 9:12 ` Avi Kivity [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=4BB46365.7020400@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.com \
--cc=xiaoguangrong@cn.fujitsu.com \
/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.