Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp9431259rwd; Wed, 21 Jun 2023 07:23:10 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4GuPcFH0nauEcnI3LRloHcSicC6sZoIkAx1cgEPZMNcf6Uth7kspg6/2wAo2HgK412uh74 X-Received: by 2002:a05:6a20:158b:b0:10e:e813:46ed with SMTP id h11-20020a056a20158b00b0010ee81346edmr20085400pzj.43.1687357390709; Wed, 21 Jun 2023 07:23:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687357390; cv=none; d=google.com; s=arc-20160816; b=x37LFw7CjGou92/0ITKRTEEsJvq3vuwuT4TYCq1qRLbXpZ77z9liqkyIr62fkY4FB9 GQzemxhqxKRTFy2FmVb1i0nb6NH2m+aBgeiPIc6Yl6PGvse7FRr6Xr790mwfwFdxjcli 67NDM76nFJyQy0RkB5LB8bg0uvECb7MV15DZcDlnFOY/jD1R01rVMbpocwTdG4HJPVGR oClqgbCTXmbdvo+puptQLNA1wkBOKIjkxn5kWaDXxLR/wjpOSEBN5Og+KHq/jyYO3RyH 9xJkzppsDkz6gXoqHN3I8+vrmfBk0eqlR0uy7WyNYZRPEIMHDhKIe44CMEYIsLzoumJV kC1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=KFZAtgrQch7A5U4wgSpfS/jvQRtXk8ffgaPSS2oGLeU=; b=sHOQyJqMcNCh3sZI9yKzTVe3U6fjT4bxzQAX2NPbA3fjmgNQejTjTpeVrTOxZ+Sop+ oVJcmxbAmCsOp7fE3JLDwUco/lTKSl3jg8lFsVvfyniVJxVVyx3foj72W1j7K2Pg56aY TdK52dddk0qzyRa1LQLKQRM8jy2kTPRGz2s3SCerRUN/PsL8KFPAm+udFnwK4PliGl8l SODj92JyLM+ZBTPznDW3w+Zw8u30NdePFWRkRZgXWasuKPDrx/GIsuyxM6CJ3rowS8bl lfhbBnlO6uOesjsvCJpLhdWgaHZUKMk4V3lWSLQk+yS+/dfcJdNPScuGfQShJMuTJxxq oPkQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=GO1YdxmM; 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=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t188-20020a6378c5000000b0054febefe103si3854925pgc.437.2023.06.21.07.22.55; Wed, 21 Jun 2023 07:23:10 -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=@redhat.com header.s=mimecast20190719 header.b=GO1YdxmM; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230109AbjFUOCL (ORCPT + 99 others); Wed, 21 Jun 2023 10:02:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48656 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232702AbjFUOBh (ORCPT ); Wed, 21 Jun 2023 10:01:37 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A1D971FCE for ; Wed, 21 Jun 2023 07:00:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1687356041; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KFZAtgrQch7A5U4wgSpfS/jvQRtXk8ffgaPSS2oGLeU=; b=GO1YdxmMfiKYXrCzGTVi07JKa2sbQKreQ/cwUGGtOg9luCta44Qwa2bCJwhYPLJqSJUuQA c2ZcVDryx3SlG+oWp77npivd2aPrGnTWZoFb7XcAz74Wa8kpAtSNUcgZZwVcMVL5C2JiOu hKiekj5yfRS4hiQvB9XC6mpD7gS1pm8= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-461-Zv36G5imOcut5ARR-nnz_A-1; Wed, 21 Jun 2023 10:00:38 -0400 X-MC-Unique: Zv36G5imOcut5ARR-nnz_A-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id EFACE382C5D0; Wed, 21 Jun 2023 13:59:52 +0000 (UTC) Received: from [10.22.17.140] (unknown [10.22.17.140]) by smtp.corp.redhat.com (Postfix) with ESMTP id 51F981402C06; Wed, 21 Jun 2023 13:59:52 +0000 (UTC) Message-ID: <7f2424df-1846-6c38-e446-b3d5aa693ecd@redhat.com> Date: Wed, 21 Jun 2023 09:59:52 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v2 2/5] x86/idle: Disable IBRS when cpu is offline Content-Language: en-US To: Peter Zijlstra Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , Josh Poimboeuf , Pawan Gupta , Jacob Pan , Len Brown , linux-kernel@vger.kernel.org, x86@kernel.org, linux-pm@vger.kernel.org, Robin Jarry , Joe Mario References: <20230620140625.1001886-1-longman@redhat.com> <20230620140625.1001886-3-longman@redhat.com> <20230621072313.GA2046280@hirez.programming.kicks-ass.net> From: Waiman Long In-Reply-To: <20230621072313.GA2046280@hirez.programming.kicks-ass.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,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 On 6/21/23 03:23, Peter Zijlstra wrote: > On Tue, Jun 20, 2023 at 10:06:22AM -0400, Waiman Long wrote: >> Commit bf5835bcdb96 ("intel_idle: Disable IBRS during long idle") >> disables IBRS when the CPU enters long idle. However, when a CPU becomes >> offline, the IBRS bit is still set when X86_FEATURE_KERNEL_IBRS is >> enabled. That will impact the performance of a sibling CPU. Mitigate >> this performance impact by clearing all the mitigation bits in SPEC_CTRL >> MSR when offline and restoring the value of the MSR when it becomes >> online again. >> >> Signed-off-by: Waiman Long >> --- >> arch/x86/kernel/smpboot.c | 13 +++++++++++++ >> 1 file changed, 13 insertions(+) >> >> diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c >> index 352f0ce1ece4..5ff82fef413c 100644 >> --- a/arch/x86/kernel/smpboot.c >> +++ b/arch/x86/kernel/smpboot.c >> @@ -84,6 +84,7 @@ >> #include >> #include >> #include >> +#include >> >> /* representing HT siblings of each logical CPU */ >> DEFINE_PER_CPU_READ_MOSTLY(cpumask_var_t, cpu_sibling_map); >> @@ -1838,12 +1839,24 @@ void __noreturn hlt_play_dead(void) >> >> void native_play_dead(void) >> { >> + u64 spec_ctrl = spec_ctrl_current(); >> + >> + if (cpu_feature_enabled(X86_FEATURE_KERNEL_IBRS)) { >> + this_cpu_write(x86_spec_ctrl_current, 0); >> + native_wrmsrl(MSR_IA32_SPEC_CTRL, 0); >> + } >> + >> play_dead_common(); >> tboot_shutdown(TB_SHUTDOWN_WFS); >> >> mwait_play_dead(); >> if (cpuidle_play_dead()) >> hlt_play_dead(); >> + >> + if (cpu_feature_enabled(X86_FEATURE_KERNEL_IBRS)) { >> + native_wrmsrl(MSR_IA32_SPEC_CTRL, spec_ctrl); >> + this_cpu_write(x86_spec_ctrl_current, spec_ctrl); >> + } >> } > play_dead() is marked __noreturn There are different versions of play_dead() in the kernel. Some of them are indeed marked __noreturn like the non-SMP one in arch/x86/kernel/process.c. The native_play_dead() that I am patching isn't one of those. Cheers, Longman