From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Zhang Rui <rui.zhang@intel.com>, X86 ML <x86@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>,
linux-pm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 2/2] thermal: Move therm_throt there from x86/mce
Date: Mon, 25 Jan 2021 09:25:48 -0800 [thread overview]
Message-ID: <1c0aa438b89eef3681e782d4187422eaf3cd86cb.camel@linux.intel.com> (raw)
In-Reply-To: <20210125171845.GJ23070@zn.tnic>
On Mon, 2021-01-25 at 18:18 +0100, Borislav Petkov wrote:
> On Mon, Jan 25, 2021 at 09:14:35AM -0800, Srinivas Pandruvada wrote:
> > Can the handler, processing architectural features via thermal
> > interrupt, reside in arch/x86 folder or need to be
> > drivers/thermal/intel?
>
> Look at...
>
> > > > @@ -718,7 +699,7 @@ void intel_init_thermal(struct cpuinfo_x86
> > > > *c)
> > > > |
> > > > PACKAGE_THERM_INT_HIGH_ENABLE), h);
> > > > }
> > > >
> > > > - smp_thermal_vector = intel_thermal_interrupt;
> > > > + thermal_set_handler(intel_thermal_interrupt);
>
> ... here. ^
>
> This should answer your question.
Thanks for the answer.
-Srinivas
next prev parent reply other threads:[~2021-01-25 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 13:05 [PATCH v2 0/2] Move ...mce/therm_throt.c to drivers/thermal/ Borislav Petkov
2021-01-25 13:05 ` [PATCH v2 1/2] x86/mce: Get rid of mcheck_intel_therm_init() Borislav Petkov
2021-01-29 18:18 ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2021-01-25 13:05 ` [PATCH v2 2/2] thermal: Move therm_throt there from x86/mce Borislav Petkov
2021-01-25 15:42 ` Zhang Rui
2021-01-25 16:47 ` Borislav Petkov
2021-01-25 17:14 ` Srinivas Pandruvada
2021-01-25 17:18 ` Borislav Petkov
2021-01-25 17:25 ` Srinivas Pandruvada [this message]
2021-01-27 11:07 ` Zhang Rui
2021-01-29 18:18 ` [tip: ras/core] " tip-bot2 for Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2021-02-09 2:27 [PATCH v2 2/2] " Sergey Senozhatsky
2021-02-09 10:16 ` Borislav Petkov
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=1c0aa438b89eef3681e782d4187422eaf3cd86cb.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amitk@kernel.org \
--cc=bp@alien8.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rui.zhang@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