[PATCH] m32r: fix build warning

Some m32r builds were having a warning: arch/m32r/include/asm/cmpxchg.h:191:3: warning: value computed is not used arch/m32r/include/asm/cmpxchg.h:68:3: warning: value computed is not used Taking the idea from e001bbae7147 ("ARM: cmpxchg: avoid warnings from macro-ized

[PATCH 15/22] openrisc: Add optimized memset

From: Olof Kindgren This adds a hand-optimized assembler version of memset and sets __HAVE_ARCH_MEMSET to use this version instead of the generic C routine Signed-off-by: Olof Kindgren Signed-off-by: Stafford Horne ---

[PATCH 11/22] openrisc: add futex_atomic_* implementations

From: Stefan Kristiansson Support for the futex_atomic_* operations by using the load-link/store-conditional l.lwa/l.swa instructions. Most openrisc cores provide these instructions now if not available, emulation is provided. Signed-off-by: Stefan

[PATCH 10/22] openrisc: add spinlock implementation

From: Stefan Kristiansson Heavily based on the ARM implementation, this adds ticket spinlock support for OpenRISC. Signed-off-by: Stefan Kristiansson [sho...@gmail.com: fix tabs vs space checkpatch warning] Signed-off-by:

[PATCH 03/22] openrisc: tlb miss handler optimizations

From: Stefan Kristiansson By slightly reorganizing the code, the number of registers used in the tlb miss handlers can be reduced by two, thus removing the need to save them to memory. Also, some dead and commented out code is removed. No functional change.

[PATCH 19/22] scripts/checkstack.pl: Add openrisc support

Openrisc stack pointer is managed by decrementing r1. Add regexes to recognize this. Signed-off-by: Stafford Horne --- scripts/checkstack.pl | 3 +++ 1 file changed, 3 insertions(+) diff --git a/scripts/checkstack.pl b/scripts/checkstack.pl index dd83978..eea5b78 100755 ---

[PATCH 12/22] openrisc: remove unnecessary stddef.h include

From: Stefan Kristiansson This causes the build to fail when building with the or1k-musl-linux- toolchain and it is not needed. Signed-off-by: Stafford Horne --- arch/openrisc/kernel/ptrace.c | 1 - 1 file changed, 1 deletion(-) diff --git

[GIT PULL] Block fixes for 4.10-rc

Hi Linus, Here's a set of fixes for the current series. This pull request contains: - The virtio_blk stack DMA corruption fix from Christoph, fixing and issue with VMAP stacks. - O_DIRECT blkbits calculation fix from Chandan. - Discard regression fix from Christoph. - Queue init error

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3900' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f0ad17712b9f71c24e2b8b9725230ef57232377f commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

cc1: error: '-march=r3900' requires '-mfp32'

Hi James, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f0ad17712b9f71c24e2b8b9725230ef57232377f commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 3 months ago config:

RE: [char-misc for 4.10-rc4 V2] mei: bus: enable OS version only for SPT and newer

> Subject: Re: [char-misc for 4.10-rc4 V2] mei: bus: enable OS version only for > SPT > and newer > > On Sat, Jan 14, 2017 at 08:27:31PM +0100, Paul Menzel wrote: > > Dear Greg, > > > > > > On 2017-01-13 14:00, Greg Kroah-Hartman wrote: > > > On Wed, Jan 11, 2017 at 03:26:06PM +0100, Paul Menzel

Re: [PATCH] lib: bitmap: introduce bitmap_find_next_zero_area_and_size

Hi Jaewon, with all comments above, some of my concerns. On Mon, Dec 26, 2016 at 01:18:11PM +0900, Jaewon Kim wrote: > There was no bitmap API which returns both next zero index and size of zeros > from that index. Yes, there is. Most probably because this function is not needed. Typical

[PATCH] Drivers: staging: rtl8192e: style fix, octal file permissions

Changed file permissions to octal. Found with checkpatch. Signed-off-by: Derek Robson --- drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/rtl8192e/rtl8192e/rtl_core.c

Re: [PATCH 5/6] treewide: use kv[mz]alloc* rather than opencoded variants

On Sat 14-01-17 12:01:50, Tetsuo Handa wrote: > On 2017/01/13 2:29, Michal Hocko wrote: > > Ilya has noticed that I've screwed up some k[zc]alloc conversions and > > didn't use the kvzalloc. This is an updated patch with some acks > > collected on the way > > --- > > From

[PATCH tip/core/rcu 10/20] rcu: Add functions to test for trivial grace periods

Under some circumstances, RCU grace periods are zero cost. For RCU-preempt, this is the case during boot, and for RCU-bh and RCU-sched, this is the case if there is only one CPU. This means that RCU users might wish to dispense with grace-period-avoidance strategies when grace periods are zero

[PATCH tip/core/rcu 13/20] rcu: Don't wake rcuc/X kthreads on NOCB CPUs

Chris Friesen notice that rcuc/X kthreads were consuming CPU even on NOCB CPUs. This makes no sense because the only purpose or these kthreads is to invoke normal (non-offloaded) callbacks, of which there will never be any on NOCB CPUs. This problem was due to a bug in

[PATCH tip/core/rcu 06/20] rcu: Remove unused but set variable

From: Tobias Klauser Since commit 7ec99de36f40 ("rcu: Provide exact CPU-online tracking for RCU"), the variable mask in rcu_init_percpu_data is set but no longer used. Remove it to fix the following warning when building with 'W=1': kernel/rcu/tree.c: In function

[PATCH tip/core/rcu 07/20] rcu: Remove short-term CPU kicking

Commit 4914950aaa12d ("rcu: Stop treating in-kernel CPU-bound workloads as errors") added a (relatively) short-timeout call to resched_cpu(). This was inspired by as issue that was fixed by b7e7ade34e61 ("sched/core: Fix remote wakeups"). But given that this issue was fixed, it is time for the

[PATCH tip/core/rcu 18/20] llist: Clarify comments about when locking is needed

From: Joel Fernandes llist.h comments are confusing about when locking is needed versus when it isn't. Clarify these comments by being more descriptive about why locking is needed for llist_del_first. Cc: Ingo Molnar Cc: Will Deacon

[PATCH tip/core/rcu 20/20] rcu: Add lockdep checks to synchronous expedited primitives

The non-expedited synchronize_*rcu() primitives have lockdep checks, but their expedited counterparts lack these checks. This commit therefore adds these checks to the expedited synchronize_*rcu() primitives. Signed-off-by: Paul E. McKenney --- kernel/rcu/tree_exp.h

[PATCH tip/core/rcu 09/20] rcu: Once again use NMI-based stack traces in stall warnings

This commit is for all intents and purposes a revert of bc1dce514e9b ("rcu: Don't use NMIs to dump other CPUs' stacks"). The reason to suppose that this can now safely be reverted is the presence of 42a0bb3f7138 ("printk/nmi: generic solution for safe printk in NMI"), which is said to have made

[PATCH tip/core/rcu 17/20] rcu: Fix comment in rcu_organize_nocb_kthreads()

It used to be that the rcuo callback-offload kthreads were spawned in rcu_organize_nocb_kthreads(), and the comment before the "for" loop says as much. However, this spawning has long since moved to the CPU-hotplug code, so this commit fixes this comment. Reported-by: Michalis Kokologiannakis

[PATCH tip/core/rcu 2/3] srcu: Force full grace-period ordering

If a process invokes synchronize_srcu(), is delayed just the right amount of time, and thus does not sleep when waiting for the grace period to complete, there is no ordering between the end of the grace period and the code following the synchronize_srcu(). Similarly, there can be a lack of

[PATCH tip/core/rcu 0/3] SRCU updates for 4.11

Hello! This series provides updates to SRCU: 1. This is a rewrite of the algorithm simplifying reader-count tracking. Algorithm courtesy of Mathieu Desnoyers, implementation courtesy of Lance Roy. 2. Force full grace-period ordering in SRCU. 3. Add CBMC-based

[PATCH tip/core/rcu 3/9] torture: Add tests without slow grace period setup/cleanup

This commit moves CONFIG_RCU_TORTURE_TEST_SLOW_CLEANUP, CONFIG_RCU_TORTURE_TEST_SLOW_INIT, and CONFIG_RCU_TORTURE_TEST_SLOW_PREINIT from CFcommon to all of the TREE scenarios other than TREE08 and TREE09 in order to do at least some testing without these Kconfig options set. Signed-off-by: Paul

[PATCH tip/core/rcu 0/9] Torture-test changes for 4.11

Hello! This series provides torture-test updates: 1. Add a check for CONFIG_RCU_STALL_COMMON for TINY01, in order to complain if this case is not tested. 2. Add CONFIG_PROVE_RCU_REPEATEDLY=y for TINY02, in order to test this case. 3. Add tests without slow grace

[PATCH tip/core/rcu 8/9] locktorture: Fix potential memory leak with rw lock test

From: Yang Shi When running locktorture module with the below commands with kmemleak enabled: $ modprobe locktorture torture_type=rw_lock_irq $ rmmod locktorture The below kmemleak got caught: root@10:~# echo scan > /sys/kernel/debug/kmemleak [ 323.197029] kmemleak: 2

Re: [PATCH] mm: Ignore __GFP_NOWARN when reporting stalls

On Fri 13-01-17 20:00:11, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Wed 11-01-17 19:55:20, Tetsuo Handa wrote: > > > Currently, warn_alloc() prints warning messages only if __GFP_NOWARN > > > is not specified. When warn_alloc() was proposed, I asserted that > > > warn_alloc() should print

[PATCH tip/core/rcu 9/9] torture: Enable DEBUG_OBJECTS_RCU_HEAD for Tiny RCU

The RCU torture tests currently do not run any Tiny RCU scenarios for CONFIG_DEBUG_OBJECTS_RCU_HEAD=y. This is a hole in the test, given that someone might need this in real life and given that Tiny RCU uses different callback-handling code than does Tree RCU. This commit therefore enables this

Re: [PATCH tip/core/rcu 1/3] srcu: More efficient reader counts.

Noticed a few minor nits: * Paul E. McKenney wrote: > From: Lance Roy > > SRCU uses two per-cpu counters: a nesting counter to count the number of > active critical sections, and a sequence counter to ensure that the nesting > counters don't

[tip:sched/core] sched/cputime, powerpc32: Fix stale scaled stime on context switch

Commit-ID: 90d08ba2b9b4be4aeca6a5b5a4b09fbcde30194d Gitweb: http://git.kernel.org/tip/90d08ba2b9b4be4aeca6a5b5a4b09fbcde30194d Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:41 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

[tip:sched/core] sched/cputime, ia64: Fix incorrect start cputime assignment on task switch

Commit-ID: 8388d21468e7e7656867b67ab2ec98a78c9ad799 Gitweb: http://git.kernel.org/tip/8388d21468e7e7656867b67ab2ec98a78c9ad799 Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:42 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

Re: [PATCH 5/6] treewide: use kv[mz]alloc* rather than opencoded variants

On Thu, Jan 12, 2017 at 04:37:16PM +0100, Michal Hocko wrote: > From: Michal Hocko > > There are many code paths opencoding kvmalloc. Let's use the helper > instead. The main difference to kvmalloc is that those users are usually > not considering all the aspects of the memory

[tip:sched/core] sched/cputime: Allow accounting system time using cpustat index

Commit-ID: c31cc6a5187e8b09ccee34f81728a90f80e872e7 Gitweb: http://git.kernel.org/tip/c31cc6a5187e8b09ccee34f81728a90f80e872e7 Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:43 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

Re: [PATCH] clk: rockchip: rk3288: make aclk_vio1_niu a critical clock

Hi Jacob, Am Mittwoch, 11. Januar 2017, 09:26:32 CET schrieb Jacob Chen: > According to the pd blocks, VIO1_NIU is required by RGA,ISP and VOP1. > Then at least one VIO_NIU should be turned on to supply eDP, HDMI, MIPI. > > If eDP,HDMI,MIPI is inited early than VOP or RGA is inited early than

[PATCH RFC v2 tip/core/rcu 0/2] Make RCU synchronous grace periods work throughout boot

Hello! This series fixes a regression in v4.9 where code relied on RCU synchronous grace periods working between the time that the scheduler spawned the first task and RCU finished spawning all of its tasks. This series makes RCU able to handle synchronous grace periods throughout boot. Please

[PATCH] fix race caused by hyperthreads when online an offline cpu

After online an offline cpu, cpu_hw_events.excl_thread_id will always be set to 1 in intel_pmu_cpu_starting() even when its sibling's excl_thread_id is also 1. Then the two siblings will use the same state in their shared cpu_hw_events.excl_cntrs, it will cause race problem. The race senario is

[PATCH tip/core/rcu 0/20] Miscellaneous fixes for 4.11

Hello! This series provides miscellaneous fixes: 1. Make RCU_EXPEDITE_BOOT be the default in order to speed up boot, courtesy of Sebastian Andrzej Siewior. 2. Make RCU suspicious-access lockdep splats use pr_err(). 3. Disable sys_membarrier when nohz_full is enabled,

[PATCH tip/core/rcu 11/20] sched,rcu: Make cond_resched() provide RCU quiescent state

There is some confusion as to which of cond_resched() or cond_resched_rcu_qs() should be added to long in-kernel loops. This commit therefore eliminates the decision by adding RCU quiescent states to cond_resched(). Warning: This is a prototype. For example, it does not correctly handle Tasks

[PATCH tip/core/rcu 08/20] rcu: Add long-term CPU kicking

Commit d2db185bfee8 ("rcu: Remove short-term CPU kicking") removed frequent calls to resched_cpu(), which means that the only time resched_cpu() is invoked is after an RCU CPU stall warning. Although this is good from an avoid-IPIs perspective, we should try to break things loose -before-

[PATCH tip/core/rcu 04/20] rcu: Only dump stalled-tasks stacks if there was a real stall

From: Byungchul Park The print_other_cpu_stall() function currently unconditionally invokes rcu_print_detail_task_stall(). This is OK because if there was a stall sufficient to cause print_other_cpu_stall() to be invoked, that stall is very likely to persist through the

[PATCH tip/core/rcu 02/20] lockdep: Make RCU suspicious-access splats use pr_err

This commit switches RCU suspicious-access splats use pr_err() instead of the current INFO printk()s. This change makes it easier to automatically classify splats. Reported-by: Dmitry Vyukov Signed-off-by: Paul E. McKenney ---

[PATCH tip/core/rcu 19/20] rcu: Eliminate unused expedited_normal counter

Expedited grace periods no longer fall back to normal grace periods in response to lock contention, given that expedited grace periods now use the rcu_node tree so as to avoid contention. This commit therfore removes the expedited_normal counter. Signed-off-by: Paul E. McKenney

[PATCH tip/core/rcu 4/9] torture: Run at least one test with CONFIG_DEBUG_OBJECTS_RCU_HEAD

This commit enables the CONFIG_DEBUG_OBJECTS_RCU_HEAD Kconfig option in TREE02 in order to do at least some testing with this enabled. Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/configs/rcu/TREE02 | 1 + 1 file changed, 1 insertion(+)

[PATCH tip/core/rcu 7/9] torture: Update RCU test scenario documentation

Signed-off-by: Paul E. McKenney --- .../selftests/rcutorture/doc/TREE_RCU-kconfig.txt | 33 -- 1 file changed, 31 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/rcutorture/doc/TREE_RCU-kconfig.txt

[PATCH tip/core/rcu 5/9] torture: Run one test with DEBUG_LOCK_ALLOC but not PROVE_LOCKING

This commit sets CONFIG_DEBUG_LOCK_ALLOC but not CONFIG_PROVE_LOCKING for TREE08 in order to have at least one test with this configuration. Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/configs/rcu/TREE08 | 3 +-- 1 file changed, 1

[PATCH tip/core/rcu 6/9] torture: Run a couple scenarios with CONFIG_RCU_EQS_DEBUG

This commit runs TREE04 and TREE08 with CONFIG_RCU_EQS_DEBUG=y, enabling dyntick-counter checking on those two tests. Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/configs/rcu/TREE04 | 1 +

[PATCH tip/core/rcu 2/9] torture: Add CONFIG_PROVE_RCU_REPEATEDLY=y for TINY02

This commit adds CONFIG_PROVE_RCU_REPEATEDLY=y, which has been untested for quite some time. Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/configs/rcu/TINY02 | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH tip/core/rcu 1/9] torture: Add a check for CONFIG_RCU_STALL_COMMON for TINY01

