All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Len Brown <lenb@kernel.org>,
	"open list:EDAC-CORE" <linux-edac@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v7] acpi: Issue _OSC call for native thermal interrupt handling
Date: Sat, 26 Mar 2016 05:13:46 -0700	[thread overview]
Message-ID: <1458994426.19816.0.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0hP7F_6Wdd0dS7DRWysQApRUrgo5-XvhWiHHo0VYQwKOQ@mail.gmail.com>

On Sat, 2016-03-26 at 01:56 +0100, Rafael J. Wysocki wrote:
> On Thu, Mar 24, 2016 at 5:07 AM, Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > There are several reports of freeze on enabling HWP (Hardware
> > PStates)
> > feature on Skylake based systems by Intel P states driver. The root
> > cause is identified as the HWP interrupts causing BIOS code to
> > freeze.
> > HWP interrupts uses thermal LVT.
> > Linux natively handles thermal interrupts, but in Skylake based
> > systems
> > SMM will take control of thermal interrupts. This is a problem for
> > several
> > reasons:
> > - It is freezing in BIOS when tries to handle thermal interrupt,
> > which
> > will require BIOS upgrade
> > - With SMM handling thermal we loose all the reporting features of
> > Linux arch/x86/kernel/cpu/mcheck/therm_throt driver
> > - Some thermal drivers like x86-package-temp driver depends on the
> > thermal
> > threshold interrupts
> > - The HWP interrupts are useful for debugging and tuning
> > performance
> > 
> > So we need native handling of thermal interrupts. This requires
> > some
> > way to inform SMM that OS can handle thermal interrupts. This can
> > be
> > done by using _OSC/_PDC under processor scope very early in ACPI
> > initialization flow.
> > The bit 12 of _OSC/_PDC in processor scope defines whether OS
> > supports
> > handling of native interrupts for Collaborative Processor
> > Performance
> > Control (CPPC) notifications. Since HWP is a implementation of
> > CPPC,
> > setting this bit is equivalent to inform SMM that OS is capable of
> > handling thermal interrupts.
> > Refer to this document for details on _OSC/_PDC
> > http://www.intel.com/content/www/us/en/standards/processor-vendor-
> > specific-acpi-specification.html
> > 
> > This change introduces a new function
> > acpi_early_processor_set_osc(),
> > which walks acpi name space and finds acpi processor object and
> > set capability via _OSC method.
> > 
> > Also this change writes HWP status bits to 0 to clear any HWP
> > status
> > bits in intel_thermal_interrupt().
> > 
> > Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel
> > .com>
> 
> I've queued it up, but I have modified the subject and the changelog
> and renamed the new function.
> 
> Please have a look at
> http://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commi
> t/?h=bleeding-edge&id=42341f87ba1bee4c5be95038c24abb69cbcf361a
> and let me know if it makes sense to you.

Looks fine to me.

Thanks,
Srinivas

> 
> Thanks,
> Rafael

      reply	other threads:[~2016-03-26 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24  4:07 [PATCH v7] acpi: Issue _OSC call for native thermal interrupt handling Srinivas Pandruvada
2016-03-26  0:56 ` Rafael J. Wysocki
2016-03-26 12:13   ` Srinivas Pandruvada [this message]

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=1458994426.19816.0.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.