50a9ff6df4
The kernel is moved ahead to version 3.10.0-693.21.1.el7 To summarize: CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1' This is fixed by load fences and is "baked in" and cannot be turned off. CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2' This is fixed by a combination of retpolines and IBPB, or IBRS+IBPB if on skylake. This requires a microcode change in the processors. This feature, if on, has a significant performance impact. It is assumed on unless turned off via the "nospectre_v2" bootarg. CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3' This is fixed by page table isolation using the Kaiser patches. This feature is assumed on unless turned off via the "nopti" bootarg. As of the commit date, we have changed the installer kickstarts to issue both "nopti nospectre_v2" bootargs to minimize realtime impacts by default. The customer will be able to optionally sacrifice performance for extra security at datafill time. Change-Id: Id7c99923f2ee2ee91f77c7bd9940e684eff8b476 Signed-off-by: Jim Somerville <Jim.Somerville@windriver.com>
64 lines
2.4 KiB
Diff
64 lines
2.4 KiB
Diff
From 16210ff52ec2d6b6d8799220fed83ae17a16f694 Mon Sep 17 00:00:00 2001
|
|
Message-Id: <16210ff52ec2d6b6d8799220fed83ae17a16f694.1522795098.git.Jim.Somerville@windriver.com>
|
|
In-Reply-To: <21c11de06542297206c798b405b54a3ec9052aa4.1522795097.git.Jim.Somerville@windriver.com>
|
|
References: <21c11de06542297206c798b405b54a3ec9052aa4.1522795097.git.Jim.Somerville@windriver.com>
|
|
From: Alex Shi <alex.shi@linaro.org>
|
|
Date: Thu, 12 Jan 2017 21:27:03 +0800
|
|
Subject: [PATCH 24/33] CPU / PM: expose pm_qos_resume_latency for CPUs
|
|
|
|
[ commit 37efa4b41ffb31dcdfc3beb97d47992bb2a083e5 from linux-stable ]
|
|
|
|
The cpu-dma PM QoS constraint impacts all the cpus in the system. There is no way
|
|
to let the user to choose a PM QoS constraint per cpu.
|
|
|
|
The following patch exposes to the userspace a per cpu based sysfs file
|
|
in order to let the userspace to change the value of the PM QoS latency
|
|
constraint.
|
|
|
|
This change is inoperative in its form and the cpuidle governors have to
|
|
take into account the per cpu latency constraint in addition to the
|
|
global cpu-dma latency constraint in order to operate properly.
|
|
|
|
BTW
|
|
The pm_qos_resume_latency usage defined in
|
|
Documentation/ABI/testing/sysfs-devices-power
|
|
The /sys/devices/.../power/pm_qos_resume_latency_us attribute
|
|
contains the PM QoS resume latency limit for the given device,
|
|
which is the maximum allowed time it can take to resume the
|
|
device, after it has been suspended at run time, from a resume
|
|
request to the moment the device will be ready to process I/O,
|
|
in microseconds. If it is equal to 0, however, this means that
|
|
the PM QoS resume latency may be arbitrary.
|
|
|
|
Signed-off-by: Alex Shi <alex.shi@linaro.org>
|
|
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
|
|
Signed-off-by: Alex Kozyrev <alex.kozyrev@windriver.com>
|
|
Signed-off-by: Jim Somerville <Jim.Somerville@windriver.com>
|
|
---
|
|
drivers/base/cpu.c | 2 ++
|
|
1 file changed, 2 insertions(+)
|
|
|
|
diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
|
|
index 9cc92a2..daae169 100644
|
|
--- a/drivers/base/cpu.c
|
|
+++ b/drivers/base/cpu.c
|
|
@@ -15,6 +15,7 @@
|
|
#include <linux/percpu.h>
|
|
#include <linux/acpi.h>
|
|
#include <linux/tick.h>
|
|
+#include <linux/pm_qos.h>
|
|
|
|
#include "base.h"
|
|
|
|
@@ -318,6 +319,7 @@ int register_cpu(struct cpu *cpu, int num)
|
|
per_cpu(cpu_sys_devices, num) = &cpu->dev;
|
|
if (!error)
|
|
register_cpu_under_node(num, cpu_to_node(num));
|
|
+ dev_pm_qos_expose_latency_limit(&cpu->dev, 0);
|
|
|
|
#ifdef CONFIG_KEXEC
|
|
if (!error)
|
|
--
|
|
1.8.3.1
|
|
|