From: Peter Zijlstra <peterz@infradead.org>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-pm@vger.kernel.org, x86@kernel.org,
linux-doc@vger.kernel.org, Len Brown <len.brown@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Aubrey Li <aubrey.li@linux.intel.com>,
Amit Kucheria <amitk@kernel.org>, Andi Kleen <ak@linux.intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
Ricardo Neri <ricardo.neri@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] thermal: intel: hfi: Enable notification interrupt
Date: Mon, 8 Nov 2021 10:01:04 +0100 [thread overview]
Message-ID: <YYjnUM/v8LmtnBq3@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20211106013312.26698-6-ricardo.neri-calderon@linux.intel.com>
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?
next prev parent reply other threads:[~2021-11-08 9:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 1:33 [PATCH 0/7] Thermal: Introduce the Hardware Feedback Interface for thermal and performance management Ricardo Neri
2021-11-06 1:33 ` [PATCH 1/7] x86/Documentation: Describe the Intel Hardware Feedback Interface Ricardo Neri
2021-11-30 9:24 ` Daniel Lezcano
2021-11-30 10:20 ` Srinivas Pandruvada
2021-11-06 1:33 ` [PATCH 2/7] x86: Add definitions for " Ricardo Neri
2021-11-06 10:30 ` Borislav Petkov
2021-11-06 22:01 ` Ricardo Neri
2021-11-06 1:33 ` [PATCH 3/7] thermal: intel: hfi: Minimally initialize the " Ricardo Neri
2021-11-08 8:47 ` Peter Zijlstra
2021-11-09 2:28 ` Ricardo Neri
2021-11-24 14:09 ` Rafael J. Wysocki
2021-11-30 3:20 ` Ricardo Neri
2021-11-30 3:55 ` Srinivas Pandruvada
2021-11-30 13:45 ` Ricardo Neri
2021-11-06 1:33 ` [PATCH 4/7] thermal: intel: hfi: Handle CPU hotplug events Ricardo Neri
2021-11-24 14:48 ` Rafael J. Wysocki
2021-11-30 13:21 ` Ricardo Neri
2021-11-30 13:32 ` Rafael J. Wysocki
2021-12-02 23:43 ` Ricardo Neri
2021-11-06 1:33 ` [PATCH 5/7] thermal: intel: hfi: Enable notification interrupt Ricardo Neri
2021-11-08 9:01 ` Peter Zijlstra [this message]
2021-11-09 15:00 ` Ricardo Neri
2021-11-08 9:07 ` Peter Zijlstra
2021-11-09 2:26 ` Ricardo Neri
2021-11-09 8:48 ` Peter Zijlstra
2021-11-09 12:54 ` Srinivas Pandruvada
2021-11-06 1:33 ` [PATCH 6/7] thermal: netlink: Add a new event to notify CPU capabilities change Ricardo Neri
2021-11-09 12:39 ` Lukasz Luba
2021-11-09 13:23 ` Srinivas Pandruvada
2021-11-09 13:53 ` Lukasz Luba
2021-11-09 14:15 ` Srinivas Pandruvada
2021-11-09 17:51 ` Lukasz Luba
2021-11-09 21:25 ` Srinivas Pandruvada
2021-11-30 9:29 ` Daniel Lezcano
2021-12-09 16:03 ` Ricardo Neri
2021-12-09 16:57 ` Daniel Lezcano
2021-12-09 17:39 ` Srinivas Pandruvada
2021-11-06 1:33 ` [PATCH 7/7] thermal: intel: hfi: Notify user space for HFI events Ricardo Neri
2021-11-24 15:18 ` Rafael J. Wysocki
2021-11-26 6:23 ` Srinivas Pandruvada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YYjnUM/v8LmtnBq3@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=amitk@kernel.org \
--cc=aubrey.li@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox