mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Xudong Hao <xudong.hao@linux.intel.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 0/4] KVM: Enable EPT access bit feature
Date: Wed, 16 May 2012 22:35:19 +0900	[thread overview]
Message-ID: <20120516223519.4f7d6fdc864a552ce67161e9@gmail.com> (raw)
In-Reply-To: <4FB371B1.7000407@redhat.com>

On Wed, 16 May 2012 12:21:53 +0300
Avi Kivity <avi@redhat.com> wrote:

> On 05/16/2012 04:04 AM, Xudong Hao wrote:
> > EPT A/D bits enable VMMs to efficiently implement memory management and page classification algorithms to optimize VM memory operations such as de-fragmentation, paging, live-migration, and check-pointing.
> >
> > The series of patches enable the EPT access bit in KVM.
> >
> > PATCH 1: Add EPT A/D bits definition.
> > PATCH 2: Add kernel parameter to control EPT A/D bits support, the feature is on by default.
> > PATCH 3: Enable EPT A/D bits if supported by turning on relevant bit in EPTP.
> > PATCH 4: Enabling Access bit when doing memory swapping.
> >
> 
> Minor comment on patch 2, but otherwise looks good.

Except for being white space damaged and based on old kvm.git?

BTW, we can use this for dirty logging as you suggested.

Although we need to traverse each spte from rmap and sync with dirty
bitmap, I think it will work well by using with range based GET_DIRTY_LOG
to restrict the cost for one call.

Thanks,
	Takuya

  reply	other threads:[~2012-05-16 13:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  1:04 Xudong Hao
2012-05-16  9:21 ` Avi Kivity
2012-05-16 13:35   ` Takuya Yoshikawa [this message]
2012-05-16 13:43     ` Avi Kivity
2012-05-17  6:30       ` Hao, Xudong

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=20120516223519.4f7d6fdc864a552ce67161e9@gmail.com \
    --to=takuya.yoshikawa@gmail.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

Powered by JetHome