Add MSR and bit definitions for SPEC_CTRL, PRED_CMD and ARCH_CAPABILITIES.
See Intel's 336996-Speculative-Execution-Side-Channel-Mitigations.pdf
Signed-off-by: David Woodhouse
Reviewed-by: Greg Kroah-Hartman
---
arch/x86/include/asm/msr-index.h | 12
1 file changed, 12 insertions(
Add three feature bits exposed by new microcode on Intel CPUs for
speculation control.
Signed-off-by: David Woodhouse
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Borislav Petkov
---
arch/x86/include/asm/cpufeatures.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/include/asm/
Also, for CPUs which don't speculate at all, don't report that they're
vulnerable
to the Spectre variants either.
Leave the cpu_no_meltdown[] match table with just X86_VENDOR_AMD in it for now,
even though that could be done with a simple comparison, on the assumption that
we'll have more to add.
This is a pure feature bits leaf. We have two AVX512 feature bits in it
already which were handled as scattered bits, and I'm about to add three
more from this leaf for speculation control features.
Signed-off-by: David Woodhouse
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Borislav Petkov
---
Add the basic CPUID and MSR definitions for AMD and Intel, followed by
the complete no-brainer: Disable KPTI on Intel CPUs which set the
RDCL_NO bit to say that they don't need it, as well as others which are
known not to speculate such as old Atoms and even older 32-bit chips.
Alan will continu
On Thu, Jan 25, 2018 at 09:58:20AM +0100, Peter Zijlstra wrote:
> On Wed, Jan 24, 2018 at 04:36:41PM -0800, Tim Chen wrote:
> > These two patches provide optimization to skip IBPB for this
> > commonly encountered scenario:
> > We could switch to a kernel idle thread and then back to the original
>
On 25 January 2018 at 16:55, Arnd Bergmann wrote:
> On Thu, Jan 25, 2018 at 9:05 AM, Baolin Wang wrote:
>> @@ -2554,7 +2554,7 @@ static int kdb_summary(int argc, const char **argv)
>> kdb_printf("domainname %s\n", init_uts_ns.name.domainname);
>> kdb_printf("ccversion %s\n", __st
On 24/01/18 11:13, Bartosz Golaszewski wrote:
Hi Srinivas,
I don't see this series in next - is it going to miss this merge window?
Thanks for your patience.
In general, I pick stuff which are sent before rc5-rc6 and send it to
Greg KH for inclusion in char-misc tree.
These patches wi
On Wed, Jan 24, 2018 at 08:29:14PM +, Corentin Labbe wrote:
> Last use of IOMMU_STRESS was removed in commit 29b68415e335 ("x86: amd_iommu:
> move to drivers/iommu/")
> 6 years after, we could remove it.
>
> Signed-off-by: Corentin Labbe
> ---
> arch/x86/Kconfig.debug | 8
> 1 file
From: Tianyu Lan
Some hv_get/set** helper functions in ring_buffer code are
only called once or not used. This patch is to clear up these codes.
Signed-off-by: Tianyu Lan
---
Change since v1:
Clear up more hv_get/set** functions.
---
drivers/hv/ring_buffer.c | 49 --
From: yuzhoujian
Introduce a new option to print counts after N milliseconds
and update perf-stat documentation accordingly.
Show below is the output of the new option for perf stat.
$ perf stat --time 2000 -e cycles -a
Performance counter stats for 'system wide':
From: yuzhoujian
Introduce a new option to print counts for fixed number of times
and update perf-stat documentation accordingly.
Show below is the output of the new option for perf stat.
$ perf stat -I 1000 --interval-count 2 -e cycles -a
# time counts uni
FYI:
A-EON AmigaOne X1000 (CPU P.A. Semi PWRficient PA6T-1682M with two PA6T
cores):
/sys/devices/system/cpu/vulnerabilities/
-r--r--r-- 1 root root 4096 Jan 25 09:38 meltdown
-r--r--r-- 1 root root 4096 Jan 25 09:38 spectre_v1
-r--r--r-- 1 root root 4096 Jan 25 09:38 spectre_v2
meltdown Vul
From: yuzhoujian
Introduce two new options for perf stat and update perf-stat documentation
accordingly.
The interval-count option can be used to print counts for fixed number of
times, and it should be used specifically with "-I" option.
Show below is the output of the interval-count option fo
On Thu, Jan 25, 2018 at 9:42 AM, David Laight wrote:
> From: Dmitry Vyukov [mailto:dvyu...@google.com]
>> Sent: 25 January 2018 08:33
>>
>> On Wed, Jan 24, 2018 at 6:52 PM, Linus Torvalds
>> wrote:
>> > On Wed, Jan 24, 2018 at 12:54 AM, Rasmus Villemoes
>> > wrote:
>> >>
>> >> I see something si
On Wed, 24 Jan 2018, Palmer Dabbelt wrote:
> It looks like this same irqchip registration mechanism has been copied
> into a handful of ports, including aarch64 and openrisc. I want to use
> this in the RISC-V port, so I thought it would be good to make this
> generic instead.
>
> This patch sim
The comment is confusing. On the one hand, it refers to 32-bit
alignment (struct page alignment on 32-bit platforms), but this
would only guarantee that the 2 lowest bits must be zero. On the
other hand, it claims that at least 3 bits are available, and 3 bits
are actually used.
This is not broken
On Mon, Feb 13, 2017 at 07:42:40PM -0600, Josh Poimboeuf wrote:
> diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> index 6a4bae0..a8b3f1a 100644
> --- a/kernel/sched/idle.c
> +++ b/kernel/sched/idle.c
> @@ -9,6 +9,7 @@
> #include
> #include
> #include
> +#include
>
> #include
>
On 25 January 2018 at 09:41, Maxime Ripard
wrote:
> Hi,
>
> On Wed, Jan 24, 2018 at 03:11:01PM +0100, codekip...@gmail.com wrote:
>> From: Marcus Cooper
>>
>> On the newer SoCs this is set by default to transfer a 0 after
>> each sample in each slot. Add the regmap field to configure this
>> and
On Wed, Jan 24, 2018 at 04:36:41PM -0800, Tim Chen wrote:
> These two patches provide optimization to skip IBPB for this
> commonly encountered scenario:
> We could switch to a kernel idle thread and then back to the original
> process such as:
> process A -> idle -> process A
>
> In such scenario
On Thu, Jan 25, 2018 at 9:05 AM, Baolin Wang wrote:
> @@ -2554,7 +2554,7 @@ static int kdb_summary(int argc, const char **argv)
> kdb_printf("domainname %s\n", init_uts_ns.name.domainname);
> kdb_printf("ccversion %s\n", __stringify(CCVERSION));
>
> - now = __current_kernel_
On Wed, 24 Jan 2018, Lyude Paul wrote:
> Sorry about that! Let me clarify a little bit: this is a problem that shows up
> on mainline. Normally when we suspend the GPU in nouveau, we free the IRQs
> it's using before going into suspend
> (drivers/gpu/drm/nouveau/nvkm/subdev/pci/base.c:88), then res
Attention,
We have deposited the check of your fund ($2,700,000,00USD) through western
union after our finally meeting regarding your fund, All you will do is to
contact Western Union Director Howard Edward Email:(
newwesternunion.office...@list.ru ) He will give you more direction on how you
On Thu, Jan 25, 2018 at 06:22:59PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the rdma tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "init_rcu_head" [drivers/infiniband/ulp/srpt/ib_srpt.ko] undefined!
>
> Caused by commit
>
> a11253142e6d ("IB
Hi!
> On 17.01.2018, at 16:19, David Gstir wrote:
>
> Hi everybody!
>
> Richard and I have been working on extending UBIFS' security features and came
> up with the following concept to add full file contents and metadata
> authentication.
>
> For block devices like eMMCs dm-crypt and dm-veri
Commit-ID: 617ab45c9a8900e64a78b43696c02598b8cad68b
Gitweb: https://git.kernel.org/tip/617ab45c9a8900e64a78b43696c02598b8cad68b
Author: Vitaly Kuznetsov
AuthorDate: Wed, 24 Jan 2018 11:36:29 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 25 Jan 2018 09:40:59 +0100
x86/hyperv: Stop s
Am 24.01.2018 22:40, schrieb Christopher Díaz Riveros:
> Given the following definitions from s2255drv.c
>
> #define LINE_SZ_4CIFS_NTSC 640
> #define LINE_SZ_2CIFS_NTSC 640
> #define LINE_SZ_1CIFS_NTSC 320
>
> and
>
> #define LINE_SZ_4CIFS_PAL 704
> #define LINE_SZ_2C
On Wed, 24 Jan 2018, Andi Kleen wrote:
> On Wed, Jan 24, 2018 at 09:00:48AM -0800, Linus Torvalds wrote:
> > On Wed, Jan 24, 2018 at 6:28 AM, Greg Kroah-Hartman
> > wrote:
> > >
> > > Linus, if there are no objections, can you apply this revert to your
> > > tree now so this doesn't get into 4.15
From: Dmitry Vyukov [mailto:dvyu...@google.com]
> Sent: 25 January 2018 08:33
>
> On Wed, Jan 24, 2018 at 6:52 PM, Linus Torvalds
> wrote:
> > On Wed, Jan 24, 2018 at 12:54 AM, Rasmus Villemoes
> > wrote:
> >>
> >> I see something similar, but at the 30->31 transition, and the
> >> branch-misses
Hi,
On Wed, Jan 24, 2018 at 03:11:01PM +0100, codekip...@gmail.com wrote:
> From: Marcus Cooper
>
> On the newer SoCs this is set by default to transfer a 0 after
> each sample in each slot. Add the regmap field to configure this
> and set it so that it pads the sample with 0s.
>
> Signed-off-b
Hi Akash,
Thank you for the patch.
On Thursday, 25 January 2018 09:34:36 EET Akash Gajjar wrote:
> From: Akash Gajjar
>
> Witth this changes, the driver builds with CONFIG_OF support
Does the driver fail to build with CONFIG_OF at the moment ?
> Signed-off-by: Akash Gajjar
> ---
> drivers/m
On Thu 25-01-18 11:04:23, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Wed 15-11-17 09:00:20, Johannes Weiner wrote:
> > > In any case, Minchan's lock breaking seems way preferable over that
> > > level of headscratching complexity for an unusual case like Shakeel's.
> >
> > agreed! I would go
On Thu, Jan 25, 2018 at 12:37 AM, Stephen Hemminger
wrote:
> On Wed, 24 Jan 2018 14:21:30 +0800
> lantianyu1...@gmail.com wrote:
>
>> From: Tianyu Lan
>>
>> The "next" variable is redundant in hv_get_next_write_location().
>> This patch is to remove it and return write_index directly.
>>
>> Signe
On Fri, Jan 19, 2018 at 11:57:32AM +0100, Enric Balletbo Serra wrote:
> Hi Vito,
>
> 2018-01-17 23:48 GMT+01:00 :
> > On Mon, Dec 18, 2017 at 10:25:33AM +0100, Enric Balletbo Serra wrote:
> >> Hi Vito,
> >>
> >> 2017-12-01 22:33 GMT+01:00 :
> >> > On Wed, Nov 29, 2017 at 10:39:19AM -0800, vcap..
On Wed, Jan 24, 2018 at 6:52 PM, Linus Torvalds
wrote:
> On Wed, Jan 24, 2018 at 12:54 AM, Rasmus Villemoes
> wrote:
>>
>> I see something similar, but at the 30->31 transition, and the
>> branch-misses remain at 1-3% for higher values, until 42 where it drops
>> back to 0%. Anyway, I highly doub
On 01/21/18 06:31, Wolfram Sang wrote:
> From: Tyrel Datwyler
>
> This patch introduces event tracepoints for tracking a device_nodes
> reference cycle as well as reconfig notifications generated in response
> to node/property manipulations.
>
> With the recent upstreaming of the refcount API se
On Wed, Jan 24, 2018 at 07:07:56PM -0800, Palmer Dabbelt wrote:
> The old mechanism for handling IRQs on RISC-V was pretty ugly: the arch
> code looked at the Kconfig entry for our first-level irqchip driver and
> called into it directly.
>
> This patch uses the new 0generic IRQ handling infastruc
On 01/25/18 00:01, Geert Uytterhoeven wrote:
> Hi Frank,
>
> On Thu, Jan 25, 2018 at 7:48 AM, Frank Rowand wrote:
>>> create mode 100644 include/trace/events/of.h
>>
>> mode looks incorrect. Existing files in include/trace/events/ are -rw-rw
>
> Not in my git clone ;-) 644 should be fine.
Hi James,
thanks for the review.
On 2018/1/24 3:07, James Morse wrote:
> Hi Dongjiu Geng,
>
> On 06/01/18 16:02, Dongjiu Geng wrote:
>> RAS Extension add a VSESR_EL2 register which can provide
>> the syndrome value reported to software on taking a virtual
>> SError interrupt exception. This pat
On Wed, 2018-01-24 at 16:36 -0800, Tim Chen wrote:
> It is possible that the last uesr mm that we recorded for a cpu was
> released, and a new mm with identical address was allocated when we
> check it again. We could skip IBPB flush here for the process with
> the new mm.
>
> It is a difficult t
Em Wed, Jan 24, 2018 at 02:54:11PM -0600, Josh Poimboeuf escreveu:
> On Tue, Jan 23, 2018 at 07:38:37PM -0500, Arvind Sankar wrote:
> > We inherited this hack with the original code from the Git project. The
> > select call is invalid as the two fd_set pointers should not be aliased.
> >
> > We co
The .prepare() callback of intel-lpss driver does nothing but wakes up its
children. I don't know if there is any reason to do so, but to me, this is
not preferred because it should be the child device driver to do so when
necessary, not the parent device driver.
Plus, .prepare() does not support a
On Wed 24-01-18 14:08:05, Andrew Morton wrote:
[...]
> Can we please try to narrow the scope of this issue by concentrating on
> the userspace interfaces? David believes that the mount option and
> memory.oom_group will disappear again in the near future, others
> disagree.
Mount option is the cg
Since struct timespec is not y2038 safe on 32 bit machines, thus replace
uses of struct timespec with struct timespec64 in the kernel.
Signed-off-by: Baolin Wang
---
kernel/debug/kdb/kdb_main.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/debug/kdb/kdb_
Commit df351ef73789 ("nvme-fabrics: fix memory leak when parsing host ID
option") fixed the leak of 'p' but in case uuid_parse() fails the memory
is freed before the error print that is using it.
Free it after printing eventual errors.
Signed-off-by: Johannes Thumshirn
Fixes: df351ef73789 ("nvme
On Wed 24-01-18 13:44:02, David Rientjes wrote:
> On Wed, 24 Jan 2018, Michal Hocko wrote:
>
> > > The current implementation of memory.oom_group is based on top of a
> > > selection implementation that is broken in three ways I have listed for
> > > months:
> >
> > This doesn't lead to anywher
On 2018/1/25 11:44, Jens Axboe wrote:
On 1/24/18 8:38 PM, Jia-Ju Bai wrote:
After checking all possible call chains to kmalloc here,
my tool finds that kmalloc is never called in atomic context.
Thus GFP_ATOMIC is not necessary, and it can be replaced with GFP_KERNEL.
This is found by a stati
Hi Hyunchul,
On 2018/1/25 10:47, Hyunchul Lee wrote:
> Hi Chao,
>
> On 01/25/2018 12:32 AM, Chao Yu wrote:
>> On 2018/1/22 18:49, Hyunchul Lee wrote:
>>> From: Hyunchul Lee
>>>
>>> Add the 'whint_mode' mount option that controls which write
>>> hints are passed down to block layer. There are "of
Hi Frank,
On Thu, Jan 25, 2018 at 7:48 AM, Frank Rowand wrote:
>> create mode 100644 include/trace/events/of.h
>
> mode looks incorrect. Existing files in include/trace/events/ are -rw-rw
Not in my git clone ;-) 644 should be fine.
Gr{oetje,eeting}s,
Geert
--
Gee
701 - 749 of 749 matches
Mail list logo
