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
| ||
|
Date: Sun, 06 Mar 2011 14:16:37 +0200 From: Avi Kivity <avi@...hat.com> To: Xiao Guangrong <xiaoguangrong@...fujitsu.com> CC: Marcelo Tosatti <mtosatti@...hat.com>, LKML <linux-kernel@...r.kernel.org>, KVM <kvm@...r.kernel.org> Subject: Re: [PATCH 6/10] KVM: MMU: don not record gfn in kvm_mmu_pte_write On 03/06/2011 02:14 PM, Avi Kivity wrote: > On 03/04/2011 01:00 PM, Xiao Guangrong wrote: >> No need to record the gfn to verifier the pte has the same mode as >> current vcpu, it's because we only speculatively update the pte only >> if the pte and vcpu have the same mode > > True. We can, as an additional cleanup, change > mmu_pte_write_new_pte() to just do vcpu->arch.mmu.update_pte(...) > instead of the if (). > Also, we can remove the pfn guessing and to it in FNAME(update_pte), using gfn_to_pfn_atomic(). -- error compiling committee.c: too many arguments to function -- 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/
Powered by blists - more mailing lists