Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp1226629rwb; Thu, 22 Sep 2022 11:52:59 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7+9/2uD8xU/BbJqtX8TYF80cqeGN3cqcj7i0ei858tjPZlY/4MjaDHhzHZmjarLgVPb0V8 X-Received: by 2002:a17:907:b0e:b0:77a:d97d:9afc with SMTP id h14-20020a1709070b0e00b0077ad97d9afcmr3984949ejl.199.1663872779006; Thu, 22 Sep 2022 11:52:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663872778; cv=none; d=google.com; s=arc-20160816; b=els5a3l83TBAzxmsXlRYWO5OpYv4iAOQlicf6sbPNUNXJDQbtSmbWDA8lYG0b6IJnz ispHrdSJ4THTlaFS/6S5ml+Ebs8gMjrOVQNf7ldb6NFslt5gI83F1W5QfoIEsW/hXgTX 1Er9mVyE/alriS45R1D2MN9qzyYbBhROqEhib1b70ikReNIh25ZXo2vtHQDK0UXdoTDQ OlpzoRIaz4lMlE6l8TEU+22lGhoI7CXvknoRzahSRbVsXO1gSX9XtXXOT+TrVLXMDfln xn+msPIqw2Ps1awpCtmkCnHW9qpGfP22Ma2f8zc7G2l63jl1kU5z/5A6roMn0hBnJP8k fKHg== 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=6/CgiTjji/v7PCfXQAssBbzLC+ytfhhRxGg/TdiLjdI=; b=06o+97B7+YsaL4xNCTjP+6bLBgP1lJNjLWHS/d5sWnX1N6ryDnfxArOB/Q95JM2vLS gNvoBEA8Hc4KtLP/jI5ZTliqkJSV/Q6/bCdPvfRkinvm/c6YBUXg3DRZdmOn1VLfQGTN CdwSCKT8PZdzd5Z+JzHqkFuu5ETsADUiURcKzWrJ4H7vygwLypcsYCRf2R8YZZIkeOXB rwkOpmr0ctb6rHKgX/4mapn/Wu6Vyw+e7VikdxpPOtGKtH0kEcVdmmHG79VLUDRitU0a HNIHSNV45sVdTAP8wXJa9KtTLgrrhTrFC/pu7OsHpBZ5Ts2v7hiNTBhyk46ZcBv7OJgV 8LSg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=anQvo6aP; 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=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id gt13-20020a1709072d8d00b00781a32fd847si7382708ejc.917.2022.09.22.11.52.33; Thu, 22 Sep 2022 11:52:58 -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=@intel.com header.s=Intel header.b=anQvo6aP; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232394AbiIVSS0 (ORCPT + 99 others); Thu, 22 Sep 2022 14:18:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57498 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232392AbiIVSSY (ORCPT ); Thu, 22 Sep 2022 14:18:24 -0400 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D86D910912A; Thu, 22 Sep 2022 11:18:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663870703; x=1695406703; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=irvpxRGJNiroM1fXkhuMmUhHwaH1jS9Bj7zSfZHS2YY=; b=anQvo6aPXHB1/aXMtMyd2JhzZviW6g3lc23KwKyZHqzdKSdTEPKTQGyc /QUrg3MVohEdIgsoUSxWACnfkHD24Tjr3jYOLCSmGPf65zsiMD2kRZFZb UywDvHf0/Ed+U2S2QM5zsc2VWBTi8K7qHDmblp08c0InFBL5AlrkwVDyy 9Ndx6C6EQkgq+eWaspsmTNj0sWts8YfG08UGd3lP5o1bp7mU5igLiPqvz IFzo5c18+js1u1+oaB7LtQJf7LaE5qhz/0orqiUcsjd5sCwecoxcjX2Pl 9fmAms5qGgHCCPoTsJi7qaMUAL3TnwGEpvNg4f/2STOLDzoydUuLmOH4R Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10478"; a="300371015" X-IronPort-AV: E=Sophos;i="5.93,337,1654585200"; d="scan'208";a="300371015" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Sep 2022 11:17:55 -0700 X-IronPort-AV: E=Sophos;i="5.93,337,1654585200"; d="scan'208";a="682328889" Received: from sponnura-mobl1.amr.corp.intel.com (HELO [10.209.58.200]) ([10.209.58.200]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Sep 2022 11:17:53 -0700 Message-ID: <9d3d3424-a6d4-4076-87ff-a1c216de79c6@intel.com> Date: Thu, 22 Sep 2022 11:17:53 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH] ACPI: processor_idle: Skip dummy wait for processors based on the Zen microarchitecture Content-Language: en-US To: "Limonciello, Mario" , "Nayak, K Prateek" , "linux-kernel@vger.kernel.org" Cc: "rafael@kernel.org" , "lenb@kernel.org" , "linux-acpi@vger.kernel.org" , "linux-pm@vger.kernel.org" , "dave.hansen@linux.intel.com" , "bp@alien8.de" , "tglx@linutronix.de" , "andi@lisas.de" , "puwen@hygon.cn" , "peterz@infradead.org" , "rui.zhang@intel.com" , "gpiccoli@igalia.com" , "daniel.lezcano@linaro.org" , "Narayan, Ananth" , "Shenoy, Gautham Ranjal" , "Ong, Calvin" , "stable@vger.kernel.org" , "regressions@lists.linux.dev" References: <20220921063638.2489-1-kprateek.nayak@amd.com> <20e78a49-25df-c83d-842e-1d624655cfd7@intel.com> <0885eecb-042f-3b74-2965-7d657de59953@amd.com> <88c17568-8694-940a-0f1f-9d345e8dcbdb@intel.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-9.0 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_HI,SPF_HELO_NONE,SPF_NONE 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 9/22/22 10:48, Limonciello, Mario wrote: > > 2) The title says to limit it to old intel systems, but nothing about this actually enforces that. > It actually is limited to all Intel systems, but effectively won't be used on anything but new > ones because of intel_idle. > > As an idea for #2 you could check for CONFIG_INTEL_IDLE in the Intel case and > if it's not defined show a pr_notice_once() type of message trying to tell people to use > Intel Idle instead for better performance. What does that have to do with *this* patch, though? If you've got CONFIG_INTEL_IDLE disabled, you'll be slow before this patch. You'll also be slow after this patch. It's entirely orthogonal. I can add a "Practically" to the subject so folks don't confuse it with some hard limit that is being enforced: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems BTW, is there seriously a strong technical reason that AMD systems are still using this code? Or is it pure inertia?