From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takuya Yoshikawa Subject: Re: [PATCH v6 6/9] KVM: MMU: fast path of handling guest page fault Date: Tue, 19 Jun 2012 11:07:28 +0900 Message-ID: <20120619110728.14504b91ec1c2ee9cd81b413@gmail.com> References: <4FC470C7.5040700@linux.vnet.ibm.com> <4FC471B8.3070204@linux.vnet.ibm.com> <20120613224002.GE19290@amt.cnet> <20120614102214.1c8a6e23.yoshikawa.takuya@oss.ntt.co.jp> <20120618192120.GA2697@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Takuya Yoshikawa , Xiao Guangrong , Avi Kivity , LKML , KVM To: Marcelo Tosatti Return-path: In-Reply-To: <20120618192120.GA2697@amt.cnet> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, 18 Jun 2012 16:21:20 -0300 Marcelo Tosatti wrote: > > [not about this patch] > > > > EPT accessed/dirty bits will be used for more things in the future. > > Are there any rules for using these bits? > > > > Same as other bits? > > Do you mean hardware rules or KVM rules? KVM rules. Your concern was about "lock-less" v. "current EPT-A/D code". My question was what we should care not to break the former in the future. Takuya