[PATCH v2 2/2] KVM: X86: Don't use PV TLB flush with dedicated vCPUs and steal time disabled

From: Wanpeng Li vCPUs are very unlikely to get preempted when they are the only task running on a CPU. PV TLB flush is slower that the native flush in that case. In addition, avoid traversing all the cpus for pv tlb flush when steal time is disabled since pv tlb flush

[PATCH v2 2/2] KVM: X86: Don't use PV TLB flush with dedicated vCPUs and steal time disabled

From: Wanpeng Li vCPUs are very unlikely to get preempted when they are the only task running on a CPU. PV TLB flush is slower that the native flush in that case. In addition, avoid traversing all the cpus for pv tlb flush when steal time is disabled since pv tlb flush depends on the field in

[PATCH v2 1/2] KVM: x86: Add dedicated vCPU hint KVM_HINTS_DEDICATED

From: Wanpeng Li Waiman Long mentioned that: Generally speaking, unfair lock performs well for VMs with a small number of vCPUs. Native qspinlock may perform better than pvqspinlock if there is vCPU pinning and there is no vCPU over-commitment. This patch adds a

[PATCH v2 1/2] KVM: x86: Add dedicated vCPU hint KVM_HINTS_DEDICATED

From: Wanpeng Li Waiman Long mentioned that: Generally speaking, unfair lock performs well for VMs with a small number of vCPUs. Native qspinlock may perform better than pvqspinlock if there is vCPU pinning and there is no vCPU over-commitment. This patch adds a performance hint to allow

Re: [Resend] Possible bug in __fragmentation_index()

On 2 Feb 2018, at 17:47, Mel Gorman wrote: > On Fri, Feb 02, 2018 at 02:16:39PM +, Robert Harris wrote: >> I was planning to annotate the opaque calculation in >> __fragmentation_index() but on closer inspection I think there may be a >> bug. I could use some feedback. A belated thank you

[PATCH v2] ASoC: use DEFINE_SHOW_ATTRIBUTE() to decrease code duplication

There is some duplicate code in soc-core.c, and the kernel provides DEFINE_SHOW_ATTRIBUTE() helper macro to decrease it in seq_file.h. Signed-off-by: Peng Donglin --- v2: [addressed comments from Andy] * modify code change description * do not rename m -> s ---

Re: [Resend] Possible bug in __fragmentation_index()

On 2 Feb 2018, at 17:47, Mel Gorman wrote: > On Fri, Feb 02, 2018 at 02:16:39PM +, Robert Harris wrote: >> I was planning to annotate the opaque calculation in >> __fragmentation_index() but on closer inspection I think there may be a >> bug. I could use some feedback. A belated thank you

[PATCH v2] ASoC: use DEFINE_SHOW_ATTRIBUTE() to decrease code duplication

There is some duplicate code in soc-core.c, and the kernel provides DEFINE_SHOW_ATTRIBUTE() helper macro to decrease it in seq_file.h. Signed-off-by: Peng Donglin --- v2: [addressed comments from Andy] * modify code change description * do not rename m -> s --- sound/soc/soc-core.c | 45

Re: [PATCH] x86/spectre_v2: Remove 0xc2 from spectre_bad_microcodes

On Fri, Feb 09, 2018 at 02:29:27PM +, David Woodhouse wrote: On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote: According to the latest microcode update from Intel (on Feb 8, 2018) on Skylake we should be using the microcode revisions 0xC2***, so we need to remove that from the

Re: [PATCH] x86/spectre_v2: Remove 0xc2 from spectre_bad_microcodes

On Fri, Feb 09, 2018 at 02:29:27PM +, David Woodhouse wrote: On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote: According to the latest microcode update from Intel (on Feb 8, 2018) on Skylake we should be using the microcode revisions 0xC2***, so we need to remove that from the

Re: [PATCH] RDMA/nldev: Fix multiple potential NULL pointer dereferences

On Fri, Feb 09, 2018 at 07:36:49AM -0600, Gustavo A. R. Silva wrote: > Hi Leon, > > Quoting Leon Romanovsky : > > > On Fri, Feb 09, 2018 at 12:37:02AM -0600, Gustavo A. R. Silva wrote: > > > In case the message header and payload cannot be stored, function > > > nlmsg_put returns

Re: [PATCH] RDMA/nldev: Fix multiple potential NULL pointer dereferences

