linux-kernel - Re: [PATCH v6 6/9] KVM: MMU: fast path of handling guest page fault

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20120619110728.14504b91ec1c2ee9cd81b413@gmail.com>
Date:	Tue, 19 Jun 2012 11:07:28 +0900
From:	Takuya Yoshikawa <takuya.yoshikawa@...il.com>
To:	Marcelo Tosatti <mtosatti@...hat.com>
Cc:	Takuya Yoshikawa <yoshikawa.takuya@....ntt.co.jp>,
	Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com>,
	Avi Kivity <avi@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>, KVM <kvm@...r.kernel.org>
Subject: Re: [PATCH v6 6/9] KVM: MMU: fast path of handling guest page fault

On Mon, 18 Jun 2012 16:21:20 -0300
Marcelo Tosatti <mtosatti@...hat.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/