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] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 01 Jul 2010 09:11:36 +0800
From:	Xiao Guangrong <xiaoguangrong@...fujitsu.com>
To:	Marcelo Tosatti <mtosatti@...hat.com>
CC:	Avi Kivity <avi@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
	KVM list <kvm@...r.kernel.org>
Subject: Re: [PATCH v3 9/11] KVM: MMU: prefetch ptes when intercepted guest
 #PF



Marcelo Tosatti wrote:

>> +
>> +		addr = gfn_to_hva_many(vcpu->kvm, gfn, &entry);
>> +		if (kvm_is_error_hva(addr))
>> +			return -1;
>> +
>> +		entry = min(entry, (int)(end - start));
>> +		ret = __get_user_pages_fast(addr, entry, 1, pages);
>> +		if (ret <= 0)
>> +			return -1;
> 
> Why can't you use gfn_to_pfn_atomic() here, one page at a time? Is 
> the overhead significant that this is worthwhile?
> 
> You're bypassing the centralized interface.

I think it's worthwhile to do since we can reduce gup overhead, no reason
to traverse process's page table again and again for the consecutive pages.

> 
>> +
>> +		pte_access = sp->role.access & FNAME(gpte_access)(vcpu, gpte);
>> +		mmu_set_spte(vcpu, spte, sp->role.access, pte_access, 0, 0,
>> +			     is_dirty_gpte(gpte), NULL, sp->role.level, gfn,
>> +			     pfn, true, false);
> 
> reset_host_protection should be true, see commit 1403283acca (also for
> direct case to be consistent).
> 

Ah, i forgot it, thanks, Marcelo!

I'll post a small fix patch base on this patchset to change 'false' to 'true' if no
other places no to be improved. :-)
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