linux-kernel - Re: [PATCH] KVM: const-ify all relevant uses of struct kvm_memory

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: <K0F3XQ.PUWYFZOU1LO23@effective-light.com>
Date:   Sat, 31 Jul 2021 00:55:32 -0400
From:   Hamza Mahfooz <someguy@...ective-light.com>
To:     Peter Xu <peterx@...hat.com>
Cc:     linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
        Sean Christopherson <seanjc@...gle.com>,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        Wanpeng Li <wanpengli@...cent.com>,
        Jim Mattson <jmattson@...gle.com>,
        Joerg Roedel <joro@...tes.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
        kvm@...r.kernel.org
Subject: Re: [PATCH] KVM: const-ify all relevant uses of struct
 kvm_memory_slot



On Fri, Jul 30 2021 at 04:19:21 PM -0400, Peter Xu <peterx@...hat.com> 
wrote:
> separate patch.  At the meantime I also don't understand why memcpy() 
> here,
> which seems to be even slower..

Alright, I've now had a chance to compare the object code generated 
before
my patch is applied, with what is generated after it is applied and the
same object code is generated for arch/x86/kvm/mmu/mmu.c in both cases 
(at
least when compiling with clang, however I suspect other optimizing
compilers would behave similarly).