Received: by 2002:a05:6358:e9c4:b0:b2:91dc:71ab with SMTP id hc4csp2612310rwb; Sat, 6 Aug 2022 02:41:36 -0700 (PDT) X-Google-Smtp-Source: AA6agR7Yq3g/PC6oUtO2PYrzq7TQuAzl2QKm7HkgRXx8cw+r85trwvmIWgQWwedTzO4QUqeI0VOe X-Received: by 2002:a05:6402:e96:b0:43a:f21f:42a0 with SMTP id h22-20020a0564020e9600b0043af21f42a0mr10283766eda.382.1659778896410; Sat, 06 Aug 2022 02:41:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659778896; cv=none; d=google.com; s=arc-20160816; b=uA0YDF1QeN6jS+4Pn5U/b3PQNGo5+Sn3DuRftxBNDe78U2T6RTxoZ+R0wN9sXPfMca tK+EMifTztOphfkKge+4/ksDWnSC1G2HM9kx7cTbgq2g/cX+NwSeSZOiGWXFVH0ZoHFD FqNO8RWXt/JT1QU4hYvxt2fC6wVEJ7IcPFR4y5bc1Fd3fB5XEPbmcRc4hrd8htMAbDBi adfe7eYLVvRCQjl9CJKB5GdGe30q77gPZDslItV1c/r7/oQDGW4YT0YJZwlTpSCP1VZe /7bzMYx31vSs3X2f0blh/q9UsCzMkntqQ/exxn2FNjn2habLLmf6vaJgt0myM6tCA5uO HXFQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=K/JEm6qsqObxv5k42BECF3rRNZFaVIF4KqwrFKnMaTk=; b=eoy3gSplJNXdMdGJja12a+y50xslcklM25nXApwXHINb///EFXnSHH32y1uULc7cxj UrpI1W9Dj3LqDNHxwvMaDYcMnVxm3pbxYAdXSA17mngLKCza6qHKfdrhd8Uo7lIUo9Ay Ndjq8zCJzIggZD5EGt1Mk0kMuKE66KeIM0Bbv40zOgocWDLcIlfpVaMvkZA8nOAGqQ8+ t7g81qHGYbAR9OAaxrRB18APnvPBvQCRg9yTLaItlF9NTT7xMJ+MoQhLZ+ZLzNQaV7ZV /QMCXXspDUZN+YZLr3MUGqrELlz6WeyL+sVElc1Y8n+s0fm2sC9LrfaYaPVsOy7qvIij g0KA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=XUEJgqyq; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o5-20020a50c905000000b0043bb6c97fa0si1542207edh.75.2022.08.06.02.41.11; Sat, 06 Aug 2022 02:41:36 -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; dkim=pass header.i=@alien8.de header.s=dkim header.b=XUEJgqyq; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241761AbiHFJLf (ORCPT + 99 others); Sat, 6 Aug 2022 05:11:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33956 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230013AbiHFJLd (ORCPT ); Sat, 6 Aug 2022 05:11:33 -0400 Received: from mail.skyhub.de (mail.skyhub.de [IPv6:2a01:4f8:190:11c2::b:1457]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABB3E16583 for ; Sat, 6 Aug 2022 02:11:31 -0700 (PDT) Received: from zn.tnic (p200300ea971b986e329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:971b:986e:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id EABCE1EC064A; Sat, 6 Aug 2022 11:11:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1659777085; h=from:from: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; bh=K/JEm6qsqObxv5k42BECF3rRNZFaVIF4KqwrFKnMaTk=; b=XUEJgqyqcfRJVUKXij21BB7HfTe+CT2HIFR7YHWoac0g6o0m/9Mxr1yniLLpJ1x+NuUD8x UEBPe9/wfWtWgVinboUYy/5nmBvx/wDfh0QpUcYlmxGBBHf41t1lm8Sa+qT/EsPv4FCzJh Ufd9ifoHtmKkvU1ZTpi2CgwYvhTx5Zs= Date: Sat, 6 Aug 2022 11:11:20 +0200 From: Borislav Petkov To: Ingo Molnar Cc: Dave Hansen , ira.weiny@intel.com, Rik van Riel , x86@kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com Subject: Re: [RFC PATCH 5/5] x86/entry: Store CPU info on exception entry Message-ID: References: <20220805173009.3128098-1-ira.weiny@intel.com> <20220805173009.3128098-6-ira.weiny@intel.com> <5d62c1d0-7425-d5bb-ecb5-1dc3b4d7d245@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, 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 On Sat, Aug 06, 2022 at 11:01:06AM +0200, Ingo Molnar wrote: > It's still 2 instructions more than what we had before, while the > fault-time CPU number is only needed infrequently AFAICS. With the amount of logical cores ever increasing and how CPU packages (nodes, L3 sharing, you name it) get more and more complex topology, I'd say the 2 insns to show the CPU number in every exception is a good thing to do. Arguably, we probably should've even done it already... -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette