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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 43908C02181 for ; Mon, 20 Jan 2025 14:06:31 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id CB037280004; Mon, 20 Jan 2025 09:06:30 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id C379D280002; Mon, 20 Jan 2025 09:06:30 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id AB3B2280004; Mon, 20 Jan 2025 09:06:30 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 87B36280002 for ; Mon, 20 Jan 2025 09:06:30 -0500 (EST) Received: from smtpin19.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 27746C01B0 for ; Mon, 20 Jan 2025 14:06:30 +0000 (UTC) X-FDA: 83028005340.19.A9BA080 Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) by imf16.hostedemail.com (Postfix) with ESMTP id 7692F18001B for ; Mon, 20 Jan 2025 14:06:27 +0000 (UTC) Authentication-Results: imf16.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf16.hostedemail.com: domain of riel@shelob.surriel.com designates 96.67.55.147 as permitted sender) smtp.mailfrom=riel@shelob.surriel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1737381987; a=rsa-sha256; cv=none; b=dp3J1KKRdswBsdCb0vGtuCtq5nv9HldsDfjsQd3MVCEW/jLP5cj77eo74IKh83UPInQXAM fpZATiR7Njzz9WJoJECp3lX51FxA8YKwYZwBiX8DlVeh4jaWc5ualwSbxubbdPBpbjqKCR euBTKx0Dv+iazFpVWOcdRGL/4SFDCXk= ARC-Authentication-Results: i=1; imf16.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf16.hostedemail.com: domain of riel@shelob.surriel.com designates 96.67.55.147 as permitted sender) smtp.mailfrom=riel@shelob.surriel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1737381987; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yG5RPMq6zxnK18isL5wyHRMr4yPjGmoK46wkFQeZ1WA=; b=e840b6KptusXbvLXVk10HAY0kstNV4uPfE0SnCkK0uvpB6Kug0HvZFXh/8f8QlSr5lyIz0 VjG2ZaXcY7I5qryytLjrUvtCR0bA/dQZMhX2j2aGfo2a7yPdAVFaOaBrZADiCd6cxcAOHT JfRrnpD7wpj6Mc1QenrXwqucLsBsopo= Received: from fangorn.home.surriel.com ([10.0.13.7]) by shelob.surriel.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1tZsMD-000000001RM-1skx; Mon, 20 Jan 2025 09:02:25 -0500 Message-ID: <4dcf2b4ecaede883e2c7f6af3db58a4f6afaf4ad.camel@surriel.com> Subject: Re: [PATCH v5 10/12] x86,tlb: do targeted broadcast flushing from tlbbatch code From: Rik van Riel To: Nadav Amit , x86@kernel.org Cc: linux-kernel@vger.kernel.org, bp@alien8.de, peterz@infradead.org, dave.hansen@linux.intel.com, zhengqi.arch@bytedance.com, thomas.lendacky@amd.com, kernel-team@meta.com, linux-mm@kvack.org, akpm@linux-foundation.org, jannh@google.com, mhklinux@outlook.com, andrew.cooper3@citrix.com Date: Mon, 20 Jan 2025 09:02:25 -0500 In-Reply-To: <13bc0c49-09a4-434e-bd35-1ea50be38e25@gmail.com> References: <20250116023127.1531583-1-riel@surriel.com> <20250116023127.1531583-11-riel@surriel.com> <13bc0c49-09a4-434e-bd35-1ea50be38e25@gmail.com> Autocrypt: addr=riel@surriel.com; prefer-encrypt=mutual; keydata=mQENBFIt3aUBCADCK0LicyCYyMa0E1lodCDUBf6G+6C5UXKG1jEYwQu49cc/gUBTTk33A eo2hjn4JinVaPF3zfZprnKMEGGv4dHvEOCPWiNhlz5RtqH3SKJllq2dpeMS9RqbMvDA36rlJIIo47 Z/nl6IA8MDhSqyqdnTY8z7LnQHqq16jAqwo7Ll9qALXz4yG1ZdSCmo80VPetBZZPw7WMjo+1hByv/ lvdFnLfiQ52tayuuC1r9x2qZ/SYWd2M4p/f5CLmvG9UcnkbYFsKWz8bwOBWKg1PQcaYHLx06sHGdY dIDaeVvkIfMFwAprSo5EFU+aes2VB2ZjugOTbkkW2aPSWTRsBhPHhV6dABEBAAG0HlJpayB2YW4gU mllbCA8cmllbEByZWRoYXQuY29tPokBHwQwAQIACQUCW5LcVgIdIAAKCRDOed6ShMTeg05SB/986o gEgdq4byrtaBQKFg5LWfd8e+h+QzLOg/T8mSS3dJzFXe5JBOfvYg7Bj47xXi9I5sM+I9Lu9+1XVb/ r2rGJrU1DwA09TnmyFtK76bgMF0sBEh1ECILYNQTEIemzNFwOWLZZlEhZFRJsZyX+mtEp/WQIygHV WjwuP69VJw+fPQvLOGn4j8W9QXuvhha7u1QJ7mYx4dLGHrZlHdwDsqpvWsW+3rsIqs1BBe5/Itz9o 6y9gLNtQzwmSDioV8KhF85VmYInslhv5tUtMEppfdTLyX4SUKh8ftNIVmH9mXyRCZclSoa6IMd635 Jq1Pj2/Lp64tOzSvN5Y9zaiCc5FucXtB9SaWsgdmFuIFJpZWwgPHJpZWxAc3VycmllbC5jb20+iQE +BBMBAgAoBQJSLd2lAhsjBQkSzAMABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDOed6ShMTe g4PpB/0ZivKYFt0LaB22ssWUrBoeNWCP1NY/lkq2QbPhR3agLB7ZXI97PF2z/5QD9Fuy/FD/jddPx KRTvFCtHcEzTOcFjBmf52uqgt3U40H9GM++0IM0yHusd9EzlaWsbp09vsAV2DwdqS69x9RPbvE/Ne fO5subhocH76okcF/aQiQ+oj2j6LJZGBJBVigOHg+4zyzdDgKM+jp0bvDI51KQ4XfxV593OhvkS3z 3FPx0CE7l62WhWrieHyBblqvkTYgJ6dq4bsYpqxxGJOkQ47WpEUx6onH+rImWmPJbSYGhwBzTo0Mm G1Nb1qGPG+mTrSmJjDRxrwf1zjmYqQreWVSFEt26tBpSaWsgdmFuIFJpZWwgPHJpZWxAZmIuY29tP okBPgQTAQIAKAUCW5LbiAIbIwUJEswDAAYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQznneko TE3oOUEQgAsrGxjTC1bGtZyuvyQPcXclap11Ogib6rQywGYu6/Mnkbd6hbyY3wpdyQii/cas2S44N cQj8HkGv91JLVE24/Wt0gITPCH3rLVJJDGQxprHTVDs1t1RAbsbp0XTksZPCNWDGYIBo2aHDwErhI omYQ0Xluo1WBtH/UmHgirHvclsou1Ks9jyTxiPyUKRfae7GNOFiX99+ZlB27P3t8CjtSO831Ij0Ip QrfooZ21YVlUKw0Wy6Ll8EyefyrEYSh8KTm8dQj4O7xxvdg865TLeLpho5PwDRF+/mR3qi8CdGbkE c4pYZQO8UDXUN4S+pe0aTeTqlYw8rRHWF9TnvtpcNzZw== Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.1 (3.54.1-1.fc41) MIME-Version: 1.0 X-Rspam-User: X-Rspamd-Queue-Id: 7692F18001B X-Rspamd-Server: rspam10 X-Stat-Signature: iwfnncx61789effzjciyhtgyehrt63o8 X-HE-Tag: 1737381987-781947 X-HE-Meta: U2FsdGVkX1/oUT4mwoym7k8KNMbLcmEQeMhEEhn4jGt23Lb5mb8t0QpLctFn3vaEVumDCHsPTAlnCHpd4OpXWkMo6REdwj7t18wE+w2P2qvbXXei/ElpoiX2agZgXe75vBp3otZ73tIY/jHrsuCxh48JGoGxszgd14bZ/yz9Fhjs1Zpr1zgFXyD2U4d1EHHeeb1nGu0DnDntnBcnWdI1NQ4rrIsG7IFJL+To340aI+hrsngtC7JMhFgir1MyB/HepYN7TLdPegM294Sa7Hfjqt1LXWS3iyExby29eM98UPM+u5GZugtRfMLJ26CyIrLr92+1DkrWnPeDLIRbChf8b+4xA+6TT9Pf5lIzZOdQp/p39YpGcdKDVrXi72bTabU+VsTiY2JoIa5Kaq2XnCXgGvMdyBSXQMg02TMQakgyYRZqX7Xxr8IQE+aY390jB7LWAMI/Ia/xGnxOwbKHp0bTiJJaDvCS7FFje6PM74KIUccGXCJR4CIigsqZiQI8Ya3pQzPMlfxUYtUv0wJYc2SbHZ7vsPCt20RXC71qoTxFvkD0C0857R7C38mTvp4T6ViEQZ2prY0LrpFZ9f8ursQSwQACZ6SqJGNNCD1T8Rpe+82a9SgHTzmxaKzfxItMgBUHtp04M1v3gCvK/uvUJ+jxNzVV18rZciaMrmQoFv8rmypXL5uQ1MG7TwQt/zdEgqX55FCyhLLolak0BiPNl8bYEZGqWcB8Lmr3BoiuyZT6vn+rlJcmF6Wqau3BEeyNx6b7Ur9lXUS4uyGUAeY7KKxqS0iQoKL4VBcMoZ5V65+UvpNGR3ABOHjBVwRA6hQmvIv55jYML87l5ZA8YQpo6T3qByBo5CNmpVJDsCdkWj6gqqZ41Paw+jSXH8MpLiEZ29nj2PwCm5RUcMOI0zGHYn3SfqpXDdMd9ZdXNl7EyKektmakrGUdqTJzWcYHYt9TBR+/eNuwisn1YzHnsoslPoo tvUuGD5i plRSUAA9O+M6H45T4yjzjh0k+Ofl7tKJ5tgEV86mAkFerF7jWIH+2jsHCraFybuktisI4PHZ9uuJ4JN59Y2btiO1YTR81wK3+GkiJ4GdZClc6vNZlZ6PCOtpT3UOYcJ+v1vdqV//qcktA+3BH+YMbBJmYPE+tU2q7seo1XElZ8QhM9eSTcSb02fL7tuhsiDSi/a29z39+LQT+nmic+FLQ0SJuJzImx++Yt4E3zgero07IOWWLkZJfuGKPEoPTBZWy1ULHxiLZY8J3XmGTkF2W7nlV6mfyR64VRdSZbm36eZX70qLNC/yXhi3VrjjOIXvjaCQgeg/t2mKssk4kvOOOvcUx6g== X-Bogosity: Ham, tests=bogofilter, spamicity=0.007674, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Mon, 2025-01-20 at 11:56 +0200, Nadav Amit wrote: >=20 > > @@ -1670,12 +1668,62 @@ void arch_tlbbatch_flush(struct > > arch_tlbflush_unmap_batch *batch) > > =C2=A0=C2=A0 local_irq_enable(); > > =C2=A0=C2=A0 } > > =C2=A0=20 > > + /* > > + * If we issued (asynchronous) INVLPGB flushes, wait for > > them here. > > + * The cpumask above contains only CPUs that were running > > tasks > > + * not using broadcast TLB flushing. > > + */ > > + if (cpu_feature_enabled(X86_FEATURE_INVLPGB) && batch- > > >used_invlpgb) { > > + tlbsync(); > > + migrate_enable(); >=20 > Maybe someone mentioned it before, but I would emphasize that I do > not=20 > think that preventing migration for potentially long time is that > great. >=20 > One alternative solution would be to set a bit on cpu_tlbstate, that=20 > when set, you'd issue a tlbsync on context switch. >=20 > (I can think about other solutions, but I think the one I just > mentioned=20 > is the cleanest one). It is clean, but I'm not convinced it is good enough. We need to guarantee that the INVLPGBs have finished before we free the pages. Running a TLBSYNC at the next context switch could mean that TLBSYNC won't run until after the pages have been freed. In practice it is probably good enough, since it would be simpler for TLBSYNC to return once all pending (older) INVLPGBs have finished, but it's not architecturally guaranteed. We could send an IPI to remote CPUs in order for them to call TLBSYNC, but is that really better? --=20 All Rights Reversed.