From: Tim Chen <tim.c.chen@linux.intel.com>
To: rjw@rjwysocki.net, tglx@linutronix.de, mingo@redhat.com, bp@suse.de
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
x86@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
peterz@infradead.org, Tim Chen <tim.c.chen@linux.intel.com>,
jolsa@redhat.com
Subject: [PATCH v7 7/8] acpi: bus: Set _OSC for diverse core support
Date: Thu, 10 Nov 2016 14:36:39 -0800 [thread overview]
Message-ID: <30b355f2d26746edfdb1ab298f1febebaf035f40.1478805832.git.tim.c.chen@linux.intel.com> (raw)
In-Reply-To: <cover.1478805832.git.tim.c.chen@linux.intel.com>
In-Reply-To: <cover.1478805832.git.tim.c.chen@linux.intel.com>
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Set the OSC_SB_CPC_DIVERSE_HIGH_SUPPORT (bit 12) to enable diverse
core support.
This is required to inform BIOS the support of Intel Turbo Boost Max
Technology 3.0 feature.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
---
drivers/acpi/bus.c | 3 +++
include/linux/acpi.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index 2f381ba..806db0d 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -338,6 +338,9 @@ static void acpi_bus_osc_support(void)
}
#endif
+ if (IS_ENABLED(CONFIG_SCHED_ITMT))
+ capbuf[OSC_SUPPORT_DWORD] |= OSC_SB_CPC_DIVERSE_HIGH_SUPPORT;
+
if (!ghes_disable)
capbuf[OSC_SUPPORT_DWORD] |= OSC_SB_APEI_SUPPORT;
if (ACPI_FAILURE(acpi_get_handle(NULL, "\\_SB", &handle)))
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 689a8b9..639fc63 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -469,6 +469,7 @@ acpi_status acpi_run_osc(acpi_handle handle, struct acpi_osc_context *context);
#define OSC_SB_CPCV2_SUPPORT 0x00000040
#define OSC_SB_PCLPI_SUPPORT 0x00000080
#define OSC_SB_OSLPI_SUPPORT 0x00000100
+#define OSC_SB_CPC_DIVERSE_HIGH_SUPPORT 0x00001000
extern bool osc_sb_apei_support_acked;
extern bool osc_pc_lpi_support_confirmed;
--
2.5.5
next prev parent reply other threads:[~2016-11-10 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 22:36 [PATCH v7 0/8] Support Intel Turbo Boost Max Technology 3.0 Tim Chen
2016-11-10 22:36 ` [PATCH v7 1/8] sched: Extend scheduler's asym packing Tim Chen
2016-11-22 10:09 ` Peter Zijlstra
2016-11-22 20:21 ` Tim Chen
2016-11-10 22:36 ` [PATCH v7 2/8] x86/topology: Define x86's arch_update_cpu_topology Tim Chen
2016-11-10 22:36 ` [PATCH v7 3/8] x86: Enable Intel Turbo Boost Max Technology 3.0 Tim Chen
2016-11-10 22:36 ` [PATCH v7 4/8] x86/sysctl: Add sysctl for ITMT scheduling feature Tim Chen
2016-11-10 22:36 ` [PATCH v7 5/8] x86/sched: Add SD_ASYM_PACKING flags to x86 ITMT CPU Tim Chen
2016-11-10 22:36 ` [PATCH v7 6/8] acpi: bus: Enable HWP CPPC objects Tim Chen
2016-11-10 22:36 ` Tim Chen [this message]
2016-11-10 22:36 ` [PATCH v7 8/8] cpufreq: intel_pstate: Use CPPC to get max performance Tim Chen
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=30b355f2d26746edfdb1ab298f1febebaf035f40.1478805832.git.tim.c.chen@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bp@suse.de \
--cc=jolsa@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).