Received: by 2002:a05:6358:e9c4:b0:b2:91dc:71ab with SMTP id hc4csp5015296rwb; Mon, 8 Aug 2022 10:35:17 -0700 (PDT) X-Google-Smtp-Source: AA6agR7H3kfwHfgh5nAd7ctogp8TzCGWxYC1Acxe1o+jhHFjgVXk4KGBWf55u+bcKsLdmneL+S+2 X-Received: by 2002:a63:84c1:0:b0:41b:ebff:f3bf with SMTP id k184-20020a6384c1000000b0041bebfff3bfmr16729709pgd.435.1659980117412; Mon, 08 Aug 2022 10:35:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659980117; cv=none; d=google.com; s=arc-20160816; b=UltQjBl3PHL461C0SQR0dtQq+aUGGqZ4ivVgYspWy7HNdWAZsBJZfuEX/FWmO3f+Z9 kFPEXIxIz0bWv3a8wgXmFuQA0ECv0KYrnFuNB1B0WQkPU5UVRQUbbyf1Z8TvfK/S/E6h eSo7so2H/c36gQoCA8rpvmzv8odyqymVn0ePqwtOb+6Q9xDRuHLwm6DOBsyQUKoVgb1n xKMx5rSWpF3DYBg1csLdMV8P1bMpVGy08Om00gnPKs8G0k872qAa0kBW0J9//bU63ZgJ HxSqObezty4O43r3l5sfGMW06HYXkUWAVS7f9s47yvD91dELBI4l4jhH0WfeyuAavsix H9dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:date:cc:to:from:subject:message-id; bh=CEpiSBvSuq1CLvQyMg0Ds1TiwDoPyQ6+jT6Q13k3L7w=; b=Qu2z1M0VCc64esYygPGIrrkWnDWBRrXAH9FZ+142hZT51dpqQwPsAmwZB4LVpafc3F E18bEnJokOdve0SCSuOzxVRAZK2sF2ZWbxmwgtFNzHL29qmEI+2Eiw5gZdCux3aotpUq ITLNCGqO2xC/Eo/qs9XbpvvIbFT0rKsU09aTp8+XGqMUe1rqQY+ModYVSwA4M9APSjWD /m2gr5cC2g4/itNkWSWqDkaGZ0OqAMZUdb7MbX+iEjfv+RLK885HD3gwArU9WE8fVaBX R3GeqG+ge+VjwNWbcrPKbBjicYX5qodx83SwL7TFJzAVn9J7/pLGp7fExTCMSSyQb0xT t30Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t1-20020a170902e84100b0016d856c7ce7si13822253plg.407.2022.08.08.10.35.02; Mon, 08 Aug 2022 10:35:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243228AbiHHRY5 (ORCPT + 99 others); Mon, 8 Aug 2022 13:24:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33856 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243226AbiHHRY4 (ORCPT ); Mon, 8 Aug 2022 13:24:56 -0400 Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AE020167EB for ; Mon, 8 Aug 2022 10:24:55 -0700 (PDT) Received: from imladris.surriel.com ([96.67.55.152]) by shelob.surriel.com with esmtpsa (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oL6Ue-0008EX-LY; Mon, 08 Aug 2022 13:24:44 -0400 Message-ID: <06dc568d91979a3816af602a00884560cb5ec026.camel@surriel.com> Subject: Re: [RFC PATCH 5/5] x86/entry: Store CPU info on exception entry From: Rik van Riel To: Dave Hansen , Ingo Molnar , Ira Weiny , Andy Lutomirski Cc: Borislav Petkov , x86@kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com Date: Mon, 08 Aug 2022 13:24:43 -0400 In-Reply-To: <01768c70-a012-0d08-cfa5-a7a87ff0a19c@intel.com> References: <20220805173009.3128098-1-ira.weiny@intel.com> <20220805173009.3128098-6-ira.weiny@intel.com> <5d62c1d0-7425-d5bb-ecb5-1dc3b4d7d245@intel.com> <01768c70-a012-0d08-cfa5-a7a87ff0a19c@intel.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-zLfyIRf1FZ4PsR+JaPBx" User-Agent: Evolution 3.42.4 (3.42.4-1.fc35) MIME-Version: 1.0 Sender: riel@shelob.surriel.com X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-zLfyIRf1FZ4PsR+JaPBx Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2022-08-08 at 09:16 -0700, Dave Hansen wrote: > On 8/8/22 04:03, Ingo Molnar wrote: > > > Again, I don't believe this is too much overhead but I don't want > > > people=20 > > > to say it was not discussed. > > Is it necessary to do this, what are the alternatives, can this > > overhead be=20 > > avoided? >=20 > I'm thinking that the whole racy smp_processor_id() thing wasn't so > bad > in the first place. >=20 FWIW, just grabbing the CPU number in show_signal_msg() appears to be good enough for our use.=C2=A0 It will typically show >90% of the errors happening on the CPU core that went bad, which is more than enough to diagnose=C2=A0 that a server has a hardware issue and should probably have the CPU repaired. --=20 All Rights Reversed. --=-zLfyIRf1FZ4PsR+JaPBx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEKR73pCCtJ5Xj3yADznnekoTE3oMFAmLxRtsACgkQznnekoTE 3oPpIQf+M/woay+5/L9lVOq1s9YMpVHckK1DzaJLC9heGr3jDjMXrt9zJYouu2M9 p46Sylwg7nU4zxMKPfV4NMIHd+kDYK73jmF41Ypnm5lbtk+Z6LA/qNElmTlWF3I2 xZA1jpA5KarA+l/9vSdQyfcIJIo8xKxYDV8MLPEoX0EBZh5JA25rUH6dxPn3Rtjd 0DR8namlwZpkkWiWOp3ZzaYFqh0azwQLnrB56hVjHU3ckKunY7nEmn70cWnV9+7d /RSpDNG5MBLs1SFWebF1oWzhbv4XqNMr4KpI6HDVTYw1PmX7uw/G1KzHE7H558Fk KAZc0I/0VuzunNoBWPSEgjfoUCURTw== =gGXL -----END PGP SIGNATURE----- --=-zLfyIRf1FZ4PsR+JaPBx--