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 E3EBFC4332F for ; Wed, 4 Jan 2023 19:07:25 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 64B928E0002; Wed, 4 Jan 2023 14:07:25 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 5D3EA8E0001; Wed, 4 Jan 2023 14:07:25 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 44DFA8E0002; Wed, 4 Jan 2023 14:07:25 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 30C468E0001 for ; Wed, 4 Jan 2023 14:07:25 -0500 (EST) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 0C64140CF7 for ; Wed, 4 Jan 2023 19:07:25 +0000 (UTC) X-FDA: 80318050050.24.D0E2180 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by imf01.hostedemail.com (Postfix) with ESMTP id EE9B84001C for ; Wed, 4 Jan 2023 19:07:21 +0000 (UTC) Authentication-Results: imf01.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=UuwqPXli; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf01.hostedemail.com: domain of dave.hansen@intel.com designates 134.134.136.100 as permitted sender) smtp.mailfrom=dave.hansen@intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1672859242; h=from:from: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:dkim-signature; bh=yl+eu1D9Wa7TWC36tF/B6ZJpLura6tsutRT6N2mJLJM=; b=7G28bssEFgGYkomZLdDIvf2QbGMtk3veRmAHTwvKPcwaw0Bmvnq2l7ECKRWWy++UiaGgIu D0zGh8lcFUBxkQf/I1l+x6/nCe9p6snPvyLKvReO/99j9LIt9FhexaBuE1Q+fLo85PgwuN W9Z83/u8j4bbfhazFuUyUypGMs0yj5A= ARC-Authentication-Results: i=1; imf01.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=UuwqPXli; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf01.hostedemail.com: domain of dave.hansen@intel.com designates 134.134.136.100 as permitted sender) smtp.mailfrom=dave.hansen@intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1672859242; a=rsa-sha256; cv=none; b=b9GinEIfiIwqBiAVcr1SFcA49UGWGY8AVfQdQ/69PN+8A4K1ULw+nJq+jvmfctapKiOTy4 GfKitbq0TKY8VFufpnnGE0+2LG7RrhwUu8z2vmScKo6frkI+WTnxjjnSFQfDmhSpsHLT00 XZsd+YCUYRUEGkEJfhcsqEmJJ2pI/xs= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1672859242; x=1704395242; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=XxNNflySTkyGkLpVJYRC4xsGOhNPakSQIFM+vaB9YCQ=; b=UuwqPXliCHSgGd/aaLhwoq77bKWCf6qe5F6cu3VyTPV3Se1OlXq3H1Fr 9KxGbLIrUp9Ou+fcoETDg14rFKz9U7TU7DEBUMFvfWIyMktW7SMKPiLnn 1cTz9NHKMEdZWRC/IIGgWeoLGxBgfM5SHWl76C6i5XfmJ+grTXd6CwQ9T lGwOPdFOZUatKgTr4ZWKw4Pn+UXPnwA6PoSQNIN3AJtsHy5dz86ZfOVpt pJRWKk7M1fSIoYBo3+GYMwQO7ELF4jfrsDsVGvGjnFM2a1Fl5hvBXSyIx DYRiHbh4pOlvR77TBjYq3aQANiy1EDljbVrjkHPl1cv3dT9Uqn3TiqQcP A==; X-IronPort-AV: E=McAfee;i="6500,9779,10580"; a="386453372" X-IronPort-AV: E=Sophos;i="5.96,300,1665471600"; d="scan'208";a="386453372" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jan 2023 11:07:17 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10580"; a="743959675" X-IronPort-AV: E=Sophos;i="5.96,300,1665471600"; d="scan'208";a="743959675" Received: from cheungbr-mobl.amr.corp.intel.com (HELO [10.209.91.155]) ([10.209.91.155]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jan 2023 11:07:15 -0800 Message-ID: Date: Wed, 4 Jan 2023 11:07:15 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCHv13 01/16] x86: Allow atomic MM_CONTEXT flags setting Content-Language: en-US To: "Kirill A. Shutemov" , Dave Hansen , Andy Lutomirski , Peter Zijlstra Cc: x86@kernel.org, Kostya Serebryany , Andrey Ryabinin , Andrey Konovalov , Alexander Potapenko , Taras Madan , Dmitry Vyukov , "H . J . Lu" , Andi Kleen , Rick Edgecombe , Bharata B Rao , Jacob Pan , Ashok Raj , Linus Torvalds , linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <20221227030829.12508-1-kirill.shutemov@linux.intel.com> <20221227030829.12508-2-kirill.shutemov@linux.intel.com> From: Dave Hansen In-Reply-To: <20221227030829.12508-2-kirill.shutemov@linux.intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspam-User: X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: EE9B84001C X-Stat-Signature: erj4pga3t5r4muz4s7k3b36kbxii4acg X-HE-Tag: 1672859241-284300 X-HE-Meta: U2FsdGVkX18EdzqEronXwSRHDPrhgW9s6VgwaAEIDJBVsCS10ZSjGTYq5dXwanTEJyoY3FuWcjiy6PYSybR/DUV14kfv7wWxiGAU4vOFf85uN4EhNj+aE/hN+LFMOG3W66P93kFEQRu0Cmwp9VqH5w2FuB6PMD+7ytsdu4y988+8tXT25VMn5dGc5L+3q2+5rdbh48jvOEXWcXuR9wMfRCwIuaDDwd/RDhPgkHjwakOjcEz+hOjdzk5YfUbbXq70ttTkLywYcpd4/yy9O91DRgAMgHc+pOQbJu3GrTCvvzJvZlxZlHyuRm2aqc57DdQ55AKHJZ/IFUK+VUWm7ZA5Wz/tlx1JWxvxTxm2mRv9iaPqqFDerfaDNrm3fXp8d6ck6pz8DvTIVYhGMTLZDdS7dWapoi0S3AwpLE54jG2c7CPS5kP30k20yAy8OriE4MK4MBKMf5SWGbAQwD675YviWvYW72roOryCIgjLH0mjjnj4xZVUmgCFcT+Q9zX1P58kcIwfpwBfdbGFCLF9J1i1y46YN8IoTEys8ExIDx/34s66QtjuBg7hRo8fXwyldGzoR8uNAU0tpEtlx7snqPQeAhy6DW4UuUZ9I14GLwP+lLeDDUVI3giEmr9Cr/oJXrEPFDXplcaeMgd9ZaU8Pmvjsl3mx6eaXfe+YK9YJtgUl20S73ZfF/ZNFRTATIjZZ/tpblRMg1arkkB9GwWLc4qAtHM7EbsI6UPKc6V+nALsEBfrwx2r+Diw/NmzAN6prlmuJWJe2snWuFEjUkqUup9Icxs3mNWjcXsrXzad395uXxMqyKdx6L1c1VEw2nccyYatLUQA/QI0H/0RUexsfFHYsxHUIkyCZqgQj9XCCvDJFhk5D4FkVy22lk3Jcb/bJI4Era8/uyqPzI94mNTfnMfE8EjyWN2RRGCyFCydqGP1ssj0+6P1RDvLy6CRz0z4vJcO0dIWZBKj9/WDZJt/Ov0 uIddW0Q9 UxD/Xj0rj53awYCI= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 12/26/22 19:08, Kirill A. Shutemov wrote: > So far there's no need in atomic setting of MM context flags in > mm_context_t::flags. The flags set early in exec and never change > after that. > > LAM enabling requires atomic flag setting. Could you elaborate on this a little more?