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: Fri, 29 Jul 2022 19:02:12 +0000 From: Sean Christopherson <seanjc@...gle.com> To: Chao Peng <chao.p.peng@...ux.intel.com> Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, linux-fsdevel@...r.kernel.org, linux-api@...r.kernel.org, linux-doc@...r.kernel.org, qemu-devel@...gnu.org, linux-kselftest@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>, Jonathan Corbet <corbet@....net>, 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>, Hugh Dickins <hughd@...gle.com>, Jeff Layton <jlayton@...nel.org>, "J . Bruce Fields" <bfields@...ldses.org>, Andrew Morton <akpm@...ux-foundation.org>, Shuah Khan <shuah@...nel.org>, Mike Rapoport <rppt@...nel.org>, Steven Price <steven.price@....com>, "Maciej S . Szmigiero" <mail@...iej.szmigiero.name>, Vlastimil Babka <vbabka@...e.cz>, Vishal Annapurve <vannapurve@...gle.com>, Yu Zhang <yu.c.zhang@...ux.intel.com>, "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>, luto@...nel.org, jun.nakajima@...el.com, dave.hansen@...el.com, ak@...ux.intel.com, david@...hat.com, aarcange@...hat.com, ddutile@...hat.com, dhildenb@...hat.com, Quentin Perret <qperret@...gle.com>, Michael Roth <michael.roth@....com>, mhocko@...e.com, Muchun Song <songmuchun@...edance.com> Subject: Re: [PATCH v7 08/14] KVM: Rename mmu_notifier_* On Wed, Jul 06, 2022, Chao Peng wrote: > The sync mechanism between mmu_notifier and page fault handler employs > fields mmu_notifier_seq/count and mmu_notifier_range_start/end. For the > to be added private memory, there is the same mechanism needed but not > rely on mmu_notifier (It uses new introduced memfile_notifier). This > patch renames the existing fields and related helper functions to a > neutral name mmu_updating_* so private memory can reuse. mmu_updating_* is too broad of a term, e.g. page faults and many other operations also update the mmu. Although the name most definitely came from the mmu_notifier, it's not completely inaccurate for other sources, e.g. KVM's MMU is still being notified of something, even if the source is not the actual mmu_notifier. If we really want a different name, I'd vote for nomenclature that captures the invalidation aspect, which is really what the variables are all trackng, e.g. mmu_invalidate_seq mmu_invalidate_in_progress mmu_invalidate_range_start mmu_invalidate_range_end
Powered by blists - more mailing lists