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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B5E59C3F6B0 for ; Sat, 30 Jul 2022 02:31:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239779AbiG3Cb4 (ORCPT ); Fri, 29 Jul 2022 22:31:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54010 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232937AbiG3Cbz (ORCPT ); Fri, 29 Jul 2022 22:31:55 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B6A03F5B0; Fri, 29 Jul 2022 19:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1659148313; x=1690684313; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=PcbwJg9Nq+orwj9qt2TIBWrJonHyULIKW9jq5xBZJlY=; b=DWC4JAFU8zH/m7E92G/WNCaD8kTAddLJ/K9O/Gsp56vkcWcYHKyEC7jG HyUFahuiZi1zgo/nUueelpxhAh21oF392wOSXkfUQfiicymXTqaZANiNv GlZDe6KesyjqxPqebyqmpJ/w6KoY7LE0qcqzws+qsl7da2ST/q+jCczE1 SeI8vaZlUZuz52GE5WqeQf0LwvqaSAyNbED5JGRLbs8OwpSVE3X/FUwe+ IAFv2BVOSDVVa6nZazpLceJjPA0NNn0ouC5MO8bVSCHE90FOp4oFFyNIJ RlAeUhITILNX/bO7m5usK67DpqvuWOcjz0HizKXMWwAxdF9Xz5lcIcbEa Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10423"; a="286440000" X-IronPort-AV: E=Sophos;i="5.93,202,1654585200"; d="scan'208";a="286440000" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2022 19:31:53 -0700 X-IronPort-AV: E=Sophos;i="5.93,202,1654585200"; d="scan'208";a="629589983" Received: from unknown (HELO desk) ([10.252.135.102]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2022 19:31:52 -0700 Date: Fri, 29 Jul 2022 19:31:51 -0700 From: Pawan Gupta To: Borislav Petkov Cc: Jonathan Corbet , Thomas Gleixner , Ingo Molnar , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, tony.luck@intel.com, antonio.gomez.iglesias@linux.intel.com, Daniel Sneddon , andrew.cooper3@citrix.com, Josh Poimboeuf Subject: Re: [RESEND RFC PATCH] x86/bugs: Add "unknown" reporting for MMIO Stale Data Message-ID: <20220730023151.kogebjrhsvhitklj@desk> References: <20220729022851.mdj3wuevkztspodh@desk> <20220729173609.45o7lllpvsgjttqt@desk> <20220729214627.wowu5sny226c5pe4@desk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Sat, Jul 30, 2022 at 12:02:34AM +0200, Borislav Petkov wrote: > On Fri, Jul 29, 2022 at 02:46:27PM -0700, Pawan Gupta wrote: > > Let me see if there is a way to distinguish between 4. and 5. below: > > > > CPU category X86_BUG_MMIO_STALE_DATA X86_BUG_MMIO_UNKNOWN > > ----------------------------------------------------------------------------------------------- > > 1. Known affected (in cpu list) 1 0 > > 2. CPUs with HW immunity (MMIO_NO=1) 0 0 > > 3. Other vendors 0 0 > > 4. Older Intel CPUs 0 1 > > 5. Not affected current CPUs (but MMIO_NO=0) 0 ? > > Not affected current CPUs should be arch_cap_mmio_immune() == true, no? That would be true in most cases, with some exceptions like systems that did not update the microcode.