On Fri, Feb 09, 2018 at 07:36:49AM -0600, Gustavo A. R. Silva wrote: > Hi Leon, > > Quoting Leon Romanovsky : > > > On Fri, Feb 09, 2018 at 12:37:02AM -0600, Gustavo A. R. Silva wrote: > > > In case the message header and payload cannot be stored, function > > > nlmsg_put returns null. > > > > > >

Re: [PATCH v2] target-i386: add KVM_HINTS_DEDICATED performance hint

On Fri, Feb 09, 2018 at 06:15:25AM -0800, Wanpeng Li wrote: > From: Wanpeng Li > > Add KVM_HINTS_DEDICATED performance hint, guest checks this feature bit > to determine if they run on dedicated vCPUs, allowing optimizations such > as usage of qspinlocks. > > Cc: Paolo

Re: [PATCH v2] target-i386: add KVM_HINTS_DEDICATED performance hint

On Fri, Feb 09, 2018 at 06:15:25AM -0800, Wanpeng Li wrote: > From: Wanpeng Li > > Add KVM_HINTS_DEDICATED performance hint, guest checks this feature bit > to determine if they run on dedicated vCPUs, allowing optimizations such > as usage of qspinlocks. > > Cc: Paolo Bonzini > Cc: Radim

Re: [PATCH 2/6] genalloc: selftest

On 05/02/18 02:14, Randy Dunlap wrote: > On 02/04/2018 03:03 PM, Matthew Wilcox wrote: >> On Sun, Feb 04, 2018 at 02:19:22PM -0800, Randy Dunlap wrote: +#ifndef __GENALLOC_SELFTEST_H__ +#define __GENALLOC_SELFTEST_H__ >>> >>> Please use _LINUX_GENALLOC_SELFTEST_H_ >> >>

Re: [PATCH 2/6] genalloc: selftest

On 05/02/18 02:14, Randy Dunlap wrote: > On 02/04/2018 03:03 PM, Matthew Wilcox wrote: >> On Sun, Feb 04, 2018 at 02:19:22PM -0800, Randy Dunlap wrote: +#ifndef __GENALLOC_SELFTEST_H__ +#define __GENALLOC_SELFTEST_H__ >>> >>> Please use _LINUX_GENALLOC_SELFTEST_H_ >> >>

Re: [PATCH] x86/spectre_v2: Remove 0xc2 from spectre_bad_microcodes

On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote: > According to the latest microcode update from Intel (on Feb 8, 2018) on > Skylake we should be using the microcode revisions 0xC2***, so we need > to remove that from the blacklist now. The doc also suggests that Gemini Lake 0x22 is also

Re: [PATCH] x86/spectre_v2: Remove 0xc2 from spectre_bad_microcodes

On Fri, 2018-02-09 at 14:10 +, Darren Kenny wrote: > According to the latest microcode update from Intel (on Feb 8, 2018) on > Skylake we should be using the microcode revisions 0xC2***, so we need > to remove that from the blacklist now. The doc also suggests that Gemini Lake 0x22 is also

Re: [PATCH 1/2] Documentation/memory-barriers.txt: cross-reference "tools/memory-model/"

On Fri, Feb 09, 2018 at 01:50:51PM +0100, Andrea Parri wrote: > On Fri, Feb 09, 2018 at 04:31:00AM -0800, Paul E. McKenney wrote: > > On Sun, Feb 04, 2018 at 07:37:08PM +0100, Andrea Parri wrote: > > > Hi Akira, > > > > > > On Mon, Feb 05, 2018 at 01:14:10AM +0900, Akira Yokosawa wrote: > > > >

Re: [PATCH 1/2] Documentation/memory-barriers.txt: cross-reference "tools/memory-model/"

On Fri, Feb 09, 2018 at 01:50:51PM +0100, Andrea Parri wrote: > On Fri, Feb 09, 2018 at 04:31:00AM -0800, Paul E. McKenney wrote: > > On Sun, Feb 04, 2018 at 07:37:08PM +0100, Andrea Parri wrote: > > > Hi Akira, > > > > > > On Mon, Feb 05, 2018 at 01:14:10AM +0900, Akira Yokosawa wrote: > > > >

Re: [PATCH 1/6] genalloc: track beginning of allocations

