From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4E5D2CCF2D6 for ; Mon, 19 Oct 2026 09:27:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Subject:Cc:To:From: Message-ID:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=2OjBa7iaXXaZQxUImtISWJdVBXlfSGVvuUO6E60OqkI=; b=QKl50pFapQMsqIrIIVN7cOrBMf N7T0h+swUlzhzGeTZ21nnVvikqNeCXM0eV7z6LZZMbq7TFGvgGqhsuju0EPh33r1rmmYs6Ks6+lgY yrNHIlx62s3wI1f52lf3rx5Erhxvt0qvfTX3bIAjdknlx7VnfUszOydWOB5CblLMKj8rMM+4sZyHb DZgkpqcsSANPPcpEpZCF1DYhBE5Uz7R1uklnwWFBQ3gYg9qTH4sYS5aRWgr83AacDJy6Qn+yCowuc lYiEiwhYfKEpFNufD7wPjlWHNrlipIR7gEwUs9s1YdQbJ2zl59xK7fOURzXCp0wcVP6T3NVAATrJA KJM5u1dQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xIjek-0000000703g-3lvf; Mon, 19 Oct 2026 09:27:46 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xIjej-0000000703Q-21OW for linux-arm-kernel@lists.infradead.org; Mon, 19 Oct 2026 09:27:45 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id E89E360207; Mon, 19 Oct 2026 09:27:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 977821F000C4; Mon, 19 Oct 2026 09:27:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1792402064; bh=2OjBa7iaXXaZQxUImtISWJdVBXlfSGVvuUO6E60OqkI=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=XOPXKQ6+hgTicpmygm4YVwbYVNQE6k/Fiz83sSfeaoX8WBuh1j7Xfg0D2c8jvn1AR qHTt+6p8qZBnji04u7xtNmJWcLCvWaVVLzmi15fprhdlHJc8taL384XZUdP/yaLcwF cV3oYIJXUfoBKrdPUBx1KFnhC3NsDc9mHWs2oYlbDqcoam/qAR0zSUE5WiXOipaX07 IoPT5H8nYD8KhLtXHJe6DfafGyxQm8k5EOXZk5bDRV1AD+6FvKjsZ0ANbG8HUDEz5K OSiPVBuICeS2UBpm2921pBWeEPp0EJgt+UoRY5Z3I4k4P7ivHQIBYQACRk8O3L4pRE m5LsGKqI2zSPg== Received: from sofa.misterjones.org ([185.219.108.64] helo=goblin-girl.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xIjeg-00000004Z9Z-20hE; Mon, 19 Oct 2026 09:27:42 +0000 Date: Mon, 19 Oct 2026 10:27:40 +0100 Message-ID: <86zewayr8z.wl-maz@kernel.org> From: Marc Zyngier To: Jinqian Yang Cc: Kristina =?UTF-8?B?TWFydMWhZW5rbw==?= ,, ,, , Catalin Marinas , Will Deacon , Mark Rutland , Ryan Roberts , David Hildenbrand , Lorenzo Stoakes , Linu Cherian , Anshuman Khandual , Lorenzo Pieralisi , Hanjun Guo , Sudeep Holla , Oliver Upton , Fuad Tabba , Joey Gouly , Steffen Eiden , Suzuki K Poulose , Zenghui Yu , Ard Biesheuvel , Ilias Apalodimas Subject: Re: [RFC 00/12] arm64: Add support for TLBI domains In-Reply-To: <9eb6e0fe-5d8a-499c-b19b-ce73fe982451@huawei.com> References: <20261001110655.461473-1-kristina.martsenko@arm.com> <9eb6e0fe-5d8a-499c-b19b-ce73fe982451@huawei.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/30.1 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: yangjinqian1@huawei.com, kristina.martsenko@arm.com, linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org, kvmarm@lists.linux.dev, linux-efi@vger.kernel.org, catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com, ryan.roberts@arm.com, david@kernel.org, ljs@kernel.org, linu.cherian@arm.com, anshuman.khandual@arm.com, lpieralisi@kernel.org, guohanjun@huawei.com, sudeep.holla@kernel.org, oupton@kernel.org, fuad.tabba@linux.dev, joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com, ardb@kernel.org, ilias.apalodimas@linaro.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, 19 Oct 2026 09:52:04 +0100, Jinqian Yang wrote: >=20 > Hi, >=20 > On 2026/10/1 19:06, Kristina Mart=C5=A1enko wrote: > > Hi, > >=20 > > This series allows the kernel to use TLBI domains. TLBI domains (FEAT_T= LBID) is > > an Arm architecture feature that enables a TLB invalidation to target a= subset > > of CPUs instead of the whole system. It can improve performance on syst= ems with > > many CPUs. TLBID is not yet part of the Arm Architecture Reference Manu= al but > > some of it is described in the latest XML [1]. > >=20 > > The goal of this series is to send TLBI commands only to the CPUs where= a > > process has run (i.e. where its page tables have been installed). The l= ast > > patch explains a bit about how it works. This is an RFC since I'm not f= amiliar > > with the kernel's TLB/mm code and I'd like feedback on whether the gene= ral > > approach is correct. > >=20 >=20 > Thanks for posting this series. >=20 > I'm working on the KVM side of TLBID, and have a series that > virtualizes TLBI domains for guests. It includes: >=20 > - per-vCPU vDomain configuration via a new capability and > two ioctls > - VTLBID_EL2 programming at vCPU load/put, mapping vDomains > to physical domains > - a guest visible TLBIDIDR_EL1 with virtual domain counts, > and conditional exposure of ID_AA64MMFR4_EL1.TLBID >=20 > You mentioned you planned to look at KVM support in your next > version. Would it be OK for us to post this as an RFC on top > of your series? :) It is always OK to post patches, but don't expect much reviewing to take place until things have settled on the host side of things. Thanks, M. --=20 Without deviation from the norm, progress is not possible.