From: Marcelo Tosatti <mtosatti@redhat.com>
To: Xudong Hao <xudong.hao@linux.intel.com>
Cc: avi@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, haitao.shan@intel.com,
xiantao.zhang@intel.com, xudong.hao@intel.com
Subject: Re: [PATCH 4/4] Enabling Access bit when doing memory swapping
Date: Thu, 17 May 2012 23:22:41 -0300 [thread overview]
Message-ID: <20120518022241.GA14096@amt.cnet> (raw)
In-Reply-To: <20120516011230.GE14256@hp-xd.sh.intel.com>
On Wed, May 16, 2012 at 09:12:30AM +0800, Xudong Hao wrote:
> Enabling Access bit when doing memory swapping.
>
> Signed-off-by: Haitao Shan <haitao.shan@intel.com>
> Signed-off-by: Xudong Hao <xudong.hao@intel.com>
> ---
> arch/x86/kvm/mmu.c | 13 +++++++------
> arch/x86/kvm/vmx.c | 6 ++++--
> 2 files changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index ff053ca..5f55f98 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -1166,7 +1166,8 @@ static int kvm_age_rmapp(struct kvm *kvm, unsigned long *rmapp,
> int young = 0;
>
> /*
> - * Emulate the accessed bit for EPT, by checking if this page has
> + * In case of absence of EPT Access and Dirty Bits supports,
> + * emulate the accessed bit for EPT, by checking if this page has
> * an EPT mapping, and clearing it if it does. On the next access,
> * a new EPT mapping will be established.
> * This has some overhead, but not as much as the cost of swapping
> @@ -1179,11 +1180,11 @@ static int kvm_age_rmapp(struct kvm *kvm, unsigned long *rmapp,
> while (spte) {
> int _young;
> u64 _spte = *spte;
> - BUG_ON(!(_spte & PT_PRESENT_MASK));
> - _young = _spte & PT_ACCESSED_MASK;
> + BUG_ON(!is_shadow_present_pte(_spte));
> + _young = _spte & shadow_accessed_mask;
> if (_young) {
> young = 1;
> - clear_bit(PT_ACCESSED_SHIFT, (unsigned long *)spte);
> + *spte &= ~shadow_accessed_mask;
> }
Now a dirty bit can be lost. Is there a reason to remove the clear_bit?
next prev parent reply other threads:[~2012-05-18 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 1:12 [PATCH 4/4] Enabling Access bit when doing memory swapping Xudong Hao
2012-05-18 2:22 ` Marcelo Tosatti [this message]
2012-05-21 3:22 ` Hao, Xudong
2012-05-21 8:31 ` Avi Kivity
2012-05-21 10:35 ` Hao, Xudong
2012-05-21 10:48 ` Avi Kivity
2012-05-21 11:17 ` Hao, Xudong
2012-05-21 11:31 ` 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=20120518022241.GA14096@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=haitao.shan@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiantao.zhang@intel.com \
--cc=xudong.hao@intel.com \
--cc=xudong.hao@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).