Received: by 2002:a05:6a10:8395:0:0:0:0 with SMTP id n21csp599587pxh; Tue, 9 Nov 2021 15:58:43 -0800 (PST) X-Google-Smtp-Source: ABdhPJxm9Tbxp6KOzZUyjUpKw/x6vCZTs1KLRk4UFe741U776izUFhB/rOPXgzbcs/AVx6jWFOSj X-Received: by 2002:a92:c244:: with SMTP id k4mr8548245ilo.293.1636502323691; Tue, 09 Nov 2021 15:58:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636502323; cv=none; d=google.com; s=arc-20160816; b=nj4yElyhQ/GAOaKQEYwEpAlhp+noc2TPpL6TaTHZiGpDS1w10mP7k/erli42ypNFp+ X5gBUlmVwmb80Emox0vKEy/JCxb2pRyYxiPrYP43u3eUE9vc1Yvyv7jcSG6oQcKhFzl/ kIehEd6c1hsnM7Mnuwl7+0mcKH3+uB5OfhQxh19L2amErArQtEMKUxTGMXmiHqDKRUN2 x/Plydvty063Pc63qjUCeBRLbJuuP5bKNiB22Q9v3GI3ywthP4CaPy8j5P49JwVhzLny XO8Psq3CoGVattbcDchWjuogp9QyiJfvIlfRRV87D7IC96/uizUa9Kr6Apb1K91mSrce aq1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=vyGiGFmInYsOOYXIgljtlU1Xdbu3aDgv1IRplXS9Xrk=; b=BHFJYLHV3VKFNxERYX5yNBPfZaLVdMi7LZf4zeA+i5LScjpeBi/z04iFhrSIZ9/Bhw CFIQdF7NStw2i0dWGzgrq2+lwKXS5ddKTaEYA11p63u2uR9R9FuqGKnQuXRT3A++UyQ/ NQWpZRv3MRsc4FUYGpNMle/NmoStaMU34wsB4lVC0P/MfSrTo7utOX00gsgWIi4Ip5aL +E5iDwGzD6k5fHacLmTVizPF+6znDTxQr+2pcN/wyv9e4zhLwBhbd4NVFd8FSzwbbD0l V3WX7X7RUQqTbuvmHJp+VZlsOHD2rWU7/nzh6WyKERft6mgMWht2aa1loS03wMkXwEyG +LxA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f11si50676753ila.39.2021.11.09.15.58.30; Tue, 09 Nov 2021 15:58:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234935AbhKIPDm (ORCPT + 97 others); Tue, 9 Nov 2021 10:03:42 -0500 Received: from mga14.intel.com ([192.55.52.115]:26047 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234372AbhKIPDl (ORCPT ); Tue, 9 Nov 2021 10:03:41 -0500 X-IronPort-AV: E=McAfee;i="6200,9189,10162"; a="232701154" X-IronPort-AV: E=Sophos;i="5.87,220,1631602800"; d="scan'208";a="232701154" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Nov 2021 07:00:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.87,220,1631602800"; d="scan'208";a="564028871" Received: from ranerica-svr.sc.intel.com ([172.25.110.23]) by fmsmga004.fm.intel.com with ESMTP; 09 Nov 2021 07:00:48 -0800 Date: Tue, 9 Nov 2021 07:00:01 -0800 From: Ricardo Neri To: Peter Zijlstra Cc: "Rafael J. Wysocki" , Daniel Lezcano , linux-pm@vger.kernel.org, x86@kernel.org, linux-doc@vger.kernel.org, Len Brown , Srinivas Pandruvada , Aubrey Li , Amit Kucheria , Andi Kleen , Tim Chen , "Ravi V. Shankar" , Ricardo Neri , linux-kernel@vger.kernel.org Subject: Re: [PATCH 5/7] thermal: intel: hfi: Enable notification interrupt Message-ID: <20211109150001.GA20404@ranerica-svr.sc.intel.com> References: <20211106013312.26698-1-ricardo.neri-calderon@linux.intel.com> <20211106013312.26698-6-ricardo.neri-calderon@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 08, 2021 at 10:01:04AM +0100, Peter Zijlstra wrote: > On Fri, Nov 05, 2021 at 06:33:10PM -0700, Ricardo Neri wrote: > > + /* > > + * On most systems, all CPUs in the package receive a package-level > > + * thermal interrupt when there is an HFI update. Since they all are > > + * dealing with the same update (as indicated by the update timestamp), > > + * it is sufficient to let a single CPU to acknowledge the update and > > + * schedule work to process it. > > + */ > > That's pretty crap hardware behaviour. Is there really no way to steer > these interrupts? The HFI is a package-level thermal interrupt. Hence, all CPUs get it. AFAIK there is no way to steer the interrupts. Thanks and BR, Ricardo