On 05/02/18 05:45, Matthew Wilcox wrote: > On Sun, Feb 04, 2018 at 02:34:08PM -0800, Randy Dunlap wrote: >>> +/** >>> + * cleart_bits_ll - according to the mask, clears the bits specified by >> >> clear_bits_ll > > 'make W=1' should catch this ... yes? > > (hint: building with 'make C=1

Re: [PATCH 1/6] genalloc: track beginning of allocations

On 05/02/18 05:45, Matthew Wilcox wrote: > On Sun, Feb 04, 2018 at 02:34:08PM -0800, Randy Dunlap wrote: >>> +/** >>> + * cleart_bits_ll - according to the mask, clears the bits specified by >> >> clear_bits_ll > > 'make W=1' should catch this ... yes? > > (hint: building with 'make C=1

[GIT PULL] xen: fixes for 4.16 rc1

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.16-rc1-tag xen: fixes for 4.16 rc1 This time only 5 small fixes for issues when running under Xen. Thanks. Juergen arch/x86/xen/p2m.c | 6 ++

[GIT PULL] xen: fixes for 4.16 rc1

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.16-rc1-tag xen: fixes for 4.16 rc1 This time only 5 small fixes for issues when running under Xen. Thanks. Juergen arch/x86/xen/p2m.c | 6 ++

[PATCH RFC tip/lkmm 09/10] EXP Remove underscore from smp_mb__after_atomic() workings

Signed-off-by: Paul E. McKenney --- tools/memory-model/linux-kernel.bell | 2 +- tools/memory-model/linux-kernel.cat | 2 +- tools/memory-model/linux-kernel.def | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH RFC tip/lkmm 02/10] MAINTAINERS: Add the Memory Consistency Model subsystem

From: Andrea Parri Move the contents of tools/memory-model/MAINTAINERS into the main MAINTAINERS file, removing tools/memory-model/MAINTAINERS. This allows get_maintainer.pl to correctly identify the maintainers of tools/memory-model/. Suggested-by: Ingo Molnar

[PATCH RFC tip/lkmm 09/10] EXP Remove underscore from smp_mb__after_atomic() workings

Signed-off-by: Paul E. McKenney --- tools/memory-model/linux-kernel.bell | 2 +- tools/memory-model/linux-kernel.cat | 2 +- tools/memory-model/linux-kernel.def | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/memory-model/linux-kernel.bell

[PATCH RFC tip/lkmm 02/10] MAINTAINERS: Add the Memory Consistency Model subsystem

From: Andrea Parri Move the contents of tools/memory-model/MAINTAINERS into the main MAINTAINERS file, removing tools/memory-model/MAINTAINERS. This allows get_maintainer.pl to correctly identify the maintainers of tools/memory-model/. Suggested-by: Ingo Molnar Signed-off-by: Andrea Parri

[PATCH RFC tip/lkmm 08/10] EXP Remove understore from smp_mb__before_atomic() workings

Signed-off-by: Paul E. McKenney --- tools/memory-model/linux-kernel.bell | 2 +- tools/memory-model/linux-kernel.cat | 2 +- tools/memory-model/linux-kernel.def | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH RFC tip/lkmm 08/10] EXP Remove understore from smp_mb__before_atomic() workings

Signed-off-by: Paul E. McKenney --- tools/memory-model/linux-kernel.bell | 2 +- tools/memory-model/linux-kernel.cat | 2 +- tools/memory-model/linux-kernel.def | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/memory-model/linux-kernel.bell

[PATCH RFC tip/lkmm 10/10] EXP Remove underscores from smp_mb__after_spinlock() workings

Signed-off-by: Paul E. McKenney --- tools/memory-model/linux-kernel.bell | 2 +- tools/memory-model/linux-kernel.cat | 2 +- tools/memory-model/linux-kernel.def | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [Xen-devel] [PATCH] [v2] xen: hypercall: fix out-of-bounds memcpy

On Fri, Feb 9, 2018 at 3:13 PM, David Laight wrote: > From: Arnd Bergmann >> Sent: 09 February 2018 12:58 > ... >> However, aside from this driver, I wonder if we should be worried about >> Spectre type 1 attacks on similar code, when gcc-8 turns a switch/case >>

[PATCH RFC tip/lkmm 10/10] EXP Remove underscores from smp_mb__after_spinlock() workings

Signed-off-by: Paul E. McKenney --- tools/memory-model/linux-kernel.bell | 2 +- tools/memory-model/linux-kernel.cat | 2 +- tools/memory-model/linux-kernel.def | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/memory-model/linux-kernel.bell

Re: [Xen-devel] [PATCH] [v2] xen: hypercall: fix out-of-bounds memcpy

On Fri, Feb 9, 2018 at 3:13 PM, David Laight wrote: > From: Arnd Bergmann >> Sent: 09 February 2018 12:58 > ... >> However, aside from this driver, I wonder if we should be worried about >> Spectre type 1 attacks on similar code, when gcc-8 turns a switch/case >> statement into an array lookup

[PATCH RFC tip/lkmm 01/10] tools/memory-model: Clarify the origin/scope of the tool name

From: Andrea Parri Ingo pointed out that: "The "memory model" name is overly generic, ambiguous and somewhat misleading, as we usually mean the virtual memory layout/model when we say "memory model". GCC too uses it in that sense [...]" Make it clear that

[PATCH RFC tip/lkmm 04/10] EXP litmus_tests: Add comments explaining tests' purposes

This commit adds comments to the litmus tests summarizing what these tests are intended to demonstrate. Suggested-by: Ingo Molnar Signed-off-by: Paul E. McKenney [ paulmck: Apply Andrea's and Alan's feedback. ] ---

[PATCH RFC tip/lkmm 01/10] tools/memory-model: Clarify the origin/scope of the tool name

From: Andrea Parri Ingo pointed out that: "The "memory model" name is overly generic, ambiguous and somewhat misleading, as we usually mean the virtual memory layout/model when we say "memory model". GCC too uses it in that sense [...]" Make it clear that tools/memory-model/ uses the

[PATCH RFC tip/lkmm 04/10] EXP litmus_tests: Add comments explaining tests' purposes

This commit adds comments to the litmus tests summarizing what these tests are intended to demonstrate. Suggested-by: Ingo Molnar Signed-off-by: Paul E. McKenney [ paulmck: Apply Andrea's and Alan's feedback. ] --- .../memory-model/litmus-tests/CoRR+poonceonce+Once.litmus | 7 +++

[PATCH RFC tip/lkmm 05/10] README: Fix a couple of punctuation errors

Signed-off-by: Paul E. McKenney --- tools/memory-model/litmus-tests/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/memory-model/litmus-tests/README b/tools/memory-model/litmus-tests/README index 9a3bb5949191..dca7d823ad57 100644

[PATCH RFC tip/lkmm 05/10] README: Fix a couple of punctuation errors

Signed-off-by: Paul E. McKenney --- tools/memory-model/litmus-tests/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/memory-model/litmus-tests/README b/tools/memory-model/litmus-tests/README index 9a3bb5949191..dca7d823ad57 100644 ---

[PATCH RFC tools/lkmm] Miscellaneous fixes

Hello! This RFC series adds some miscellaneous updates to the Linux kernel memory model: 1. Clarify the origin and scope of the tool name to avoid confusion between "memory model" and "memory management", courtesy of Andrea Parri. 2. Move the maintainer list for LKMM

[PATCH RFC tools/lkmm] Miscellaneous fixes

Hello! This RFC series adds some miscellaneous updates to the Linux kernel memory model: 1. Clarify the origin and scope of the tool name to avoid confusion between "memory model" and "memory management", courtesy of Andrea Parri. 2. Move the maintainer list for LKMM

[PATCHv9 2/4] x86/boot/compressed/64: Introduce paging_prepare()

This patch renames l5_paging_required() into paging_prepare() and changes the interface of the function. This is a preparation for the next patch, which would make the function also allocate memory for the 32-bit trampoline. The function now returns a 128-bit structure. RAX would return

[PATCHv9 2/4] x86/boot/compressed/64: Introduce paging_prepare()

This patch renames l5_paging_required() into paging_prepare() and changes the interface of the function. This is a preparation for the next patch, which would make the function also allocate memory for the 32-bit trampoline. The function now returns a 128-bit structure. RAX would return

[PATCHv9 3/4] x86/boot/compressed/64: Prepare trampoline memory

If a bootloader enables 64-bit mode with 4-level paging, we might need to switch over to 5-level paging. The switching requires the disabling paging. It works fine if kernel itself is loaded below 4G. But if the bootloader put the kernel above 4G (not sure if anybody does this), we would lose

[PATCHv9 3/4] x86/boot/compressed/64: Prepare trampoline memory

If a bootloader enables 64-bit mode with 4-level paging, we might need to switch over to 5-level paging. The switching requires the disabling paging. It works fine if kernel itself is loaded below 4G. But if the bootloader put the kernel above 4G (not sure if anybody does this), we would lose

[PATCH v2] ASoC: rt5645: Introduce mapping for ACPI-defined GPIO

From: Carlo Caione On at least one notebook (ECS EF20EA) the 'hp-detect' GPIO is defined in the DSDT table by the ACPI GpioIo resources in _CRS. Add this mapping to the rt5645 driver to enable the jack detection also on non-DT platforms. Method (_CRS, 0, NotSerialized) {

[PATCH v2] ASoC: rt5645: Introduce mapping for ACPI-defined GPIO

From: Carlo Caione On at least one notebook (ECS EF20EA) the 'hp-detect' GPIO is defined in the DSDT table by the ACPI GpioIo resources in _CRS. Add this mapping to the rt5645 driver to enable the jack detection also on non-DT platforms. Method (_CRS, 0, NotSerialized) { Name (SBUF,

[PATCHv9 4/4] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G

This patch addresses a shortcoming in current boot process on machines that supports 5-level paging. If a bootloader enables 64-bit mode with 4-level paging, we might need to switch over to 5-level paging. The switching requires the disabling paging. It works fine if kernel itself is loaded below

[PATCHv9 1/4] x86/boot/compressed/64: Rename pagetable.c to kaslr_64.c

The name of the file -- pagetable.c -- is misleading: it only contains helpers used for KASLR in 64-bit mode. Let's rename the file to reflect its content. Signed-off-by: Kirill A. Shutemov --- arch/x86/boot/compressed/Makefile| 2 +-

[PATCHv9 1/4] x86/boot/compressed/64: Rename pagetable.c to kaslr_64.c

The name of the file -- pagetable.c -- is misleading: it only contains helpers used for KASLR in 64-bit mode. Let's rename the file to reflect its content. Signed-off-by: Kirill A. Shutemov --- arch/x86/boot/compressed/Makefile| 2 +- arch/x86/boot/compressed/{pagetable.c

[PATCHv9 4/4] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G

This patch addresses a shortcoming in current boot process on machines that supports 5-level paging. If a bootloader enables 64-bit mode with 4-level paging, we might need to switch over to 5-level paging. The switching requires the disabling paging. It works fine if kernel itself is loaded below

[PATCHv9 0/4] x86: 5-level related changes into decompression code

These patcheset is a preparation for boot-time switching between paging modes. Please apply. The first patch is pure cosmetic change: it gives file with KASLR helpers a proper name. The last three patches bring support of booting into 5-level paging mode if a bootloader put the kernel above 4G.

[PATCHv9 0/4] x86: 5-level related changes into decompression code

These patcheset is a preparation for boot-time switching between paging modes. Please apply. The first patch is pure cosmetic change: it gives file with KASLR helpers a proper name. The last three patches bring support of booting into 5-level paging mode if a bootloader put the kernel above 4G.

[PATCH RFC tip/lkmm 06/10] EXP MAINTAINERS: Add the "LKMM" acronym

This commit adds "(LKMM)" to the end of the MAINTAINERS file's entry for the Linux-kernel memory-consistency model. If people are OK with this, it should be squashed into 12a62a1d0703 ("MAINTAINERS: Add the Memory Consistency Model subsystem"). Signed-off-by: Paul E. McKenney

[PATCH RFC tip/lkmm 06/10] EXP MAINTAINERS: Add the "LKMM" acronym

This commit adds "(LKMM)" to the end of the MAINTAINERS file's entry for the Linux-kernel memory-consistency model. If people are OK with this, it should be squashed into 12a62a1d0703 ("MAINTAINERS: Add the Memory Consistency Model subsystem"). Signed-off-by: Paul E. McKenney --- MAINTAINERS |

[PATCH RFC tip/lkmm 03/10] MAINTAINERS: List file memory-barriers.txt within the LKMM entry

From: Andrea Parri We now have a shiny new Linux-kernel memory model (LKMM) and the old tried-and-true Documentation/memory-barrier.txt. It would be good to keep these automatically synchronized, but in the meantime we need at least let people know that they are related.

[PATCH RFC tip/lkmm 07/10] MAINTAINERS: Add Akira Yokosawa as an LKMM reviewer

Signed-off-by: Paul E. McKenney --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 674b35c3f28e..cc4c1ac94593 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8097,6 +8097,7 @@ M:David Howells

[PATCH RFC tip/lkmm 07/10] MAINTAINERS: Add Akira Yokosawa as an LKMM reviewer

Signed-off-by: Paul E. McKenney --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 674b35c3f28e..cc4c1ac94593 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -8097,6 +8097,7 @@ M:David Howells M: Jade Alglave M: Luc Maranget M:

[PATCH RFC tip/lkmm 03/10] MAINTAINERS: List file memory-barriers.txt within the LKMM entry

From: Andrea Parri We now have a shiny new Linux-kernel memory model (LKMM) and the old tried-and-true Documentation/memory-barrier.txt. It would be good to keep these automatically synchronized, but in the meantime we need at least let people know that they are related. Will suggested adding

Re: [PATCH] ASoC: use DEFINE_SHOW_ATTRIBUTE() to decrease code duplication

On Fri, Feb 9, 2018 at 9:21 PM, Andy Shevchenko wrote: > On Fri, Feb 9, 2018 at 8:58 AM, Donglin Peng wrote: >> There is some duplicate code in soc-core.c,and the kernel provides > > 'core.c,and' -> 'core.c, and' > >> +static int

Re: [PATCH] ASoC: use DEFINE_SHOW_ATTRIBUTE() to decrease code duplication

On Fri, Feb 9, 2018 at 9:21 PM, Andy Shevchenko wrote: > On Fri, Feb 9, 2018 at 8:58 AM, Donglin Peng wrote: >> There is some duplicate code in soc-core.c,and the kernel provides > > 'core.c,and' -> 'core.c, and' > >> +static int codec_list_show(struct seq_file *s, void *v) > > No need to rename

Re: [PATCH 1/2] arm64: capabilities: Allow flexibility in scope

On Fri, Feb 09, 2018 at 12:16:01PM +, Suzuki K Poulose wrote: > >>> I'm not sure we need extra comments or documentation; I just want > >>> to check that I've understood the patch correctly. > >> > >> So, would you prefer this split to the original patch ? > > > > I think splitting out this

Re: [PATCH 1/2] arm64: capabilities: Allow flexibility in scope

On Fri, Feb 09, 2018 at 12:16:01PM +, Suzuki K Poulose wrote: > >>> I'm not sure we need extra comments or documentation; I just want > >>> to check that I've understood the patch correctly. > >> > >> So, would you prefer this split to the original patch ? > > > > I think splitting out this

[PATCH 4.9 02/92] powerpc/64: Add macros for annotating the destination of rfid/hrfid

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit 50e51c13b3822d14ff6df4279423e4b7b2269bc3 upstream. The rfid/hrfid ((Hypervisor) Return From Interrupt) instruction is used for switching from the

[PATCH 4.9 02/92] powerpc/64: Add macros for annotating the destination of rfid/hrfid

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit 50e51c13b3822d14ff6df4279423e4b7b2269bc3 upstream. The rfid/hrfid ((Hypervisor) Return From Interrupt) instruction is used for switching from the kernel to userspace,

[PATCH 4.9 03/92] powerpc/64: Convert fast_exception_return to use RFI_TO_USER/KERNEL

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit a08f828cf47e6c605af21d2cdec68f84e799c318 upstream. Similar to the syscall return path, in fast_exception_return we may be returning to user or kernel

[PATCH 4.9 03/92] powerpc/64: Convert fast_exception_return to use RFI_TO_USER/KERNEL

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit a08f828cf47e6c605af21d2cdec68f84e799c318 upstream. Similar to the syscall return path, in fast_exception_return we may be returning to user or kernel context. We already

Re: [patch v1 0/4] mlx-platform: Add support for new Mellanox systems, code improvement, fixes for msn21xx system

On Fri, Feb 9, 2018 at 4:22 AM, Darren Hart wrote: > On Fri, Feb 02, 2018 at 08:45:44AM +, Vadim Pasternak wrote: >> platform/x86: mlx-platform: Use defines for bus assignment >> platform/x86: mlx-platform: Add define for the negative bus >> platform/x86:

[PATCH 4.9 04/92] powerpc/64: Convert the syscall exit path to use RFI_TO_USER/KERNEL

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit b8e90cb7bc04a509e821e82ab6ed7a8ef11ba333 upstream. In the syscall exit path we may be returning to user or kernel context. We already have a test for

Re: [patch v1 0/4] mlx-platform: Add support for new Mellanox systems, code improvement, fixes for msn21xx system

On Fri, Feb 9, 2018 at 4:22 AM, Darren Hart wrote: > On Fri, Feb 02, 2018 at 08:45:44AM +, Vadim Pasternak wrote: >> platform/x86: mlx-platform: Use defines for bus assignment >> platform/x86: mlx-platform: Add define for the negative bus >> platform/x86: mlx-platform: Fix power cable

[PATCH 4.9 04/92] powerpc/64: Convert the syscall exit path to use RFI_TO_USER/KERNEL

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit b8e90cb7bc04a509e821e82ab6ed7a8ef11ba333 upstream. In the syscall exit path we may be returning to user or kernel context. We already have a test for that, because we

[PATCH 4.9 07/92] powerpc/64s: Support disabling RFI flush with no_rfi_flush and nopti

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit bc9c9304a45480797e13a8e1df96ffcf44fb62fe upstream. Because there may be some performance overhead of the RFI flush, add kernel command line options

[PATCH 4.9 07/92] powerpc/64s: Support disabling RFI flush with no_rfi_flush and nopti

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit bc9c9304a45480797e13a8e1df96ffcf44fb62fe upstream. Because there may be some performance overhead of the RFI flush, add kernel command line options to disable it. We

[PATCH v2] target-i386: add KVM_HINTS_DEDICATED performance hint

From: Wanpeng Li Add KVM_HINTS_DEDICATED performance hint, guest checks this feature bit to determine if they run on dedicated vCPUs, allowing optimizations such as usage of qspinlocks. Cc: Paolo Bonzini Cc: Radim Krčmář Cc:

[PATCH v2] target-i386: add KVM_HINTS_DEDICATED performance hint

From: Wanpeng Li Add KVM_HINTS_DEDICATED performance hint, guest checks this feature bit to determine if they run on dedicated vCPUs, allowing optimizations such as usage of qspinlocks. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Eduardo Habkost Signed-off-by: Wanpeng Li --- v1 -> v2: * add

[PATCH 4.9 20/92] net: igmp: add a missing rcu locking section

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit e7aadb27a5415e8125834b84a74477bfbee4eff5 ] Newly added igmpv3_get_srcaddr() needs to be called under rcu lock. Timer callbacks do not

[PATCH 4.9 20/92] net: igmp: add a missing rcu locking section

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit e7aadb27a5415e8125834b84a74477bfbee4eff5 ] Newly added igmpv3_get_srcaddr() needs to be called under rcu lock. Timer callbacks do not ensure this locking.

[PATCH 4.9 00/92] 4.9.81-stable review

This is the start of the stable review cycle for the 4.9.81 release. There are 92 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Feb 11 13:39:04 UTC 2018. Anything

[PATCH 4.9 00/92] 4.9.81-stable review

This is the start of the stable review cycle for the 4.9.81 release. There are 92 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Feb 11 13:39:04 UTC 2018. Anything

[PATCH 4.9 19/92] ip6mr: fix stale iterator

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov [ Upstream commit 4adfa79fc254efb7b0eb3cd58f62c2c3f805f1ba ] When we dump the ip6mr mfc entries via proc, we initialize an iterator with the

[PATCH 4.9 19/92] ip6mr: fix stale iterator

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov [ Upstream commit 4adfa79fc254efb7b0eb3cd58f62c2c3f805f1ba ] When we dump the ip6mr mfc entries via proc, we initialize an iterator with the table to dump but we don't

[PATCH 4.9 21/92] qlcnic: fix deadlock bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Junxiao Bi [ Upstream commit 233ac3891607f501f08879134d623b303838f478 ] The following soft lockup was caught. This is a deadlock caused by recusive locking. Process

[PATCH 4.9 21/92] qlcnic: fix deadlock bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Junxiao Bi [ Upstream commit 233ac3891607f501f08879134d623b303838f478 ] The following soft lockup was caught. This is a deadlock caused by recusive locking. Process kworker/u40:1:28016 was

[PATCH 4.9 25/92] vhost_net: stop device during reset owner

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 4cd879515d686849eec5f718aeac62a70b067d82 ] We don't stop device before reset owner, this means we could try to serve any virtqueue kick

[PATCH 4.9 25/92] vhost_net: stop device during reset owner

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit 4cd879515d686849eec5f718aeac62a70b067d82 ] We don't stop device before reset owner, this means we could try to serve any virtqueue kick before reset dev->worker.

[PATCH 4.9 27/92] cls_u32: add missing RCU annotation.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit 058a6c033488494a6b1477b05fe8e1a16e344462 ] In a couple of points of the control path, n->ht_down is currently accessed without the required

[PATCH 4.9 27/92] cls_u32: add missing RCU annotation.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit 058a6c033488494a6b1477b05fe8e1a16e344462 ] In a couple of points of the control path, n->ht_down is currently accessed without the required RCU annotation. The

[PATCH 4.9 33/92] b43: Add missing MODULE_FIRMWARE()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 3c89a72ad80c64bdbd5ff851ee9c328a191f7e01 upstream. Some firmware entries were forgotten to be added via MODULE_FIRMWARE(), which may result in the

[PATCH 4.9 26/92] tcp_bbr: fix pacing_gain to always be unity when using lt_bw

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Neal Cardwell [ Upstream commit 3aff3b4b986e51bcf4ab249e5d48d39596e0df6a ] This commit fixes the pacing_gain to remain at BBR_UNIT (1.0) when using lt_bw and returning

[PATCH 4.9 33/92] b43: Add missing MODULE_FIRMWARE()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 3c89a72ad80c64bdbd5ff851ee9c328a191f7e01 upstream. Some firmware entries were forgotten to be added via MODULE_FIRMWARE(), which may result in the non-functional state when

[PATCH 4.9 26/92] tcp_bbr: fix pacing_gain to always be unity when using lt_bw

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Neal Cardwell [ Upstream commit 3aff3b4b986e51bcf4ab249e5d48d39596e0df6a ] This commit fixes the pacing_gain to remain at BBR_UNIT (1.0) when using lt_bw and returning from the PROBE_RTT

[PATCH 4.9 32/92] media: soc_camera: soc_scale_crop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Chan commit 5331aec1bf9c9da557668174e0a4bfcee39f1121 upstream. This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing

[PATCH 4.9 32/92] media: soc_camera: soc_scale_crop: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Chan commit 5331aec1bf9c9da557668174e0a4bfcee39f1121 upstream. This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing

RE: [Xen-devel] [PATCH] [v2] xen: hypercall: fix out-of-bounds memcpy

From: Arnd Bergmann > Sent: 09 February 2018 12:58 ... > However, aside from this driver, I wonder if we should be worried about > Spectre type 1 attacks on similar code, when gcc-8 turns a switch/case > statement into an array lookup behind our back, e.g. in an ioctl handler. > Has anybody got

RE: [Xen-devel] [PATCH] [v2] xen: hypercall: fix out-of-bounds memcpy

From: Arnd Bergmann > Sent: 09 February 2018 12:58 ... > However, aside from this driver, I wonder if we should be worried about > Spectre type 1 attacks on similar code, when gcc-8 turns a switch/case > statement into an array lookup behind our back, e.g. in an ioctl handler. > Has anybody got

[PATCH 4.9 35/92] x86/retpoline: Remove the esp/rsp thunk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Waiman Long (cherry picked from commit 1df37383a8aeabb9b418698f0bcdffea01f4b1b2) It doesn't make sense to have an indirect call thunk with esp/rsp as retpoline code won't

[PATCH 4.9 35/92] x86/retpoline: Remove the esp/rsp thunk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Waiman Long (cherry picked from commit 1df37383a8aeabb9b418698f0bcdffea01f4b1b2) It doesn't make sense to have an indirect call thunk with esp/rsp as retpoline code won't work correctly with

[PATCH 4.9 36/92] KVM: x86: Make indirect calls in emulator speculation safe

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra (cherry picked from commit 1a29b5b7f347a1a9230c1e0af5b37e3e571588ab) Replace the indirect calls with CALL_NOSPEC. Signed-off-by: Peter Zijlstra (Intel)

[PATCH 4.9 36/92] KVM: x86: Make indirect calls in emulator speculation safe

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra (cherry picked from commit 1a29b5b7f347a1a9230c1e0af5b37e3e571588ab) Replace the indirect calls with CALL_NOSPEC. Signed-off-by: Peter Zijlstra (Intel) Signed-off-by: Thomas

<    4   5   6   7   8   9   10   11   12   13   >