linux-kernel - Re: [PATCH v2 06/12] KVM: MMU: introduce a static table to map guest access to spte access

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]

Date:	Wed, 30 Jan 2013 11:53:50 +0800
From:	Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com>
To:	Marcelo Tosatti <mtosatti@...hat.com>
CC:	Avi Kivity <avi.kivity@...il.com>, Gleb Natapov <gleb@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>, KVM <kvm@...r.kernel.org>
Subject: Re: [PATCH v2 06/12] KVM: MMU: introduce a static table to map guest
 access to spte access

On 01/29/2013 09:07 AM, Marcelo Tosatti wrote:
> On Mon, Jan 28, 2013 at 10:07:15PM -0200, Marcelo Tosatti wrote:
>> On Fri, Jan 25, 2013 at 10:46:31AM +0800, Xiao Guangrong wrote:
>>> On 01/25/2013 08:15 AM, Marcelo Tosatti wrote:
>>>> On Wed, Jan 23, 2013 at 06:07:20PM +0800, Xiao Guangrong wrote:
>>>>> It makes set_spte more clean and reduces branch prediction
>>>>>
>>>>> Signed-off-by: Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com>
>>>>> ---
>>>>>  arch/x86/kvm/mmu.c |   37 ++++++++++++++++++++++++++-----------
>>>>>  1 files changed, 26 insertions(+), 11 deletions(-)
>>>>
>>>> Don't see set_spte as being a performance problem?
>>>> IMO the current code is quite simple.
>>>
>>> Yes, this is not a performance problem.
>>>
>>> I just dislike this many continuous "if"-s in the function:
>>>
>>> if (xxx)
>>> 	xxx
>>> if (xxx)
>>> 	xxx
>>> ....
>>>
>>> Totally, it has 7 "if"-s before this patch.
>>>
>>> Okay, if you think this is unnecessary, i will drop this patch. :)
>>
>> Yes, please (unless you can show set_spte is a performance problem).
> 
> Same thing for spte fast drop: is it a performance problem? 

It does not fix a performance problem. The patch does optimization on the
noncrucial path and cleanup for the previous patch.

> 
> Please try to group changes into smaller, less controversial sets with 
> a clear goal:

Ah. I thought they are simple and most of them have been reviewed, so i putted
them into one group, now i know i made a mistake. ;)

> 
> - Debated performance improvement.
> - Cleanups (eg mmu_set_spte argument removal).
> - Bug fixes.
> - Performance improvements.

Okay. I will split the long series into these set:

Set 1 for improvement:
[PATCH v2 01/12] KVM: MMU: lazily drop large spte

Set 2 for cleanups:
[PATCH v2 02/12] KVM: MMU: cleanup mapping-level
[PATCH v2 07/12] KVM: MMU: remove pt_access in mmu_set_spte
[PATCH v2 08/12] KVM: MMU: cleanup __direct_map

Set 3 for simplifying set spte path:
[PATCH v2 03/12] KVM: MMU: simplify mmu_set_spte
[PATCH v2 04/12] KVM: MMU: simplify set_spte
[PATCH v2 05/12] KVM: MMU: introduce vcpu_adjust_access

Set 4 for fixing and unifying rmap walking
[PATCH v2 11/12] KVM: MMU: fix spte assertion
[PATCH v2 09/12] KVM: MMU: introduce mmu_spte_establish
[PATCH v2 10/12] KVM: MMU: unify the code of walking pte list
[PATCH v2 12/12] KVM: MMU: fast drop all spte on the pte_list

Thanks!

--
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/