This commit verifies coverage of testing with CONFIG_RCU_STALL_COMMON=n. Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/configs/rcu/TINY01 | 1 + 1 file changed, 1 insertion(+) diff --git

[tip:sched/core] sched/cputime, powerpc: Prepare accounting structure for cputime flush on tick

Commit-ID: 8c8b73c4811f2b5e458a7418dca07d2ef85c7db1 Gitweb: http://git.kernel.org/tip/8c8b73c4811f2b5e458a7418dca07d2ef85c7db1 Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:45 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

[tip:sched/core] sched/cputime, powerpc: Migrate stolen_time field to the accounting structure

Commit-ID: f828c3d0aebab130a19d36336b50afa3414fa0bc Gitweb: http://git.kernel.org/tip/f828c3d0aebab130a19d36336b50afa3414fa0bc Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:46 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

Re: [PATCH] gcc-plugins: Add structleak for more stack initialization

On 13 Jan 2017 at 14:02, Kees Cook wrote: > This plugin detects any structures that contain __user attributes and > makes sure it is being fulling initialized so that a specific class of > information exposure is eliminated. (For example, the exposure of siginfo > in CVE-2013-2141 would have been

[tip:sched/core] sched/cputime: Export account_guest_time()

Commit-ID: 1213699ab426608ff1925ab263dd6925102bb92a Gitweb: http://git.kernel.org/tip/1213699ab426608ff1925ab263dd6925102bb92a Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:44 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

[tip:locking/core] locking/spinlocks/x86, paravirt: Remove paravirt_ticketlocks_enabled

Commit-ID: aef591cd3d1ddccb268f64c836d38382007373c1 Gitweb: http://git.kernel.org/tip/aef591cd3d1ddccb268f64c836d38382007373c1 Author: Waiman Long AuthorDate: Thu, 12 Jan 2017 15:27:58 -0500 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017

Re: [PATCH] mm: Ignore __GFP_NOWARN when reporting stalls

Michal Hocko wrote: > On Fri 13-01-17 20:00:11, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > So rather than repeating why you think that warn_alloc is worse than a > > > different solution which you are trying to push through you should in > > > fact explain why we should handle stall and

Re: [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods

On Sat, Jan 14, 2017 at 12:00:22AM -0800, Paul E. McKenney wrote: > It now looks like this: > > > > Note that the code was buggy even before this commit, as it was subject > to failure on real-time systems that forced all

Re: 4.10-rc1: thinkpad x60: who ate my cpu?

Hi! On Thu 2017-01-12 20:19:31, Woody Suwalski wrote: > Pavel Machek wrote: > >Hi! > > > >>I used to have two cpus, and Thinkpad X60 should have two cores, but I > >>only see one on 4.10-rc1. This machine went through many > >>suspend/resume cycles. When backups finish, I'll try -rc2. > >Whoever

Re: [PATCH v18 00/15] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

Hi Mark, On 14 January 2017 at 03:29, Mark Rutland wrote: > Hi, > > On Fri, Dec 09, 2016 at 01:33:04AM +0800, fu@linaro.org wrote: >> From: Fu Wei >> >> This patchset: >> (1)Preparation for adding GTDT support in arm_arch_timer: >> 1.

Re: [PATCH] Input: synaptics-rmi4 - make F03 a tristate symbol

On Jan 13, 2017 10:42 PM, "Dmitry Torokhov" wrote: > On Fri, Jan 13, 2017 at 10:34:32PM +0100, Arnd Bergmann wrote: > > config RMI4_F03_SERIO > >tristate > >depends on RMI4_CORE > >depends on RMI4_F03 > >default RMI4_CORE > >

Re: [PATCH v2 2/2] iio: distance: srf08: add IIO driver for us ranger

On 10/01/17 18:48, Andreas Klinger wrote: > This is the IIO driver for devantech srf08 ultrasonic ranger which can be > used to measure the distances to an object. > > The sensor supports I2C with some registers. > > Supported Features include: > - read the distance in ranging mode in

[PATCH tip/core/rcu 05/20] rcu: Remove unneeded rcu_process_callbacks() declarations

The declarations of __rcu_process_callbacks() and rcu_process_callbacks() are not needed, as the definition of both of these functions appear before any uses. This commit therefore removes both declarations. Reported-by: "Ahmed, Iftekhar" Signed-off-by: Paul E. McKenney

[PATCH tip/core/rcu 01/20] rcu: update: Make RCU_EXPEDITE_BOOT be the default

From: Sebastian Andrzej Siewior RCU_EXPEDITE_BOOT should speed up the boot process by enforcing synchronize_rcu_expedited() instead of synchronize_rcu() during the boot process. There should be no reason why one does not want this and there is no need worry about real time

[PATCH tip/core/rcu 12/20] rcu: Re-enable TASKS_RCU for User Mode Linux

Now that User Mode Linux supports arch_irqs_disabled_flags(), this commit re-enables TASKS_RCU for User Mode Linux. Reported-by: Richard Weinberger Signed-off-by: Paul E. McKenney --- init/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH tip/core/rcu 03/20] Fix: Disable sys_membarrier when nohz_full is enabled

From: Mathieu Desnoyers Userspace applications should be allowed to expect the membarrier system call with MEMBARRIER_CMD_SHARED command to issue memory barriers on nohz_full CPUs, but synchronize_sched() does not take those into account. Given that we do not

[PATCH tip/core/rcu 15/20] rcu: Make rcu_cpu_starting() use its "cpu" argument

The rcu_cpu_starting() function uses this_cpu_ptr() to locate the incoming CPU's rcu_data structure. This works for the boot CPU and for all CPUs onlined after rcu_init() executes (during very early boot). Currently, this is the full set of CPUs, so all is well. But if anyone ever parallelizes

[PATCH tip/core/rcu 14/20] rcu: Add comment headers to expedited-grace-period counter functions

These functions (rcu_exp_gp_seq_start(), rcu_exp_gp_seq_end(), rcu_exp_gp_seq_snap(), and rcu_exp_gp_seq_done() seemed too obvious to comment when written, but not so much when being documented. This commit therefore adds header comments to each of them. Signed-off-by: Paul E. McKenney

[PATCH tip/core/rcu 16/20] rcu: Enable RCU tracepoints by default to aid in debugging

From: Matt Fleming While debugging a performance issue I needed to understand why RCU sofitrqs were firing so frequently. Unfortunately, the RCU callback tracepoints are hidden behind CONFIG_RCU_TRACE which defaults to off in the upstream kernel and is likely to also

[PATCH tip/core/rcu 3/3] rcutorture: Add CBMC-based formal verification for SRCU

From: Lance Roy This commit creates a formal/srcu-cbmc directory containing scripts that pull SRCU in from the source code, filter it to remove things that CBMC cannot handle, and run a series of verifications on it. This has a number of shortcomings: 1. It does not yet

[PATCH tip/core/rcu 1/3] srcu: More efficient reader counts.

From: Lance Roy SRCU uses two per-cpu counters: a nesting counter to count the number of active critical sections, and a sequence counter to ensure that the nesting counters don't change while they are being added together in srcu_readers_active_idx_check(). This patch instead

Re: [PATCH tip/core/rcu 2/3] srcu: Force full grace-period ordering

* Paul E. McKenney wrote: > If a process invokes synchronize_srcu(), is delayed just the right amount > of time, and thus does not sleep when waiting for the grace period to > complete, there is no ordering between the end of the grace period and > the code following

[tip:x86/platform] x86/platform/intel: Remove PMIC GPIO block support

Commit-ID: a665ece8b471de45bc19af05d52a1eaa5bc06dca Gitweb: http://git.kernel.org/tip/a665ece8b471de45bc19af05d52a1eaa5bc06dca Author: Andy Shevchenko AuthorDate: Thu, 12 Jan 2017 13:23:31 +0200 Committer: Ingo Molnar CommitDate:

[tip:x86/platform] x86/platform/UV: Fix 2 socket config problem

Commit-ID: 81a71176740624ef3b1bff50c51e7b4aa187353d Gitweb: http://git.kernel.org/tip/81a71176740624ef3b1bff50c51e7b4aa187353d Author: Mike Travis AuthorDate: Fri, 13 Jan 2017 09:21:12 -0600 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 09:26:35

[tip:x86/platform] x86/platform/intel-mid: Enable RTC on Intel Merrifield

Commit-ID: de1c2540aa4f7796f31acf5432597bb0eb086250 Gitweb: http://git.kernel.org/tip/de1c2540aa4f7796f31acf5432597bb0eb086250 Author: Andy Shevchenko AuthorDate: Fri, 13 Jan 2017 18:43:55 +0200 Committer: Ingo Molnar CommitDate:

[tip:perf/core] kprobes, extable: Identify kprobes trampolines as kernel text area

Commit-ID: 5b485629ba0d5d027880769ff467c587b24b4bde Gitweb: http://git.kernel.org/tip/5b485629ba0d5d027880769ff467c587b24b4bde Author: Masami Hiramatsu AuthorDate: Sun, 8 Jan 2017 23:58:09 +0900 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017

[tip:x86/urgent] x86/tsc: Add the Intel Denverton Processor to native_calibrate_tsc()

Commit-ID: 695085b4bc7603551db0b3da897b8bf9893ca218 Gitweb: http://git.kernel.org/tip/695085b4bc7603551db0b3da897b8bf9893ca218 Author: Len Brown AuthorDate: Fri, 13 Jan 2017 01:11:18 -0500 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017

[tip:x86/platform] x86/platform/UV: Fix panic with missing UVsystab support

Commit-ID: eee5715efd8c268724b14c956de6af5d4931f470 Gitweb: http://git.kernel.org/tip/eee5715efd8c268724b14c956de6af5d4931f470 Author: Mike Travis AuthorDate: Fri, 13 Jan 2017 09:21:11 -0600 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 09:26:35

[tip:sched/core] sched/cputime, s390: Implement delayed accounting of system time

Commit-ID: b7394a5f4ce9542666cc68422c3594ea854adc2c Gitweb: http://git.kernel.org/tip/b7394a5f4ce9542666cc68422c3594ea854adc2c Author: Martin Schwidefsky AuthorDate: Thu, 5 Jan 2017 18:11:49 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

[tip:sched/core] sched/cputime: Rename vtime_account_user() to vtime_flush()

Commit-ID: c8d7dabf8f91fadd265e6eb87afb201d14ea299b Gitweb: http://git.kernel.org/tip/c8d7dabf8f91fadd265e6eb87afb201d14ea299b Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:50 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

[tip:sched/core] sched/cputime, powerpc/vtime: Accumulate cputime and account only on tick/task switch

Commit-ID: a19ff1a2cc9227f82e97836a8ee3e593f622eaf9 Gitweb: http://git.kernel.org/tip/a19ff1a2cc9227f82e97836a8ee3e593f622eaf9 Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:47 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

[tip:sched/core] sched/cputime, ia64: Accumulate cputime and account only on tick/task switch

Commit-ID: 7dd582305d19fd178bb42ecd1666285ecfb1657a Gitweb: http://git.kernel.org/tip/7dd582305d19fd178bb42ecd1666285ecfb1657a Author: Frederic Weisbecker AuthorDate: Thu, 5 Jan 2017 18:11:48 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

Re: [PATCH v2 5/6] arm: dts: mt2701: Add ethernet device node.

Hi Erin, small comment inline On 13/01/2017 09:42, Erin Lo wrote: > From: Sean Wang > > Add ethernet device node for MT2701. > > Signed-off-by: Sean Wang > Signed-off-by: Erin Lo > --- > arch/arm/boot/dts/mt2701-evb.dts

Re: [PATCH v7 7/7] perf/amd/iommu: Enable support for multiple IOMMUs

On Sat, Jan 14, 2017 at 09:58:29AM +0700, Suravee Suthikulpanit wrote: > I'll update the commit log to mention > /bus/event_source/devices/amd_iommu_X instead. Yes, so /sys/devices/ contains *all* devices on the system and the iommu ones appear there too but since in the commit message you were

Re: [PATCH v7 4/7] perf/amd/iommu: Declare pr_fmt and remove unnecessary pr_debug

On 1/12/17 17:19, Borislav Petkov wrote: Also, looking at that driver more, this needs to die, like now: #define format_groupattr_groups[0] #define cpumask_group attr_groups[1] #define events_groupattr_groups[2] #define null_group attr_groups[3] Like, kill it dead. Define a

[PATCH] virtio_console: fix a crash in config_work_handler

Using control_work instead of config_work as the 3rd argument to container_of results in an invalid portdev pointer. Indeed, the work structure is initialized as below: INIT_WORK(>config_work, _work_handler); It leads to a crash when portdev->vdev is dereferenced later. This bug is triggered

[PATCH] net: korina: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/korina.c | 14 -- 1 files changed, 8 insertions(+), 6 deletions(-) diff --git

[PATCH] net: marvell: skge: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. The callback set_link_ksettings no longer update the value of advertising, as the struct ethtool_link_ksettings is defined as const. Signed-off-by: Philippe Reynes ---

[tip:perf/urgent] perf/core: Fix sys_perf_event_open() vs. hotplug

Commit-ID: 63cae12bce9861cec309798d34701cf3da20bc71 Gitweb: http://git.kernel.org/tip/63cae12bce9861cec309798d34701cf3da20bc71 Author: Peter Zijlstra AuthorDate: Fri, 9 Dec 2016 14:59:00 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017

Re: [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods

On Sat, Jan 14, 2017 at 11:35 AM, Borislav Petkov wrote: > On Sat, Jan 14, 2017 at 12:00:22AM -0800, Paul E. McKenney wrote: >> It now looks like this: >> >> >> >> Note that the code was buggy even before

[tip:perf/urgent] perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race

Commit-ID: 321027c1fe77f892f4ea07846aeae08cefbbb290 Gitweb: http://git.kernel.org/tip/321027c1fe77f892f4ea07846aeae08cefbbb290 Author: Peter Zijlstra AuthorDate: Wed, 11 Jan 2017 21:09:50 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017

[PATCH 4/4] drm: exynos: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski ---

[PATCH 2/4] clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski ---

[PATCH 3/4] pinctrl: samsung: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski ---

Re: [PATCH] cxgb4: Remove redundant memset before memcpy

On 2017-01-14 at 02:17:40 +0100, Shyam Saini wrote: > The region set by the call to memset, immediately overwritten by > the subsequent call to memcpy and thus makes the memset redundant. > > Also remove the memset((, 0, sizeof(info)) on line 398 because > info is

[tip:locking/core] kernel/exit: Compute 'current' directly

Commit-ID: 0039962a1473f07fd5c8355bd8264be1eb87eb3e Gitweb: http://git.kernel.org/tip/0039962a1473f07fd5c8355bd8264be1eb87eb3e Author: Davidlohr Bueso AuthorDate: Tue, 3 Jan 2017 13:43:11 -0800 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017

[tip:sched/core] sched/core: Reset RQCF_ACT_SKIP before unpinning rq->lock

Commit-ID: 92509b732baf14c59ca702307270cfaa3a585ae7 Gitweb: http://git.kernel.org/tip/92509b732baf14c59ca702307270cfaa3a585ae7 Author: Matt Fleming AuthorDate: Wed, 21 Sep 2016 14:38:11 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan

Re: [PATCH] x86/platform/UV: Clean up the UV APIC code

On Sat, 2017-01-14 at 09:26 +0100, Ingo Molnar wrote: > * Ingo Molnar wrote: [] > In particular the random line breaks, apparently to pacify checkpatch, were > horribly widespread. I just made the lines longer - that's still more readable > than the multi-line horror that was

Re: [PATCH] iio: magnetometer: ak8974: remove redundant zero timeout check

On 11/01/17 23:11, Linus Walleij wrote: > On Wed, Jan 11, 2017 at 6:49 PM, Colin King wrote: > >> From: Colin Ian King >> >> At the end of the delay loop timeout will always be zero >> and hence the check for !timeout will always be true.

Re: [PATCH 7/9] slab: introduce __kmemcg_cache_deactivate()

On Sat, Jan 14, 2017 at 12:54:47AM -0500, Tejun Heo wrote: > __kmem_cache_shrink() is called with %true @deactivate only for memcg > caches. Remove @deactivate from __kmem_cache_shrink() and introduce > __kmemcg_cache_deactivate() instead. Each memcg-supporting allocator > should implement it

Re: [PATCH] can: Fix kernel panic at security_sock_rcv_skb

Hello Eric, On 01/14/2017 04:43 AM, Liu Shuo wrote: On Thu 12.Jan'17 at 17:33:38 +0100, Oliver Hartkopp wrote: On 01/12/2017 02:01 PM, Eric Dumazet wrote: The main problem seems that the sockets themselves are not RCU protected. If CAN uses RCU for delivery, then sockets should be freed

[tip:perf/urgent] perf/x86: Reject non sampling events with precise_ip

Commit-ID: 18e7a45af91acdde99d3aa1372cc40e1f8142f7b Gitweb: http://git.kernel.org/tip/18e7a45af91acdde99d3aa1372cc40e1f8142f7b Author: Jiri Olsa AuthorDate: Tue, 3 Jan 2017 15:24:54 +0100 Committer: Ingo Molnar CommitDate: Sat, 14 Jan 2017 11:06:50

  1   2   3   4   5   6   7   >