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 C3BD5C77B7F for ; Fri, 27 Jun 2025 10:25:29 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 682B66B00CC; Fri, 27 Jun 2025 06:25:29 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 65A6A6B00CE; Fri, 27 Jun 2025 06:25:29 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 571146B00CF; Fri, 27 Jun 2025 06:25:29 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 477986B00CC for ; Fri, 27 Jun 2025 06:25:29 -0400 (EDT) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id E872C104810 for ; Fri, 27 Jun 2025 10:25:28 +0000 (UTC) X-FDA: 83600798736.24.F1F8235 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) by imf28.hostedemail.com (Postfix) with ESMTP id 41E63C0004 for ; Fri, 27 Jun 2025 10:25:26 +0000 (UTC) Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=bMcd4YQF; spf=none (imf28.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 198.175.65.12) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1751019927; 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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=jLmtfp+H9NX1lLACuiaNJa4mHAoaed68FQKH9JpItWk=; b=A/vSVd+GhGbDr/XAYGfCwsS89PlB+9jHfNitgRBWiV6esuZ0SNTepgvcLcbqnnta0fB4oS VAeP6ZAnDFyYw5X2y9PRUnxqVRq/2tIkXttsM6Z1haaPZqsx259KkrV3FVgITlc0oToRsG 6xj8jqWfsc7ZpaM9KqpT3T5/xXxJOxg= ARC-Authentication-Results: i=1; imf28.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=bMcd4YQF; spf=none (imf28.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 198.175.65.12) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1751019927; a=rsa-sha256; cv=none; b=k0FCN0fdBplyj1W2ON3FY2IxWyRLvF8lGD5rY1wFc3BChAKxgbxbqXC8U+m6b1kgP+Q917 Upd0UDou/Qt53bDVtXNsMqqMjua2MOsUOtB01LnHSr6aK/kRNqp0PPfngN3VEtrmXFf5sR d8TZmd7FKtfEWCo4t/HZlEYDjJPlvK8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1751019926; x=1782555926; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=ia6n5UXAj5uKiKTZr/E2V2AjNnYEG4HQ2T/pwQJGYEo=; b=bMcd4YQFJ2JGSnEoYnazuajmBSwPvKTmYPjRLP7tFxxRurKDQUHLiY96 TR4eBS0yMVkAQMJOMXfo8MOPwxjsXNrVeX6hJr/FXY/qMJJ0jyl2K16yh 7IJOfrxIryob33LFbzemp4tOj649raRS5ctJT0WyfQGmHpQvQUpbhow8a +wHtt2FYIyXuCnnWHyfpi0T5TdwhYl/8H9oGnqdAPrcmgZfdkOMDQRpsQ rrDollHppazjXjvgXMVqyAp/oPqzk7sOpJRR8w/nGiFA7ITt6JDsvGQr/ IEU9JGgWlY6jkOZD27jjeLPZ2N/Xjs0hzwGxYctKaNmN7LZtUqv996Gcr w==; X-CSE-ConnectionGUID: I98v3goiRWm4p6oP4diB8A== X-CSE-MsgGUID: QM+cQRCNS1Wfq6J3Uj5E4Q== X-IronPort-AV: E=McAfee;i="6800,10657,11476"; a="64769540" X-IronPort-AV: E=Sophos;i="6.16,270,1744095600"; d="scan'208";a="64769540" Received: from fmviesa009.fm.intel.com ([10.60.135.149]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Jun 2025 03:25:25 -0700 X-CSE-ConnectionGUID: mXCvdDVURbaMvopFv8zAUg== X-CSE-MsgGUID: 3qOmJE47RxSQg2u5J9xsPQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,270,1744095600"; d="scan'208";a="153071076" Received: from black.fi.intel.com ([10.237.72.28]) by fmviesa009.fm.intel.com with ESMTP; 27 Jun 2025 03:25:14 -0700 Received: by black.fi.intel.com (Postfix, from userid 1000) id A5BAD6A; Fri, 27 Jun 2025 13:25:12 +0300 (EEST) Date: Fri, 27 Jun 2025 13:25:12 +0300 From: "Kirill A. Shutemov" To: Dave Hansen Cc: Borislav Petkov , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Peter Zijlstra , Ard Biesheuvel , "Paul E. McKenney" , Josh Poimboeuf , Xiongwei Song , Xin Li , "Mike Rapoport (IBM)" , Brijesh Singh , Michael Roth , Tony Luck , Alexey Kardashevskiy , Alexander Shishkin , Jonathan Corbet , Sohil Mehta , Ingo Molnar , Pawan Gupta , Daniel Sneddon , Kai Huang , Sandipan Das , Breno Leitao , Rick Edgecombe , Alexei Starovoitov , Hou Tao , Juergen Gross , Vegard Nossum , Kees Cook , Eric Biggers , Jason Gunthorpe , "Masami Hiramatsu (Google)" , Andrew Morton , Luis Chamberlain , Yuntao Wang , Rasmus Villemoes , Christophe Leroy , Tejun Heo , Changbin Du , Huang Shijie , Geert Uytterhoeven , Namhyung Kim , Arnaldo Carvalho de Melo , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org, linux-mm@kvack.org, Yian Chen Subject: Re: [PATCHv6 01/16] x86/cpu: Enumerate the LASS feature bits Message-ID: References: <20250620135325.3300848-2-kirill.shutemov@linux.intel.com> <20250620163504.GCaFWNuI-8QFqAM0yI@fat_crate.local> <6y2iqv6c2idn7yebaec7tyhzl5zcsrwqq4lcsokumlqeophzaf@ljnmxorblgcj> <20250620182943.GDaFWolxhwogB2tTxb@fat_crate.local> <20250623102105.GCaFkqkatFSbyl1YeN@fat_crate.local> <20250626151837.GFaF1kzfLtesXLqaAQ@fat_crate.local> <20250626160707.GGaF1wK5tW37P6xt0O@fat_crate.local> <2768baad-1b1f-40c2-9cd9-9f4489e14f4d@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2768baad-1b1f-40c2-9cd9-9f4489e14f4d@intel.com> X-Rspam-User: X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 41E63C0004 X-Stat-Signature: dg17mke65ffnbp46zdh3ojmkpmzp3qq5 X-HE-Tag: 1751019926-857567 X-HE-Meta: U2FsdGVkX1+c4bonhM4EEWS8ty2EXEUz4aVYmtZh8DMhaSImoee2bjVAJqCHm5WmzeOc8pNKlJSGfSQA6V0HQ7+h7aAZxAqwU3EBm7bJqKgf6kR2067NnDvt2lIytKid2OnreE7tffSGmk4kIqTVyOW1jDKa9pn6ztiAAajSihssG/BLMTzsA8Lx4IToesx6fCo5AwhW3ZoFUl1lf1G0zZbxTj3gWquwTtWTHwrVNKMnVZo2h+eFo0uNmeA8XdQavq6vRqyBX3PCwRETIDmWO3n8toqtQ1yymzUSm49i4SQnFpYxA0lqkooS4O0EyzBgGmFtF9CqGTGuPA3MFmEIkQidSd9ImJ/s8qpoORz2GsxPBQqP530ndc8IvO7m1Rekz0uSWughBF/4N3kZukme5fomjZkCD2avsIypFqOK+JzsjfQjABsY0Gq2zL/Xg4md9+tCLVZJZ7lMJHt14ys9nejvD+kCFa9+wOxTJuZiFA/yMSTOsO2Jn5lmpUrVI7qttrZxOGvInnXsqprmr7N9bsFtI/7gaXsjHdwqnItLWtuOysyVhTlj80tZVbGxqwsfDblaziy25omwburAYe99OGHr+fH+rnuxEjtdvVoHnfuDW34EDeOAuaVLDcIvAj0Bjc0g8u+T45KUDsafDy9/eXJ7sYEWLc+4ITmUPdpbgrOOfjGRVfMA3oz4KWGkcBdqNbeR8b1ixYg9+r007heRQuUsrMrTyNqzbXvbtyGGxtd/NIqV37UrF62XRwheNwtIjo8UpL4uV/kwgTCedZR82B0Reirk/cA6c3djyq6XVgt7sNbHaA/7YHejIAXw8pbnD3OR6cgKbyepWNXpYkY/YfFzRYyriIOKpIuaNR3M13E91RpaECoWoFp6FV3VcG3l2UfZ1n/bJQtbtq2p+QQO/CAGyQY2u9FclIY80notSQQ5Zo8P7KR2VI46IdEqWjXwLnwwcbcC+Sk7hg7CmwB mDNpuc0N 33knUzkG+iQcUvsjfXr/qOBWknHWvClen1UfURxKeDJrqsnRIAVliZ+Ej3xrpAmZU6RqHWxNY3rlWcGK7a4oW0uWDSFRw+1PF3CDb71K+8AiqnYbt+I0nRS8zrYI5/qqkYmPiDSFNOgvaSECwB55fn4pO8QqSJpQUmtRN2D3KZYBwQErXjXQE2X8tjpJcXkEWoIo3x5vFUc23Kd3g1sDK0+mV83iFsQPSisJO 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: List-Subscribe: List-Unsubscribe: On Thu, Jun 26, 2025 at 10:21:23AM -0700, Dave Hansen wrote: > On 6/26/25 09:07, Borislav Petkov wrote: > >> Makes more sense? > > I meant this crap, ofc: > > > > switch (bug) { > > case X86_BUG_CPU_MELTDOWN: > > if (boot_cpu_has(X86_FEATURE_PTI)) > > return sysfs_emit(buf, "Mitigation: PTI\n"); > > > > This should say "Mitigation: LASS" if LASS is enabled... > > > > Which begs the question: how do LASS and PTI interact now? > > Maybe my babbling about LASS mitigation Meltdown was ill considered. It > seems that I've just muddied the waters. > > All the real LASS-capable hardware also has RDCL_NO=1 which is the > _actual_ x86 Meltdown mitigation. Those systems are not vulnerable to > Meltdown in the first place. > > They should say: "Not affected" for Meltdown, both before and after LASS. Right. To best of my knowledge, SLAM is the only known vulnerability LASS fixes directly so far. So, we want an entry for SLAM? I don't think it is very useful as we don't allow LAM if LASS is missing. -- Kiryl Shutsemau / Kirill A. Shutemov