Re: [PATCH/RFC] Re: 'perf test BPF' failing, libbpf regression wrt "basic API for BPF obj name"

Em Thu, Nov 30, 2017 at 01:51:15PM -0800, Alexei Starovoitov escreveu: > On 11/30/17 11:00 AM, Arnaldo Carvalho de Melo wrote: > > > Instead of sinking all future bpf_attr's backward compatibility > > > requirements to sys_bpf, I would push it up to its own BPF_* command > > > helper which has a b

Re: [PATCH RFC 2/6] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously

On 01/12/2017 18:29, Stephen Hemminger wrote: >> +static inline u64 hv_read_tsc_page_tsc(const struct ms_hyperv_tsc_page >> *tsc_pg, >> + u64 *cur_tsc) >> +{ >> +*cur_tsc = rdtsc(); >> + >> +return cur_tsc; > Why do return and setting by reference. Looks l

Re: [PATCH v6 0/2] memory: Introduce ti-emif-sram driver

* Dave Gerlach [171130 22:58]: > This is a resend of v5 of this series found here [1]. It introduces > relocatable PM handlers for the emif that are copied to sram and > run from there during low power mode entry. > > The patches still have the previous ACKs but have a small change to > accomodat

Re: [PATCH] drm/panel: support Innolux P097PFG panel

On 30 November 2017 at 06:13, Lin Huang wrote: > Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel, > it refactor Innolux P079ZCA panel driver, let it support > multi panel, and add support P097PFG panel in this driver. > Couple of drive-by suggestions: Split the refactor vs new hw? > MODULE

Re: [PATCH v2 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On Fri, Dec 01, 2017 at 05:50:26PM +, Will Deacon wrote: > On Fri, Dec 01, 2017 at 02:04:06PM +, Mark Rutland wrote: > > On Thu, Nov 30, 2017 at 04:39:28PM +, Will Deacon wrote: > Thanks for going through this. Do you have any ideas about what we could > rename the command-line option t

Re: [PATCH RT] arm*: disable NEON in kernel mode

On Fri, Dec 01, 2017 at 03:03:35PM +, Ard Biesheuvel wrote: > > l > > On 1 Dec 2017, at 14:36, Sebastian Andrzej Siewior > > wrote: > > > >> On 2017-12-01 14:18:28 [+], Mark Rutland wrote: > >> [Adding Ard, who wrote the NEON crypto code] > >> > >>> On Fri, Dec 01, 2017 at 02:45:06PM +

Re: [PATCH 1/1] at24: Fix I²C device selection for runtime PM

Bartosz wrote: > Could you take a look if my rebase didn't break anything? Unfortunately the rebase broke multi-address eeprom support ;( I will post a corrected patch.

Re: [PATCH 21/21] x86/entry: Clean up the SYSENTER_stack code

On Mon, Nov 27, 2017 at 11:45:29AM +0100, Ingo Molnar wrote: > diff --git a/arch/x86/include/asm/fixmap.h b/arch/x86/include/asm/fixmap.h > index 81fdc405ab1f..5a1013df456e 100644 > --- a/arch/x86/include/asm/fixmap.h > +++ b/arch/x86/include/asm/fixmap.h > @@ -237,5 +237,10 @@ static inline struct

Re: [PATCH v2 12/18] arm64: entry: Explicitly pass exception level to kernel_ventry macro

On Fri, Dec 01, 2017 at 05:51:44PM +, Will Deacon wrote: > On Fri, Dec 01, 2017 at 11:58:36AM +, Mark Rutland wrote: > > On Thu, Nov 30, 2017 at 04:39:40PM +, Will Deacon wrote: > > > + .macro kernel_ventry, el, label, regsize = 64 > > > + b el\()\el\()_\label > > > - kernel_ve

Re: [Intel-gfx] [PATCH v2 2/8] drm/i915: Add more control to wait_for routines

On Fri, Dec 1, 2017 at 12:57 PM, Chris Wilson wrote: > Quoting Chris Wilson (2017-12-01 17:55:15) >> Quoting Sean Paul (2017-12-01 17:48:17) >> > On Fri, Dec 1, 2017 at 12:44 PM, Chris Wilson >> > wrote: >> > > The current wait_for() is a little more complicated nowadays (variable >> > > W). >>

[PATCH v2 0/2] sched/fair: remote load updates for idle CPUs

Hi, Here is the v2, which was just delayed by my holiday. Until a NOHZ idle balance takes place on behalf of a CPU (which may never happen), the blocked load of of its root cfs_rq and its contributions to task group shares are updated only by that CPU. That means if a CPU goes suddenly from being

[PATCH v2 2/2] sched/fair: Update blocked load from newly idle balance

We now have a NOHZ kick to avoid the load of idle CPUs becoming stale. This is good, but it brings about CPU wakeups, which have an energy cost. As an alternative to waking CPUs up to do decay blocked load, we can sometimes do it from newly idle balance. If the newly idle balance is on a domain tha

[PATCH v2 1/2] sched: force update of blocked load of idle cpus

From: Vincent Guittot When idle, the blocked load of CPUs will be updated only when an idle load balance is triggered which may never happen. Because of this uncertainty on the execution of idle load balance, the utilization, the load and the shares of idle cfs_rq can stay artificially high and s

Re: [PATCH v2 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On 12/01/2017 09:58 AM, Mark Rutland wrote: > On Fri, Dec 01, 2017 at 05:50:26PM +, Will Deacon wrote: >> On Fri, Dec 01, 2017 at 02:04:06PM +, Mark Rutland wrote: >>> On Thu, Nov 30, 2017 at 04:39:28PM +, Will Deacon wrote: >> Thanks for going through this. Do you have any ideas about

[PATCH] eeprom: at24: fix I2C device selection for runtime PM

From: Sakari Ailus The at24 driver creates dummy I2C devices to access offsets in the chip that are outside the area supported using a single I2C address. It is not meaningful to use runtime PM to such devices; the system firmware (ACPI) does not know about these devices nor runtime PM was enable

Re: [PATCH RT] arm*: disable NEON in kernel mode

On Fri, Dec 01, 2017 at 05:58:45PM +, Dave Martin wrote: > +1, at least for arm64. I don't see a really compelling reason for > holding kernel-mode NEON around memory management now that we have a > strict save-once-restore-lazily model. > > This may not work so well for arm though -- I haven

Re: [PATCH v2 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On Fri, Dec 01, 2017 at 10:02:43AM -0800, Dave Hansen wrote: > On 12/01/2017 09:58 AM, Mark Rutland wrote: > > On Fri, Dec 01, 2017 at 05:50:26PM +, Will Deacon wrote: > >> On Fri, Dec 01, 2017 at 02:04:06PM +, Mark Rutland wrote: > >>> On Thu, Nov 30, 2017 at 04:39:28PM +, Will Deacon

Re: [PATCH v4 2/3] dt-bindings: display: rockchip: update DSI controller

On Fri, Dec 01, 2017 at 11:58:04AM +0800, Nickey Yang wrote: > This patch update describe panel/port links, including > unit addresses in documentation of device tree bindings > for the rockchip DSI controller based on the Synopsys > DesignWare MIPI DSI host controller. > > Signed-off-by: Nickey Y

[GIT PULL] arm64: fixes for -rc2

Hi Linus, Please pull the following arm64 fixes for 4.15-rc2. The critical one here is a fix for fpsimd register corruption across signals which was introduced by the SVE support code (the register files overlap), but the others are worth having as well. Summary in the tag. Cheers, Will --->8

Re: [PATCH RT] arm*: disable NEON in kernel mode

On Fri, Dec 01, 2017 at 06:08:28PM +, Russell King - ARM Linux wrote: > On Fri, Dec 01, 2017 at 05:58:45PM +, Dave Martin wrote: > > +1, at least for arm64. I don't see a really compelling reason for > > holding kernel-mode NEON around memory management now that we have a > > strict save-o

Timer refuses to expire

Hello, Anna-Maria, It turned out that one set of problems was due to NO_HZ_FULL issues, which are addressed with a pair of patches. However, there is still one case of a timer refusing to expire in rcutorture's TREE01 test scenario. The takes from two to four hours to trigger, and the most recent

Re: [patches] Re: [PATCH 08/10] RISC-V: Set __ARCH_WANT_RENAMEAT to pick up generic version

On Thu, Nov 30, 2017 at 10:38:32AM -0800, Palmer Dabbelt wrote: > index da09fb986459..dd5a9dd7a102 100644 > --- a/include/asm-generic/audit_dir_write.h > +++ b/include/asm-generic/audit_dir_write.h > @@ -27,7 +27,9 @@ __NR_mknod, > __NR_mkdirat, > __NR_mknodat, > __NR_unlinkat, > +#ifdef __NR_renam

Re: [PATCH v1 2/2] drm/tinydrm: add driver for ILI9225 panels

(cc: Thierry) Den 01.12.2017 15.03, skrev Linus Walleij: On Wed, Nov 8, 2017 at 4:52 AM, David Lechner wrote: This adds a new driver for display panels based on the Ilitek ILI9225 controller. This was developed for a no-name panel with a red PCB that is commonly marketed for Arduino. See

Re: [PATCH v5 04/12] perf util: Add rbtree node_delete ops

On Fri, Dec 01, 2017 at 11:14:52AM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Dec 01, 2017 at 06:57:28PM +0800, Jin Yao escreveu: > > @@ -130,7 +140,7 @@ void perf_stat__init_shadow_stats(void) > > rblist__init(&runtime_saved_values); > > runtime_saved_values.node_cmp = saved_value_cm

Re: [PATCH v4 1/3] drm/bridge/synopsys: dsi: stop clobbering drvdata

On 1 December 2017 at 08:32, Philippe CORNU wrote: > Dear Nickey, > > Many thanks for your patch. > > I am sorry to say that but you can not add my "Acked-by" to this patch > because this code is different from the "original" one from Brian (which > got my "Acked-by"). > Small idea: I've seen peo

[PATCH] sched/rt: Do not do push/pull when there is only one CPU

Daniel Wagner reported a crash on the beaglebone black. This is a single CPU architecture, and does not have a functional: arch_send_call_function_single_ipi() and can crash if that is called. As it only has one CPU, it shouldn't be called, but if the kernel is compiled for SMP, the push/pull RT

Re: [PATCH] builddeb: introduce variables for control-file customization

Am Fri, 1 Dec 2017 16:51:12 + schrieb Ben Hutchings : > On Fri, 2017-12-01 at 15:56 +, Henning Schild wrote: > > The debian packages coming out of "make *deb-pkg" lack some critical > > information in the control-files e.g. the "Depends:" field. If one > > tries to install a fresh system w

Re: [PATCH] eeprom: at24: fix I2C device selection for runtime PM

I'm not sure what happened here, but the patch is against the wrong tree. I will fix and resend the patch, and mark it clearly as [PATCH v2].

[PATCH v2] eeprom: at24: fix I2C device selection for runtime PM

From: Sakari Ailus The at24 driver creates dummy I2C devices to access offsets in the chip that are outside the area supported using a single I2C address. It is not meaningful to use runtime PM to such devices; the system firmware (ACPI) does not know about these devices nor runtime PM was enable

[PATCHv5 1/1] ima: re-introduce own integrity cache lock

The original design was discussed 3+ years ago, but was never completed/upstreamed. Based on the recent discussions with Linus https://patchwork.kernel.org/patch/9975919, I've rebased this patch. Before IMA appraisal was introduced, IMA was using own integrity cache lock along with i_mutex. proce

Re: [PATCH v2 0/8] drm/i915: Implement HDCP

Hi Sean, On 12/01/2017 06:20 PM, Sean Paul wrote: > Ok, here's v2 of the HDCP patchset, no longer RFC since I've tackled the TODO > list I set out in the first version (Annotated below for convenience). > > The big changes to take note of in v2 is locking. To account for atomic async > + > the p

Re: [PATCH] builddeb: introduce variables for control-file customization

On Fri, 2017-12-01 at 19:34 +0100, Henning Schild wrote: > Am Fri, 1 Dec 2017 16:51:12 + > schrieb Ben Hutchings : > > > On Fri, 2017-12-01 at 15:56 +, Henning Schild wrote: > > > The debian packages coming out of "make *deb-pkg" lack some critical > > > information in the control-files e.

Re: [PATCH v2 0/8] drm/i915: Implement HDCP

On Fri, Dec 1, 2017 at 1:47 PM, Hans Verkuil wrote: > Hi Sean, > > On 12/01/2017 06:20 PM, Sean Paul wrote: >> Ok, here's v2 of the HDCP patchset, no longer RFC since I've tackled the TODO >> list I set out in the first version (Annotated below for convenience). >> >> The big changes to take note

Re: waitqueue lockdep annotation

On 12/01/2017 12:11 PM, Christoph Hellwig wrote: > On Thu, Nov 30, 2017 at 05:18:07PM -0500, Jason Baron wrote: >> Yes, but for those cases it uses the ep->poll_wait waitqueue not the >> ep->wq, which is guarded by the ep->wq->lock. > > True. So it looks like we have one waitqueue in the system

Re: [PATCH 00/11] fs: use freeze_fs on suspend/hibernate

On Thu, 2017-11-30 at 17:41 +0100, Jiri Kosina wrote: > On Fri, 1 Dec 2017, Yu Chen wrote: > > > BTW, is nfs able to be included in this set? I also encountered a > > freeze() failure due to nfs access during that stage recently. > > The freezer usage in NFS is magnitudes more complicated, so it

Re: [PATCH v2 6/8] drm/i915: Add function to output Aksv over GMBUS

On Fri, Dec 01, 2017 at 12:20:28PM -0500, Sean Paul wrote: > Once the Aksv is available in the PCH, we need to get it on the wire to > the receiver via DDC. The hardware doesn't allow us to read the value > directly, so we need to tell GMBUS to source the Aksv internally and > send it to the right

Re: general protection fault in af_alg_free_areq_sgls

On Fri, Dec 01, 2017 at 10:01:01AM -0800, syzbot wrote: > kasan: CONFIG_KASAN_INLINE enabled > kasan: GPF could be caused by NULL-ptr deref or user memory access > general protection fault: [#1] SMP KASAN > Dumping ftrace buffer: >(ftrace buffer empty) > Modules linked in: > CPU: 1 PID: 30

[PATCH] bpf: Fix compile warnings when !CONFIG_BPF_SYSCALL

Such as: In file included from ./include/trace/events/xdp.h:10:0, from ./include/linux/bpf_trace.h:6, from drivers/net/ethernet/intel/i40e/i40e_txrx.c:29: ./include/trace/events/xdp.h:94:17: warning: ‘struct bpf_map’ declared inside parameter list const struc

Re: KASAN: stack-out-of-bounds Write in sha3_update

On Tue, Nov 28, 2017 at 05:23:01AM -0800, syzbot wrote: > == > BUG: KASAN: stack-out-of-bounds in memcpy include/linux/string.h:341 > [inline] > BUG: KASAN: stack-out-of-bounds in sha3_update+0xdf/0x2e0 > crypto/sha3_generic.c:161 > Wr

Re: KASAN: use-after-free Read in aead_recvmsg

On Mon, Nov 27, 2017 at 10:56:46AM -0800, syzbot wrote: > == > BUG: KASAN: use-after-free in skcipher_request_set_tfm > include/crypto/skcipher.h:499 [inline] > BUG: KASAN: use-after-free in crypto_aead_copy_sgl > crypto/algif_aead.c:8

Re: [PATCH v2 6/8] drm/i915: Add function to output Aksv over GMBUS

On Fri, Dec 1, 2017 at 2:06 PM, Ville Syrjälä wrote: > On Fri, Dec 01, 2017 at 12:20:28PM -0500, Sean Paul wrote: >> Once the Aksv is available in the PCH, we need to get it on the wire to >> the receiver via DDC. The hardware doesn't allow us to read the value >> directly, so we need to tell GMBU

Re: [PATCH RT] arm*: disable NEON in kernel mode

On 1 December 2017 at 18:24, Dave Martin wrote: > On Fri, Dec 01, 2017 at 06:08:28PM +, Russell King - ARM Linux wrote: >> On Fri, Dec 01, 2017 at 05:58:45PM +, Dave Martin wrote: >> > +1, at least for arm64. I don't see a really compelling reason for >> > holding kernel-mode NEON around

[PATCH tip/core/rcu 01/10] sched: Stop resched_cpu() from sending IPIs to offline CPUs

The rcutorture test suite occasionally provokes a splat due to invoking resched_cpu() on an offline CPU: WARNING: CPU: 2 PID: 8 at /home/paulmck/public_git/linux-rcu/arch/x86/kernel/smp.c:128 native_smp_send_reschedule+0x37/0x40 Modules linked in: CPU: 2 PID: 8 Comm: rcu_preempt Not tainted 4.14

[PATCH tip/core/rcu 0/10] Don not IPI offline CPUs, de-emphasize cond_resched_rcu_qs()

Hello! This series provides some fixes to prevent sending IPIs to offline CPUs and also replaces most uses of cond_resched_rcu_qs() with the new and improved cond_resched(). There are still a few remaining uses of cond_resched_rcu_qs() in rcutorture because the mechanisms that strengthen cond_res

[PATCH tip/core/rcu 06/10] trace: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

Now that cond_resched() also provides RCU quiescent states when needed, it can be used in place of cond_resched_rcu_qs(). This commit therefore makes this change. Signed-off-by: Paul E. McKenney Cc: Steven Rostedt Cc: Ingo Molnar --- kernel/trace/trace_benchmark.c | 2 +- 1 file changed, 1 in

[PATCH tip/core/rcu 03/10] netfilter: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

Now that cond_resched() also provides RCU quiescent states when needed, it can be used in place of cond_resched_rcu_qs(). This commit therefore makes this change. Signed-off-by: Paul E. McKenney Cc: Pablo Neira Ayuso Cc: Jozsef Kadlecsik Cc: Florian Westphal Cc: "David S. Miller" Cc: --- n

[PATCH tip/core/rcu 08/10] fs: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

Now that cond_resched() also provides RCU quiescent states when needed, it can be used in place of cond_resched_rcu_qs(). This commit therefore makes this change. Signed-off-by: Paul E. McKenney Cc: Alexander Viro Cc: --- fs/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -

[PATCH tip/core/rcu 05/10] workqueue: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

Now that cond_resched() also provides RCU quiescent states when needed, it can be used in place of cond_resched_rcu_qs(). This commit therefore makes this change. Signed-off-by: Paul E. McKenney Cc: Tejun Heo Cc: Lai Jiangshan --- kernel/workqueue.c | 2 +- 1 file changed, 1 insertion(+), 1 d

[PATCH tip/core/rcu 07/10] softirq: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

Now that cond_resched() also provides RCU quiescent states when needed, it can be used in place of cond_resched_rcu_qs(). This commit therefore makes this change. Signed-off-by: Paul E. McKenney Cc: NeilBrown Cc: Ingo Molnar --- kernel/softirq.c | 2 +- 1 file changed, 1 insertion(+), 1 delet

[PATCH tip/core/rcu 09/10] doc: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

Now that cond_resched() also provides RCU quiescent states when needed, it can be used in place of cond_resched_rcu_qs(). This commit therefore documents this change. Signed-off-by: Paul E. McKenney --- Documentation/RCU/Design/Data-Structures/Data-Structures.html | 3 ++- Documentation/RCU/De

Re: 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail

On Fri, Dec 01, 2017 at 10:40:12AM +0800, Fengguang Wu wrote: > Hi Eric, > > We noticed LTP keyctl06 test regression in > > commit: 3239b6f29bdfb4b0a2ba59df995fc9e6f4df7f1f ("KEYS: return full count in > keyring_read() if buffer is too small") > https://git.kernel.org/cgit/linux/kernel/git/torva

[PATCH tip/core/rcu 10/10] rcu: Account for rcu_all_qs() in cond_resched()

If cond_resched() returns false, then it has already invoked rcu_all_qs(). This is also invoked (now redundantly) by rcu_note_voluntary_context_switch(). This commit therefore changes cond_resched_rcu_qs() to invoke rcu_note_voluntary_context_switch_lite() instead of rcu_note_voluntary_context_sw

Re: [PATCH net-next 3/3] xfrm: Add ESN support for IPSec HW offload

On 11/30/2017 10:23 PM, Steffen Klassert wrote: On Tue, Nov 28, 2017 at 11:49:30AM +0200, yoss...@mellanox.com wrote: From: Yossef Efraim This patch adds ESN support to IPsec device offload. Adding new xfrm device operation to synchronize device ESN. Signed-off-by: Yossef Efraim --- includ

Re: [PATCH v2 2/2] cros_ec: Move cros_ec_dev module to drivers/mfd

Reviewed-by: Gwendal Grignou On Thu, Nov 30, 2017 at 12:50 PM, Guenter Roeck wrote: > On Mon, Nov 20, 2017 at 8:15 AM, Thierry Escande > wrote: >> The cros_ec_dev module is responsible for registering the MFD devices >> attached to the ChromeOS EC. This patch moves this module to drivers/mfd >>

Re: [PATCH net-next 3/3] xfrm: Add ESN support for IPSec HW offload

On 11/28/2017 1:49 AM, yoss...@mellanox.com wrote: From: Yossef Efraim This patch adds ESN support to IPsec device offload. Adding new xfrm device operation to synchronize device ESN. Signed-off-by: Yossef Efraim --- include/linux/netdevice.h | 1 + include/net/xfrm.h| 12

Re: [PATCH v2 1/2] cros_ec: Split cros_ec_devs module

Reviewed-by: Gwendal Grignou On Thu, Nov 30, 2017 at 12:49 PM, Guenter Roeck wrote: > On Mon, Nov 20, 2017 at 8:15 AM, Thierry Escande > wrote: >> This patch splits the cros_ec_devs module in two parts with a >> cros_ec_dev module responsible for handling MFD devices registration and >> a cros_

[PATCH tip/core/rcu 02/10] sched: Stop switched_to_rt() from sending IPIs to offline CPUs

The rcutorture test suite occasionally provokes a splat due to invoking rt_mutex_lock() which needs to boost the priority of a task currently sitting on a runqueue that belongs to an offline CPU: WARNING: CPU: 0 PID: 12 at /home/paulmck/public_git/linux-rcu/arch/x86/kernel/smp.c:128 native_smp_s

[PATCH tip/core/rcu 04/10] mm: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

Now that cond_resched() also provides RCU quiescent states when needed, it can be used in place of cond_resched_rcu_qs(). This commit therefore makes this change. Signed-off-by: Paul E. McKenney Cc: Andrew Morton Cc: "Kirill A. Shutemov" Cc: Vlastimil Babka --- mm/mlock.c | 2 +- 1 file chan

Re: [PATCH v2 3/4] Add support for AMD Core Perf Extension in guest

On 11/17/2017 5:44 AM, Borislav Petkov wrote: On Thu, Nov 16, 2017 at 12:00:11PM -0600, Natarajan, Janakarajan wrote: Ah my apologies. So when the pmu is initialized the cpuid entries aren't available then. So let's see: ... kvm_arch_vcpu_create() -> svm_create_vcpu() -> kvm_vcpu_init() -> kvm

Re: [PATCH] bpf: Fix compile warnings when !CONFIG_BPF_SYSCALL

On 12/01/2017 08:06 PM, Jason Gunthorpe wrote: > Such as: > > In file included from ./include/trace/events/xdp.h:10:0, > from ./include/linux/bpf_trace.h:6, > from drivers/net/ethernet/intel/i40e/i40e_txrx.c:29: > ./include/trace/events/xdp.h:94:17: warning: ‘stru

[PATCH tip/core/rcu 0/17] RCU dyntick updates for v4.16

Hello! This series includes simplifications of RCU's dyntick-idle processing, most importantly making use of the the NMI style of processing for interrupts as well as NMIs. This series provides a net decrease of more than 100 lines of code. 1. Avoid ->dynticks_nmi_nesting store tearing. 2.

[PATCH tip/core/rcu 13/17] rcu: Fold rcu_eqs_enter_common() into rcu_eqs_enter()

There is now only one call to rcu_eqs_enter_common() and there is no other reason to keep it separate. This commit therefore inlines it into its sole call site, saving a few lines of code in the process. Signed-off-by: Paul E. McKenney --- kernel/rcu/tree.c | 43

[PATCH tip/core/rcu 10/17] rcu: Add ->dynticks field to rcu_dyntick trace event

Signed-off-by: Paul E. McKenney --- include/trace/events/rcu.h | 13 - kernel/rcu/tree.c | 16 +++- 2 files changed, 15 insertions(+), 14 deletions(-) diff --git a/include/trace/events/rcu.h b/include/trace/events/rcu.h index b0a48231ea0e..d103de9f8c10 100644 ---

[PATCH tip/core/rcu 03/17] rcu: Move rcu_nmi_{enter,exit}() to prepare for consolidation

This is a code-motion-only commit that prepares to define rcu_irq_enter() in terms of rcu_nmi_enter() and rcu_irq_exit() in terms of rcu_irq_exit(). Signed-off-by: Paul E. McKenney --- kernel/rcu/tree.c | 150 +++--- 1 file changed, 75 insertions(+

[PATCH tip/core/rcu 16/17] doc: Update dyntick-idle design documentation for NMI/irq consolidation

Signed-off-by: Paul E. McKenney --- .../Design/Data-Structures/Data-Structures.html| 46 +++--- 1 file changed, 32 insertions(+), 14 deletions(-) diff --git a/Documentation/RCU/Design/Data-Structures/Data-Structures.html b/Documentation/RCU/Design/Data-Structures/Data-Struct

[PATCH tip/core/rcu 06/17] rcu: Make ->dynticks_nesting be a simple counter

Now that ->dynticks_nesting counts only process-level dyntick-idle entry and exit, there is no need for the elaborate segmented counter with its guard fields and overflow checking. This commit therefore makes ->dynticks_nesting be a simple counter. Signed-off-by: Paul E. McKenney --- kernel/rcu

Re: [PATCH 00/18] gpio: mockup: updates for v4.16

On Mon, Nov 27, 2017 at 11:48 AM, Bartosz Golaszewski wrote: > The following series contains a number of updates for the gpio-mockup > module. All 13 patches applied. Excellent work! Yours, Linus Walleij

[PATCH tip/core/rcu 09/17] rcu: Shrink ->dynticks_{nmi_,}nesting from long long to long

Because the ->dynticks_nesting field now only contains the process-based nesting level instead of a value encoding both the process nesting level and the irq "nesting" level, we no longer need a long long, even on 32-bit systems. This commit therefore changes both the ->dynticks_nesting and ->dynt

[PATCH tip/core/rcu 11/17] rcu: Stop duplicating lockdep checks in RCU's idle-entry code

The three RCU_LOCKDEP_WARN() calls in rcu_eqs_enter_common() are redundant with other lockdep checks, so this commit removes them. Signed-off-by: Paul E. McKenney --- kernel/rcu/tree.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c index 5fe

[PATCH tip/core/rcu 14/17] rcu: Fold rcu_eqs_exit_common() into rcu_eqs_exit()

There is now only one call to rcu_eqs_exit_common() and there is no other reason to keep it separate. This commit therefore inlines it into its sole call site, saving a few lines of code in the process. Signed-off-by: Paul E. McKenney --- kernel/rcu/tree.c | 50 ++---

[PATCH tip/core/rcu 05/17] rcu: Define rcu_irq_{enter,exit}() in terms of rcu_nmi_{enter,exit}()

RCU currently uses two different mechanisms for tracking irqs and NMIs. This is unnecessary complexity: Given that NMIs can nest and given that RCU's tracking handles such nesting, the NMI tracking mechanism can also be used to track irqs. This commit therefore defines rcu_irq_enter() in terms of

[PATCH tip/core/rcu 12/17] rcu: Avoid ->dynticks_nesting store tearing

Although ->dynticks_nesting is updated only by process level, it is accessed from hardirq to check for interrupt-from-idle quiescent states. Store tearing is thus possible, so this commit applies WRITE_ONCE() to ->dynticks_nesting stores. Signed-off-by: Paul E. McKenney --- kernel/rcu/tree.c | 6

[PATCH tip/core/rcu 17/17] tracing, rcu: Remove no longer used trace event rcu_prep_idle

From: "Steven Rostedt (VMware)" Commit c0f4dfd4f90 ("rcu: Make RCU_FAST_NO_HZ take advantage of numbered callbacks") removed the only instances of trace_rcu_prep_idle, but did not remove the TRACE_EVENT() that creates it. As defined trace events take up memory within the kernel even when they are

[PATCH tip/core/rcu 02/17] rcu: Reduce dyntick-idle state space

Both extended-quiescent-state entry and exit first update the nesting counter and then adjust the dyntick-idle state. This means that there are four states: (1) Both nesting and dyntick idle indicate idle, (2) Nesting indicates idle but dyntick idle does not, (3) Nesting indicates non-idle and dyn

Re: [PATCH] MAINTAINERS: add myself as reviewer for gpio-mockup

On Mon, Nov 27, 2017 at 11:50 AM, Bartosz Golaszewski wrote: > The user space libgpiod project is now tightly coupled with the > gpio-mockup module, so let me know when any changes to it are being > proposed. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH] platform/x86: hp-wmi: Actually use mask parameter in hp_wmi_hw_state

On Tue, Nov 28, 2017 at 08:41:47PM +0100, Michel Dänzer wrote: > On 2017-11-28 08:30 PM, Andy Shevchenko wrote: > > On Tue, Nov 28, 2017 at 8:06 PM, Michel Dänzer wrote: > >> On 2017-11-28 05:57 PM, Darren Hart wrote: > >>> On Tue, Nov 28, 2017 at 04:17:58PM +0100, Michel Dänzer wrote: > We w

[PATCH tip/core/rcu 15/17] rcu: Simplify rcu_eqs_{enter,exit}() non-idle task debug code

The code that checks for non-idle non-nohz_idle-usermode tasks invoking rcu_eqs_enter() and rcu_eqs_exit() prints a considerable quantity of helpful information. However, these checks fire rarely, so the extra complexity is no longer worth it. This commit therefore replaces this debug code with s

[PATCH tip/core/rcu 04/17] rcu: Clamp ->dynticks_nmi_nesting at eqs entry/exit

In preparation for merging dyntick-idle irq handling into the NMI algorithm, clamp ->dynticks_nmi_nesting value to allow for interrupts that enter but never leave and vice versa. It is important that the clamping happen outside of the extended quiescent state. Otherwise, there will be short windo

[PATCH tip/core/rcu 01/17] rcu: Avoid ->dynticks_nmi_nesting store tearing

NMIs can nest, and store tearing could in theory happen on carries from one byte to the next. This commit therefore adds the WRITE_ONCE() macros preventing this. Signed-off-by: Paul E. McKenney --- kernel/rcu/tree.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/ker

[PATCH tip/core/rcu 07/17] rcu: Eliminate rcu_irq_enter_disabled()

Now that the irq path uses the rcu_nmi_{enter,exit}() algorithm, rcu_irq_enter() and rcu_irq_exit() may be used from any context. There is thus no need for rcu_irq_enter_disabled() and for the checks using it. This commit therefore eliminates rcu_irq_enter_disabled(). Signed-off-by: Paul E. McKen

[PATCH tip/core/rcu 08/17] rcu: Add tracing to irq/NMI dyntick-idle transitions

Signed-off-by: Paul E. McKenney --- include/trace/events/rcu.h | 14 -- kernel/rcu/tree.c | 6 ++ 2 files changed, 14 insertions(+), 6 deletions(-) diff --git a/include/trace/events/rcu.h b/include/trace/events/rcu.h index 59d40c454aa0..4674b21247f7 100644 --- a/include

[PATCH tip/core/rcu 0/6] Miscellaneous fixes for v4.16

Hello! This series provides miscellaneous fixes: 1. Prohibit call_srcu() use under raw spinlocks. This feature is not currently used and causes trouble for the -rt guys. 2. Change printk() %p to %pK in SRCU. 3. Change printk() %p to %pK in RCU. 4. Hide trace event

[PATCH tip/core/rcu 1/6] srcu: Prohibit call_srcu() use under raw spinlocks

Invoking queue_delayed_work() while holding a raw spinlock is forbidden in -rt kernels, which is exactly what __call_srcu() does, indirectly via srcu_funnel_gp_start(). This commit therefore downgrades Tree SRCU's locking from raw to non-raw spinlocks, which works because call_srcu() is not ever c

[PATCH tip/core/rcu 6/6] rcu: Remove have_rcu_nocb_mask from tree_plugin.h

From: Rakib Mullick Currently have_rcu_nocb_mask is used to avoid double allocation of rcu_nocb_mask during boot up. Due to different representation of cpumask_var_t on different kernel config CPUMASK=y(or n) it was okay. But now we have a helper cpumask_available(), which can be utilized to chec

[PATCH tip/core/rcu 2/6] srcu: Change printk() %p to %pK

This commit changes the %p printk() in rcutorture to %pK. This could be considered irrelevant, given that any user able to start rcutorture could inflict far heavier damage on the system, but it doesn't hurt to change it and doing so avoids script-generated noise. Reported-by: Tobin C. Harding S

[PATCH tip/core/rcu 5/6] rcu: Add comment giving debug strategy for double call_rcu()

The following statement has for some reason proven non-intuitive: WARN_ON_ONCE(rcu_segcblist_empty(&rdp->cblist) != (count == 0)); This commit therefore adds a comment that states that this warning usually triggers in response to a double call_rcu(), which is sort of like a double free.

[PATCH tip/core/rcu 3/6] rcu: Change printk() %p to %pK

This commit changes the %p printk() in rcutorture to %pK. This could be considered irrelevant, given that any user able to start rcutorture could inflict far heavier damage on the system, but it doesn't hurt to change it and doing so avoids script-generated noise. Reported-by: Tobin C. Harding S

[PATCH tip/core/rcu 4/6] tracing, rcu: Hide trace event rcu_nocb_wake when not used

From: "Steven Rostedt (VMware)" The trace event rcu_nocb_wake is only used when CONFIG_RCU_NOCB_CPU is defined. But the trace event is defined regardless. As defined trace events take up memory, it is a waste to have it defined when not used. Surround the trace event with an #ifdef to have it onl

Re: [PATCH] bpf: Fix compile warnings when !CONFIG_BPF_SYSCALL

On Fri, 1 Dec 2017 12:06:05 -0700 Jason Gunthorpe wrote: > Such as: > > In file included from ./include/trace/events/xdp.h:10:0, > from ./include/linux/bpf_trace.h:6, > from drivers/net/ethernet/intel/i40e/i40e_txrx.c:29: > ./include/trace/events/xdp.h:94:17: wa

Re: [PATCH 0/4] add support of pinctrl to MT7622 SoC

On Tue, Nov 28, 2017 at 4:49 AM, wrote: > From: Sean Wang > > The patchset adds support for pinctrl on MT7622 SoC. It would be good if the other Mediatek driver authors, Honzhou, Yingjoe, Biao and Maoguang could review this patch set. Yours, Linus Walleij

Re: [PATCH v5 1/3] platform/chrome: cros_ec_lpc: Register the driver if ACPI entry is missing.

Checked against 7412f0a0d90ee6ddbad4cde794f88f1489422f3a (CHROMIUM: platform/chrome: Support MKBP protocol over ACPI) Reviewed-by: Gwendal Grignou On Fri, Dec 1, 2017 at 5:42 AM, Thierry Escande wrote: > From: Enric Balletbo i Serra > > Commit 12278dc7c572 ("platform/chrome: cros_ec_lpc: Add su

Re: [PATCH v4 3/8] MIPS: Octeon: Add a global resource manager.

David, Greg, On Fri, Dec 1, 2017 at 6:42 PM, David Daney wrote: > On 11/30/2017 11:53 PM, Philippe Ombredanne wrote: [...] --- /dev/null +++ b/arch/mips/cavium-octeon/resource-mgr.c @@ -0,0 +1,371 @@ +// SPDX-License-Identifier: GPL-2.0 +/* + * Resource manager for O

[PATCH tip/core/rcu 07/21] rtnetlink: Update now-misleading smp_read_barrier_depends() comment

Now that READ_ONCE() implies smp_read_barrier_depends(), update the rtnl_dereference() header comment accordingly. Signed-off-by: Paul E. McKenney Cc: "David S. Miller" Cc: Vladislav Yasevich Cc: Mark Rutland Cc: David Ahern Cc: Vlad Yasevich --- include/linux/rtnetlink.h | 3 +-- 1 file ch

[PATCH tip/core/rcu 0/21] De-emphasize {smp_,}read_barrier_depends

Hello! Now that READ_ONCE() includes smp_read_barrier_depends(), almost nothing else needs to, the exceptions being DEC Alpha architecture-specific code and of course READ_ONCE() itself. This series therefore removes smp_read_barrier_depends() and read_barrier_depends() from elsewhere, as they no

[PATCH tip/core/rcu 06/21] rcu: Adjust read-side accessor comments for READ_ONCE()

Now that READ_ONCE() implies smp_read_barrier_depends(), the commit updates now-misleading comments to account for this change. Signed-off-by: Paul E. McKenney --- include/linux/rcupdate.h | 23 +++ 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/include/linux

[PATCH tip/core/rcu 03/21] drivers/net/ethernet/qlogic/qed: Fix __qed_spq_block() ordering

The __qed_spq_block() function expects an smp_read_barrier_depends() to order a prior READ_ONCE() against a later load that does not depend on the prior READ_ONCE(), an expectation that can fail to be met. This commit therefore replaces the READ_ONCE() with smp_load_acquire() and removes the smp_re

[PATCH tip/core/rcu 05/21] percpu: READ_ONCE() now implies smp_read_barrier_depends()

Because READ_ONCE() now implies smp_read_barrier_depends(), this commit removes the now-redundant smp_read_barrier_depends() following the READ_ONCE() in __ref_is_percpu(). Signed-off-by: Paul E. McKenney Acked-by: Tejun Heo Cc: Christoph Lameter --- include/linux/percpu-refcount.h | 6 +++---

[PATCH tip/core/rcu 10/21] locking: Remove smp_read_barrier_depends() from queued_spin_lock_slowpath()

Queued spinlocks are not used by DEC Alpha, and furthermore operations such as READ_ONCE() and release/relaxed RMW atomics are being changed to imply smp_read_barrier_depends(). This commit therefore removes the now-redundant smp_read_barrier_depends() from queued_spin_lock_slowpath(), and adjusts

Re: [PATCH] platform/x86: hp-wmi: Actually use mask parameter in hp_wmi_hw_state

On Tue, Nov 28, 2017 at 9:41 PM, Michel Dänzer wrote: > On 2017-11-28 08:30 PM, Andy Shevchenko wrote: >> On Tue, Nov 28, 2017 at 8:06 PM, Michel Dänzer wrote: >>> On 2017-11-28 05:57 PM, Darren Hart wrote: Merged in 4.15-rc1 >>> >>> AFAIK commits without >>> >>> Cc: sta...@vger.kernel.org

[PATCH tip/core/rcu 01/21] doc: READ_ONCE() now implies smp_barrier_depends()

This commit updates an example in memory-barriers.txt to account for the fact that READ_ONCE() now implies smp_barrier_depends(). Signed-off-by: Paul E. McKenney --- Documentation/memory-barriers.txt | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/Documentation/me

<    1   2   3   4   5   6   7   8   9   >