[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878rctnkqg.wl-maz@kernel.org>
Date: Fri, 09 Jun 2023 08:44:07 +0100
From: Marc Zyngier <maz@...nel.org>
To: Chun-Tse Shao <ctshao@...gle.com>
Cc: linux-kernel@...r.kernel.org, yuzhao@...gle.com,
oliver.upton@...ux.dev, James Morse <james.morse@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Zenghui Yu <yuzenghui@...wei.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, Ben Gardon <bgardon@...gle.com>,
Gavin Shan <gshan@...hat.com>,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.linux.dev
Subject: Re: [PATCH v1 3/3] KVM: arm64: Using rcu_read_lock() for kvm_pgtable_stage2_mkyoung()
On Thu, 08 Jun 2023 23:05:41 +0100,
Chun-Tse Shao <ctshao@...gle.com> wrote:
>
> Access bit is RCU safe and can be set without taking kvm->mmu_lock().
Please explain why. What happens when the page tables are *not* RCU
controlled, such as in the pKVM case?
> Replacing existing kvm->mmu_lock() with rcu_read_lock() for better
> performance.
Please define "better performance", quote workloads, figures, HW setup
and point to a reproducer. Please add a cover letter to your patch
series explaining the context this happens in.
Also, I'm getting increasingly annoyed by the lack of coordination
between seamingly overlapping patch series (this, Yu's, Anish's and
Vipin's), all from a single company.
Surely you can talk to each other and devise a coordinated approach?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists