Re: [PATCH] kbuild: remove deprecated host-progs variable

On Wed, Aug 8, 2018 at 10:19 PM, Masahiro Yamada wrote: > The host-progs has been supported as an alias of hostprogs-y at least > since the beginning of Git era, with the clear prompt: > Usage of host-progs is deprecated. Please replace with hostprogs-y! > > Enough time for the migration has pas

[PATCH v5 4/6] fork: Skip setting TIF_SIGPENDING in ptrace_init_task

The code in calculate_sigpending will now handle this so it is just redundant and possibly a little confusing to continue setting TIF_SIGPENDING in ptrace_init_task. Suggested-by: Oleg Nesterov Signed-off-by: "Eric W. Biederman" --- include/linux/ptrace.h | 2 -- 1 file changed, 2 deletions(-)

[PATCH v5 3/6] signal: Add calculate_sigpending()

Add a function calculate_sigpending to test to see if any signals are pending for a new task immediately following fork. Signals have to happen either before or after fork. Today our practice is to push all of the signals to before the fork, but that has the downside that frequent or periodic sig

[PATCH v5 5/6] fork: Have new threads join on-going signal group stops

There are only two signals that are delivered to every member of a signal group: SIGSTOP and SIGKILL. Signal delivery requires every signal appear to be delivered either before or after a clone syscall. SIGKILL terminates the clone so does not need to be considered. Which leaves only SIGSTOP that

[PATCH v5 2/6] fork: Unconditionally exit if a fatal signal is pending

In practice this does not change anything as testing for fatal_signal_pending and exiting for with an error code duplicates the work of the next clause which recalculates pending signals and then exits fork if any are pending. In both cases the pending signal will trigger the slow path when existin

[PATCH v5 6/6] signal: Don't restart fork when signals come in.

Wen Yang and majiang report that a periodic signal received during fork can cause fork to continually restart preventing an application from making progress. The code was being overly pesimistic. Fork needs to guarantee that a signal sent to multiple processes is logically delivered before the

[PATCH v5 1/6] fork: Move and describe why the code examines PIDNS_ADDING

Normally this would be something that would be handled by handling signals that are sent to a group of processes but in this case the forking process is not a member of the group being signaled. Thus special code is needed to prevent a race with pid namespaces exiting, and fork adding new processe

Re: [PATCH] sched: idle: Reenable sched tick for cpuidle request

On Thu, Aug 09, 2018 at 01:47:27PM +0800, Leo Yan wrote: > The idle loop stops tick by respecting the decision from cpuidle > framework, if the condition 'need_resched()' is false without any task > scheduling, the CPU keeps running in the loop in do_idle() and it has no > chance call tick_nohz_idl

Re: [PATCH] ALSA: usb-audio: Mark expected switch fall-through

On Thu, 09 Aug 2018 00:23:44 +0200, Gustavo A. R. Silva wrote: > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > Addresses-Coverity-ID: 1357413 ("Missing break in switch") > Addresses-Coverity-ID: 114917 ("Missing break in swi

[PATCH v5 0/6] Not restarting for due to signals.

This builds on patches 1-15 of my previous patch posting. As those are non-controversial I am not posting them again. I took longer than I had hoped to get this set together because a kernel testing robot noticed some random corruption with the way I had been adding to the list. I finally trac

Re: [PATCH] ALSA: mixart_core: Mark expected switch fall-through

On Thu, 09 Aug 2018 00:11:48 +0200, Gustavo A. R. Silva wrote: > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > where we are expecting to fall through. > > Notice that in this particular case, I replaced the code comment with > a proper "fall through" annotation, which

[PATCH] kconfig: fix the rule of mainmenu_stmt symbol

The rule of mainmenu_stmt does not have debug print of zconf_lineno(), but if it had, it would print a wrong line number for the same reason as commit b2d00d7c61c8 ("kconfig: fix line numbers for if-entries in menu tree"). The mainmenu_stmt does not need to eat following empty lines because they a

Re: [PATCH v5 5/5] Auto-detect whether a FPU exists

On Wed, Aug 08, 2018 at 11:31:24PM -0700, Christoph Hellwig wrote: > > extern unsigned long elf_hwcap; > > +extern bool has_fpu; > > #endif > > Doesn't this conflict with the !CONFIG_CPU stub in switch_to.h? switch_to.h did include asm/hwcap.h, but the !CONFIG_FPU stub +#define has_fpu false

[PATCH v2] i2c: xlp9xx: Fix case where SSIF read transaction completes early

During ipmi stress tests we see occasional failure of transactions at the boot time. This happens in the case of a I2C_M_RECV_LEN transactions, when the read transfer completes (with the initial read length of 34) before the driver gets a chance to handle interrupts. The current driver code expect

Re: [PATCH 03/11] dt-bindings: interrupt-controller: RISC-V PLIC documentation

On Wed, Aug 08, 2018 at 11:29:17PM -0700, Palmer Dabbelt wrote: >> So I guess to answer my question, you are just making up version >> numbers. Unless you are doing the IP verilog too, don't do that. > > Well, in this case my proposal would be that we change the hardware team's > versioning scheme

Re: [PATCH v4 3/7] dt-bindings: dmaengine: xilinx_dma: add optional xlnx,sg-length-width property

On Tue, Aug 7, 2018 at 4:56 PM, Rob Herring wrote: > On Thu, Aug 02, 2018 at 04:10:08PM +0200, Andrea Merello wrote: >> The width of the "length register" cannot be autodetected, and it is now >> specified with a DT property. Add DOC for it. >> >> Cc: Rob Herring >> Cc: Mark Rutland >> Cc: devic

Re: [PATCH v5 5/5] Auto-detect whether a FPU exists

> extern unsigned long elf_hwcap; > +extern bool has_fpu; > #endif Doesn't this conflict with the !CONFIG_CPU stub in switch_to.h? It seems like we should only have this definition in one place to start with. Otherwise this looks fine to me: Reviewed-by: Christoph Hellwig

Re: [PATCH] PCI: Fix calculation of bridge window's size

Hi Bjorn, Here is the public bug. https://bugzilla.kernel.org/show_bug.cgi?id=200769 Best regards, AceLan Kao. 2018-08-09 2:00 GMT+08:00 Bjorn Helgaas : > On Wed, Aug 08, 2018 at 01:48:37PM +0800, AceLan Kao wrote: >> There are some 0 resource size pci devices, and it leads to the >> accumulator

Re: [PATCH 03/11] dt-bindings: interrupt-controller: RISC-V PLIC documentation

On Wed, 08 Aug 2018 16:32:07 PDT (-0700), robh...@kernel.org wrote: On Wed, Aug 8, 2018 at 1:38 PM Palmer Dabbelt wrote: On Wed, 08 Aug 2018 07:16:14 PDT (-0700), robh...@kernel.org wrote: > On Tue, Aug 7, 2018 at 8:17 PM Palmer Dabbelt wrote: >> >> On Mon, 06 Aug 2018 13:59:48 PDT (-0700), r

[PATCH v5 5/5] Auto-detect whether a FPU exists

We expect that a kernel with CONFIG_FPU=y can still support no-FPU machines. To do so, the kernel should first examine the existence of a FPU, then do nothing if a FPU does exist; otherwise, it should disable/bypass all FPU-related functions. In this patch, a new global variable, has_fpu, is creat

[PATCH v5 4/5] Allow to disable FPU support

FPU codes have been separated from common part in previous patches. This patch add the CONFIG_FPU option and some stubs, so that a no-FPU configuration is allowed. Signed-off-by: Alan Kao Cc: Greentime Hu Cc: Vincent Chen Cc: Zong Li Cc: Nick Hu Reviewed-by: Christoph Hellwig --- arch/riscv

[PATCH v5 2/5] Refactor FPU code in signal setup/return procedures

FPU-related logic is separated from normal signal handling path in this patch. Kernel can easily be configured to exclude those procedures for no-FPU systems. Signed-off-by: Alan Kao Cc: Greentime Hu Cc: Vincent Chen Cc: Zong Li Cc: Nick Hu Reviewed-by: Christoph Hellwig --- arch/riscv/ker

[PATCH v5 3/5] Cleanup ISA string setting

Just a side note: (Assume that atomic and compressed is on) Before this patch, assembler was always given the riscv64imafdc MARCH string because there are fld/fsd's in entry.S; compiler was always given riscv64imac because kernel doesn't need floating point code generation. After this, the MARCH

[PATCH v5 1/5] Extract FPU context operations from entry.S

We move __fstate_save and __fstate_restore to a new source file, fpu.S. Signed-off-by: Alan Kao Cc: Greentime Hu Cc: Vincent Chen Cc: Zong Li Cc: Nick Hu Reviewed-by: Christoph Hellwig --- arch/riscv/kernel/Makefile | 1 + arch/riscv/kernel/entry.S | 87 -- a

[PATCH v5 0/5] riscv: Add support to no-FPU systems

This patchset adds an option, CONFIG_FPU, to enable/disable floating- point procedures. Kernel's new behavior will be as follows: * with CONFIG_FPU=y All FPU codes are reserved. If no FPU is found during booting, a global flag will be set, and those functions will be bypassed with conditio

Re: [PATCH v8 20/22] KVM: s390: Handling of Cypto control block in VSIE

On 08.08.2018 16:44, Tony Krowiak wrote: > From: Pierre Morel > +#define ECA_APIE 0x0008 That shouldn't be necessary, it's defined in kvm_host.h which vsie.c includes. Or is it not? > +static int shadow_crycb(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page) > +{ > + struct kvm_s390_si

Re: [PATCH v3 20/20] signal: Don't restart fork when signals come in.

Oleg Nesterov writes: > On 07/26, Eric W. Biederman wrote: >> >> Are the earlier patches looking ok to you? > > I obviously like 1-15. > > "[PATCH 16/20] fork: Move and describe why the code examines PIDNS_ADDING" > is "interesting". I mean it is fine, but at the end of this series it doesn't > m

Re: [PATCH v2] RISC-V: Don't use a global include guard for uapi/asm/syscalls.h

This actually seems to break the compilation for me in for-next: hch@carbon:~/work/linux$ make ARCH=riscv CALLscripts/checksyscalls.sh :1335:2: warning: #warning syscall rseq not implemented [-Wcpp] CHK include/generated/compile.h CC arch/riscv/kernel/syscall_table.o ./arch/risc

Re: [PATCH v8 07/22] KVM: s390: refactor crypto initialization

On 08.08.2018 16:44, Tony Krowiak wrote: > From: Tony Krowiak > > This patch refactors the code that initializes and sets up the > crypto configuration for a guest. The following changes are > implemented via this patch: > > 1. Prior to the introduction of AP device virtualization, it >was n

Re: [PATCH v5 1/2] leds: core: Introduce LED pattern trigger

Hi Jacek, On 9 August 2018 at 05:28, Jacek Anaszewski wrote: > Hi Baolin, > > On 08/08/2018 08:01 AM, Baolin Wang wrote: >> Hi Jacek, >> >> On 8 August 2018 at 05:54, Jacek Anaszewski >> wrote: >>> Hi Baolin, >>> >>> Thank you for addressing the review remarks. >>> Since the patch set is target

[PATCH] sched: idle: Reenable sched tick for cpuidle request

The idle loop stops tick by respecting the decision from cpuidle framework, if the condition 'need_resched()' is false without any task scheduling, the CPU keeps running in the loop in do_idle() and it has no chance call tick_nohz_idle_exit() to enable the tick. This results in the idle loop canno

Crypto Fixes for 4.18

Hi Linus: This push fixes a performance regression in arm64 NEON crypto as well as a crash in x86 aegis/morus on unsupported CPUs. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Ard Biesheuvel (1): crypto: arm64 - revert NEON yield for fast

Re: [PATCH RFC 2/2] KVM: s390: introduce and use KVM_REQ_VSIE_RESTART

On 07.08.2018 14:51, David Hildenbrand wrote: > When we change the crycb (or execution controls), we also have to make sure > that the vSIE shadow datastructures properly consider the changed > values before rerunning the vSIE. We can achieve that by simply using a > VCPU request now. > > This has

Re: [PATCH RFC 1/2] KVM: s390: vsie: simulate VCPU SIE entry/exit

On 07.08.2018 14:51, David Hildenbrand wrote: > VCPU requests and VCPU blocking right now don't take care of the vSIE > (as it was not necessary until now). But we want to have VCPU requests > that will also be handled before running the vSIE again. > > So let's simulate a SIE entry when entering

[PATCH] kbuild: remove deprecated host-progs variable

The host-progs has been supported as an alias of hostprogs-y at least since the beginning of Git era, with the clear prompt: Usage of host-progs is deprecated. Please replace with hostprogs-y! Enough time for the migration has passed. Signed-off-by: Masahiro Yamada --- arch/xtensa/boot/Makef

Re: [PATCH 1/1] kbuild: allow alternate src for target's implicit prerequisite

2018-08-06 23:37 GMT+09:00 Vasily Gorbik : > With kbuild there is no easy way to re-compile source files from another > directory, which is required for the decompressor on some platforms > (files like lib/ctype.c, lib/cmdline.c, etc). Writing custom build > rules for those files is not feasible si

ALT+CTRL+F2 - Switch Terminal - agetty process

I am trying to understand how agetty process is called when ALT+CTRL+F2/ALT+CTRL+F3/ keys are pressed in CentOS or in any other linux distro. What I know so far - systemd runs agetty.service with next tty[N] number - agetty then run login process and then other process continues. What I want

Re: [PATCH] kbuild: add Map option to save vmlinux linker map file(s)

2018-08-06 22:38 GMT+09:00 Vasily Gorbik : > Add "Map" kbuild option, so that "make Map=1" would save vmlinux linker > map into vmlinux.map, which is quite useful during making kernel changes > related to how the kernel is composed. > > KBUILD_SAVE_LINK_MAP flag is exported and architectures > supp

[PATCH v3] perf report: Create auxiliary trace data files for s390

Create auxiliary trace data log files when invoked with option --itrace=d as in [root@s35lp76 perf] ./perf report -i perf.data.aux1 --stdio --itrace=d perf report creates several data files in the current directory named aux.smp.## where ## is a 2 digit hex number with leading zeros representing

Re: [PATCH] extcon: maxim: Add SPDX license identifiers

Hi Krzysztof, On 2018년 08월 08일 01:21, Krzysztof Kozlowski wrote: > Replace GPL v2.0+ license statements with SPDX license identifiers. > > Signed-off-by: Krzysztof Kozlowski > --- > drivers/extcon/extcon-max14577.c | 24 +++- > drivers/extcon/extcon-max77693.c | 22 ++---

Re: [PATCH 2/3] perf report: Add raw report support for s390 auxiliary trace

On 08/08/2018 06:42 PM, Arnaldo Carvalho de Melo wrote: > Em Wed, Aug 08, 2018 at 01:14:51PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Wed, Aug 08, 2018 at 01:08:43PM -0300, Arnaldo Carvalho de Melo escreveu: >>> No need for __packed. >> >>> I'm removing that to avoid having this failling i

[PATCH v8 0/6] Uprobes: Support SDT markers having reference count (semaphore)

v8 changes: - Call delayed_uprobe_remove(uprobe, NULL) from put_uprobe() as well. - Other minor optimizations. v7: https://lkml.org/lkml/2018/7/31/20 Description: Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. Applications like PostgreSQL, M

[PATCH v8 1/6] Uprobes: Simplify uprobe_register() body

Simplify uprobe_register() function body and let __uprobe_register() handle everything. Also move dependency functions around to fix build failures. Signed-off-by: Ravi Bangoria --- kernel/events/uprobes.c | 69 ++--- 1 file changed, 36 insertions(+),

[PATCH v8 5/6] trace_uprobe/sdt: Prevent multiple reference counter for same uprobe

We assume to have only one reference counter for one uprobe. Don't allow user to add multiple trace_uprobe entries having same inode+offset but different reference counter. Ex, # echo "p:sdt_tick/loop2 /home/ravi/tick:0x6e4(0x10036)" > uprobe_events # echo "p:sdt_tick/loop2_1 /home/ravi/tick:0

[PATCH v8 2/6] Uprobe: Additional argument arch_uprobe to uprobe_write_opcode()

Add addition argument 'arch_uprobe' to uprobe_write_opcode(). We need this in later set of patches. Signed-off-by: Ravi Bangoria --- arch/arm/probes/uprobes/core.c | 2 +- arch/mips/kernel/uprobes.c | 2 +- include/linux/uprobes.h| 2 +- kernel/events/uprobes.c| 9 +

[PATCH v8 6/6] perf probe: Support SDT markers having reference counter (semaphore)

With this, perf buildid-cache will save SDT markers with reference counter in probe cache. Perf probe will be able to probe markers having reference counter. Ex, # readelf -n /tmp/tick | grep -A1 loop2 Name: loop2 ... Semaphore: 0x10020036 # ./perf buildid-cache --add /tmp/tic

[PATCH v8 4/6] Uprobes/sdt: Prevent multiple reference counter for same uprobe

We assume to have only one reference counter for one uprobe. Don't allow user to register multiple uprobes having same inode+offset but different reference counter. Signed-off-by: Ravi Bangoria --- kernel/events/uprobes.c | 9 + 1 file changed, 9 insertions(+) diff --git a/kernel/events

[PATCH v8 3/6] Uprobes: Support SDT markers having reference count (semaphore)

Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. Applications like PostgreSQL, MySQL, Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc have these markers embedded in them. These markers are added by developer at important places

FUSE: write operations trigger balance_dirty_pages when using writeback cache

Dear Miklos, Recently I've been testing FUSE and libfuse example passthrough_ll with writeback cache on, and found out that the performance drops significantly compared to that in local filesystem. As I can see from trace, balance_dirty_pages is triggered very frequently even if there not enoug

Re: [PATCH] dmaengine: sprd: Support DMA link-list mode

Hi Vinod, (Comments from Eric Long) On 9 August 2018 at 10:32, Vinod wrote: > On 26-07-18, 16:00, Baolin Wang wrote: >> From: Eric Long >> >> The Spreadtrum DMA can support the link-list transaction mode, which means >> DMA controller can do transaction one by one automatically once we linked >>

Re: [PATCH 2/2] spi: sprd: Add SPI driver for Spreadtrum SC9860

Hi Trent, On 9 August 2018 at 03:08, Trent Piepho wrote: > On Wed, 2018-08-08 at 11:19 +0800, Baolin Wang wrote: >> On 8 August 2018 at 01:10, Trent Piepho wrote: >> > On Tue, 2018-08-07 at 18:43 +0800, Baolin Wang wrote: >> > > >> > > +static u32 sprd_spi_transfer_max_timeout(struct sprd_spi *s

Re: [PATCH 1/2] dt-bindings: spi: Add Spreadtrum SPI controller documentation

Hi Trent, On 9 August 2018 at 02:57, Trent Piepho wrote: > On Wed, 2018-08-08 at 11:54 +0100, Mark Brown wrote: >> On Wed, Aug 08, 2018 at 06:35:28PM +0800, Baolin Wang wrote: >> > On 8 August 2018 at 17:50, Mark Brown wrote: >> > > Right, I don't think we added this yet (if we did I can't see >

[PATCH v2 2/2] ASoC: trace: track dapm type in snd_soc_dapm_widget

Track snd_soc_dapm_widget:id which is used as dapm sequence index in dapm_down_seq/dapm_up_seq. It's useful for checking dapm seq after tracking it. Signed-off-by: Liu Changcheng diff --git a/include/trace/events/asoc.h b/include/trace/events/asoc.h index bf17edc..7c4e8de 100644 --- a/include/tr

[PATCH v2 1/2] ASoC: trace: remove unnecessary typecast

There's no need to do typecast since the defined type matches the output fromat requirement. Signed-off-by: Liu Changcheng diff --git a/include/trace/events/asoc.h b/include/trace/events/asoc.h index 40c300f..bf17edc 100644 --- a/include/trace/events/asoc.h +++ b/include/trace/events/asoc.h @@ -

[PATCH v2 0/2] ASoC: trace: format file and add trace field

1. Some typecast are not needed 2. trace dapm type in snd_soc_dapm_widget class event Liu Changcheng (2): ASoC: trace: remove unnecessary typecast ASoC: trace: track dapm type in snd_soc_dapm_widget v1->v2 correct code style to meet kernel requirement. include/trace/events/asoc.h | 21 ++

Re: [PATCH 0/4][RFC v2] Introduce the in-kernel hibernation encryption

Hi Pavel, Joey, Oliver Please let me describe the original requirement and my understanding about hibernation encryption here, thus help us sync on the same thread: On Wed, Aug 08, 2018 at 07:50:36PM +0200, Pavel Machek wrote: > Hi! > > > > > > User space doesn't need to involve. The EFI root key

[PATCH v3] resource: Merge resources on a node when hot-adding memory

When hot-removing memory release_mem_region_adjustable() splits iomem resources if they are not the exact size of the memory being hot-deleted. Adding this memory back to the kernel adds a new resource. Eg a node has memory 0x0 - 0xf. Offlining and hot-removing 1GB from 0xf4000 results

RE: [PATCH 0/4] locks: avoid thundering-herd wake-ups

On Wed, Aug 08 2018, Frank Filz wrote: > > Now here's another question... How does this new logic play with Open > File Description Locks? Should still be ok since there's a thread > waiting on each of those. At this level Posix locks and OFD locks are almost identical - just a different owner. S

Re: [PATCH v3 3/4] dmaengine: Add Actions Semi Owl family S900 DMA driver

On 26-07-18, 10:36, Manivannan Sadhasivam wrote: > Add Actions Semi Owl family S900 DMA driver. Applied, thanks -- ~Vinod

Re: [PATCH v3 1/4] dt-bindings: dmaengine: Add binding for Actions Semi Owl SoCs

On 26-07-18, 10:36, Manivannan Sadhasivam wrote: > Add devicetree binding for Actions Semi Owl SoCs DMA controller. Applied, thanks -- ~Vinod

[PATCH v1 2/2] ASoC: trace: track dapm type in snd_soc_dapm_widget

ASoC: trace: track dapm type in snd_soc_dapm_widget Track snd_soc_dapm_widget:id which is used as dapm sequence index in dapm_down_seq/dapm_up_seq. It's useful for checking dapm seq after tracking it. Signed-off-by: Liu Changcheng diff --git a/include/trace/events/asoc.h b/include/trace/events/

[PATCH v1 1/2] ASoC: trace: remove unnecessary typecast

There's no need to do typecast since the defined type matches the output fromat requirement. Signed-off-by: Liu Changcheng diff --git a/include/trace/events/asoc.h b/include/trace/events/asoc.h index 40c300f..bf17edc 100644 --- a/include/trace/events/asoc.h +++ b/include/trace/events/asoc.h @@ -

[PATCH v1 0/2] ASoC: trace: format file and add trace field

1. Some typecast are not needed. 2. trace dapm type in snd_soc_dapm_widget class event. Liu Changcheng (2): ASoC: trace: remove unnecessary typecast ASoC: trace: track dapm type in snd_soc_dapm_widget include/trace/events/asoc.h | 21 +++-- 1 file changed, 11 insertions(+), 1

Re: [PATCH v3 2/2] clk: meson: add sub MMC clock controller driver

Hi Jerome On 07/30/18 16:57, Jerome Brunet wrote: > On Fri, 2018-07-27 at 09:45 -0700, Stephen Boyd wrote: >> Quoting Stephen Boyd (2018-07-27 09:41:40) >>> Quoting Yixun Lan (2018-07-27 07:52:23) HI Stephen: On 07/26/2018 11:20 PM, Stephen Boyd wrote: > Quoting Yixun Lan (2018-

Re: [PATCH 07/46] dmaengine: omap-dma: use dmaenginem_async_device_register to simplify the code

On 03-08-18, 10:47, Peter Ujfalusi wrote: > > > On 2018-08-03 10:19, Huang Shijie wrote: > > Use dmaenginem_async_device_register to simplify the code: > >remove dma_async_device_unregister > > > > Signed-off-by: Huang Shijie > > --- > > drivers/dma/ti/omap-dma.c | 5 + > > 1 file chan

RE: [PATCH 0/4] locks: avoid thundering-herd wake-ups

> On Wed, Aug 08, 2018 at 03:54:45PM -0400, J. Bruce Fields wrote: > > On Wed, Aug 08, 2018 at 11:51:07AM +1000, NeilBrown wrote: > > > If you have a many-core machine, and have many threads all wanting > > > to briefly lock a give file (udev is known to do this), you can get > > > quite poor perfo

Re: [PATCH] dmaengine: sprd: Support DMA link-list mode

On 26-07-18, 16:00, Baolin Wang wrote: > From: Eric Long > > The Spreadtrum DMA can support the link-list transaction mode, which means > DMA controller can do transaction one by one automatically once we linked > these transaction by link-list register. > > Signed-off-by: Eric Long > Signed-of

Re: [PATCH mmc-next v3 0/3] solve SDHCI DWC MSHC 128MB DMA boundary limitation

Hi Adrian, Ulf, could you please review these patches? Any comments are welcome. Thanks in advance, Jisheng On Mon, 30 Jul 2018 10:42:28 +0800 Jisheng Zhang wrote: > When using DMA, if the DMA addr spans 128MB boundary, we have to split > the DMA transfer into two so that each one doesn't excee

[PATCH 5/5] fs/locks: create a tree of dependent requests.

When we find an existing lock which conflicts with a request, and the request wants to wait, we currently add the request to a list. When the lock is removed, the whole list is woken. This can cause the thundering-herd problem. To reduce the problem, we make use of the (new) fact that a pending re

[PATCH 4/5] fs/locks: split out __locks_wake_one()

This functionality will be useful in the next patch, so split it out from __locks_wake_up_blocks(). Signed-off-by: NeilBrown --- fs/locks.c | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/fs/locks.c b/fs/locks.c index d06658b2dc7a..fc64016d01ee 100644 --- a

[PATCH 3/5] fs/locks: change all *_conflict() functions to return a new enum.

In a future patch we will need to differentiate between conflicts that are "transitive" and those that aren't. A "transitive" conflict is defined as one where any lock that conflicts with the first (newly requested) lock would conflict with the existing lock. So change posix_locks_conflict(), floc

[PATCH 2/5] fs/locks: allow a lock request to block other requests.

Currently, a lock can block pending requests, but all pending requests are equal. If lots of pending requests are mutually exclusive, this means they will all be woken up and all but one will fail. This can hurt performance. So we will allow pending requests to block other requests. Only the fir

[PATCH 1/5] fs/locks: rename some lists and pointers.

struct file lock contains an 'fl_next' pointer which is used to point to the lock that this request is blocked waiting for. So rename it to fl_blocker. The fl_blocked list_head in an active lock is the head of a list of blocked requests. In a request it is a node in that list. These are two dist

[PATCH 0/5 - V2] locks: avoid thundering-herd wake-ups

This series adds "wake_non_conflicts()" to wake up any waiters that are being added beneath a lock that they don't actually conflict with, even though they conflict with a parent which conflict with the top-level blocker. Thanks for Bruce for highlighting this issue. This series hasn't been tested

Re: [PATCH] net/9p/trans_virtio.c: decrease the refcount of 9p virtio device when removing it

piaojun wrote on Thu, Aug 09, 2018: > > What exact kernel commit are you running? > > My kernel commit id 6edf1d4cb0acde, and I replace the 9p code with > 9p-next. And I wonder if this will work well? That is somewhere on top of 4.18-rc1 and got merged in 4.18-rc4, which are close enough so while

Re: [PATCH RFC ftrace/core] tracing: Directly call tracer and lockdep probes

On Wed, 8 Aug 2018 15:20:22 -0700 Joel Fernandes wrote: > On Wed, Aug 8, 2018 at 3:00 PM, Joel Fernandes (Google) > wrote: > > From: Steven Rostedt > > > > I realize I kept your authorship since I started working based on your patch > ;-) > > Well sorry about that, and you could change it

Re: [PATCH 0/4] locks: avoid thundering-herd wake-ups

On Wed, Aug 08 2018, J. Bruce Fields wrote: > On Wed, Aug 08, 2018 at 12:47:22PM -0400, Jeff Layton wrote: >> On Wed, 2018-08-08 at 11:51 +1000, NeilBrown wrote: >> > If you have a many-core machine, and have many threads all wanting to >> > briefly lock a give file (udev is known to do this), you

Re: [PATCH] net/9p/trans_virtio.c: decrease the refcount of 9p virtio device when removing it

Hi Dominique, On 2018/8/8 17:40, Dominique Martinet wrote: > piaojun wrote on Wed, Aug 08, 2018: >> I try to remove 9pnet_virtio.ko by 'rmmod 9pnet_virtio' as I want to >> replace it without rebooting system. > > I do that all the time when testing, it works for me. > What exact kernel commit are

Re: [PATCH v2] platform/x86: acer-wmi: refactor function has_cap

Hi Gustavo, Sorry for my delay! On Mon, Aug 06, 2018 at 03:38:32PM -0500, Gustavo A. R. Silva wrote: > Refactor function has_cap in order to avoid returning integer > values, when instead it should return booleans. > > This code was detected with the help of Coccinelle. > > Signed-off-by: Gust

Re: [PATCH RFC 01/10] rcu: Make CONFIG_SRCU unconditionally enabled

On Thu, Aug 09, 2018 at 07:31:25AM +1000, Dave Chinner wrote: > IMO, we've had enough recent bugs to deal with from shrinkers being > called before the filesystem is set up and from trying to handle > allocation errors during setup. Do we really want to make shrinker > shutdown just as prone to mis

Re: [PATCH v2 2/2] firmware: coreboot: Collapse platform drivers into bus core

Quoting Julius Werner (2018-08-08 12:07:30) > > +config GOOGLE_COREBOOT_TABLE_ACPI > > + tristate > > + default GOOGLE_COREBOOT_TABLE > > I don't think this helps in upgrading (as your commit message says) > unless you also keep the 'select GOOGLE_COREBOOT_TABLE' here, right? Oh yes s

RE: [PATCH 0/4] locks: avoid thundering-herd wake-ups

> On Wed, 2018-08-08 at 17:28 -0400, J. Bruce Fields wrote: > > On Wed, Aug 08, 2018 at 04:09:12PM -0400, J. Bruce Fields wrote: > > > On Wed, Aug 08, 2018 at 03:54:45PM -0400, J. Bruce Fields wrote: > > > > On Wed, Aug 08, 2018 at 11:51:07AM +1000, NeilBrown wrote: > > > > > If you have a many-cor

Re: [PATCH 03/11] dt-bindings: interrupt-controller: RISC-V PLIC documentation

On Wed, Aug 8, 2018 at 1:38 PM Palmer Dabbelt wrote: > > On Wed, 08 Aug 2018 07:16:14 PDT (-0700), robh...@kernel.org wrote: > > On Tue, Aug 7, 2018 at 8:17 PM Palmer Dabbelt wrote: > >> > >> On Mon, 06 Aug 2018 13:59:48 PDT (-0700), robh...@kernel.org wrote: > >> > On Thu, Aug 2, 2018 at 4:08 PM

[BUG] Loopback devices with 4k logical block size are not automatically scanned for GPT partitions

I think I found a bug with partition scanning/loopback devices with 4k logical sectors. It affects 4.14.x and 4.17.x kernels (and presumably others). I've also filed the bug on the kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=200749 Copied from the bugzilla report: Loop devices w

linux-next: build failure after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 defconfig) failed like this: Invalid absolute R_X86_64_32S relocation: __end_rodata_aligned /kisskb/src/arch/x86/boot/compressed/Makefile:127: recipe for target 'arch/x86/boot/compressed/vmlinux.relocs' failed Caused by commit

Re: [PATCH] misc: mic: SCIF Fix scif_get_new_port() error handling

On Thu, 2018-08-02 at 01:42 -0700, Dan Carpenter wrote: > There are only 2 callers of scif_get_new_port() and both appear to get > the error handling wrong. Both treat zero returns as error, but it > actually returns negative error codes and >= 0 on success. > > Fixes: e9089f43c9a7 ("misc: mic: S

Re: [PATCH v1 3/4] drivers: edac: Add EDAC driver support for QCOM SoCs

Reminder. Would someone review this EDAC patch series? Thanks, Narendra On 2018-08-01 13:33, Venkata Narendra Kumar Gutta wrote: From: Channagoud Kadabi Add error reporting driver for SBEs and DBEs. As of now, this driver supports erp for Last Level Cache Controller (LLCC). This driver take

Re: [PATCH RFC 01/10] rcu: Make CONFIG_SRCU unconditionally enabled

On Wed, Aug 08, 2018 at 04:02:29PM -0700, Shakeel Butt wrote: > On Wed, Aug 8, 2018 at 11:02 AM Josh Triplett wrote: > > > > On Wed, Aug 08, 2018 at 07:30:13PM +0300, Kirill Tkhai wrote: > > > On 08.08.2018 19:23, Kirill Tkhai wrote: > > > > On 08.08.2018 19:13, Josh Triplett wrote: > > > >> On We

Re: [PATCH RFC 01/10] rcu: Make CONFIG_SRCU unconditionally enabled

On Wed, Aug 8, 2018 at 11:02 AM Josh Triplett wrote: > > On Wed, Aug 08, 2018 at 07:30:13PM +0300, Kirill Tkhai wrote: > > On 08.08.2018 19:23, Kirill Tkhai wrote: > > > On 08.08.2018 19:13, Josh Triplett wrote: > > >> On Wed, Aug 08, 2018 at 01:17:44PM +0300, Kirill Tkhai wrote: > > >>> On 08.08.

Re: [PATCH v8 00/22] vfio-ap: guest dedicated crypto adapters

On 08/08/2018 12:25 PM, Cornelia Huck wrote: On Wed, 8 Aug 2018 10:44:10 -0400 Tony Krowiak wrote: From: Tony Krowiak Several major objections were raised to design changes introduced in the v7 patch series, so in order to avoid an extended discussion around these objections and to expedite

Re: [PATCH 0/4] locks: avoid thundering-herd wake-ups

On Wed, 2018-08-08 at 17:28 -0400, J. Bruce Fields wrote: > On Wed, Aug 08, 2018 at 04:09:12PM -0400, J. Bruce Fields wrote: > > On Wed, Aug 08, 2018 at 03:54:45PM -0400, J. Bruce Fields wrote: > > > On Wed, Aug 08, 2018 at 11:51:07AM +1000, NeilBrown wrote: > > > > If you have a many-core machine,

Re: [PATCH 1/4] dt-bindings: reset: Add PDC reset binding for SDM845 SoCs

On Wed, Aug 08, 2018 at 03:37:24PM -0600, Jordan Crouse wrote: > On Wed, Aug 08, 2018 at 09:14:05PM +0530, Sibi Sankar wrote: > > Hi Rob, > > Thanks for the review > > > > On 08/07/2018 11:46 PM, Rob Herring wrote: > > >On Tue, Jul 31, 2018 at 06:27:24PM +0530, Sibi S wrote: > > >>Hi Philipp, > >

Re: [PATCH v12 3/3] tracing: Centralize preemptirq tracepoints and unify their usage

On Wed, Aug 08, 2018 at 03:15:31PM -0700, Joel Fernandes wrote: > On Wed, Aug 8, 2018 at 1:18 PM, Paul E. McKenney > wrote: > [...] > >> >> >> It does start to seem like a show stopper :-( > >> >> > > >> >> > I suppose that an srcu_read_lock_nmi() and srcu_read_unlock_nmi() > >> >> > could > >> >

Re: [PATCH 0/4] locks: avoid thundering-herd wake-ups

On Wed, Aug 08 2018, J. Bruce Fields wrote: > On Wed, Aug 08, 2018 at 04:09:12PM -0400, J. Bruce Fields wrote: >> On Wed, Aug 08, 2018 at 03:54:45PM -0400, J. Bruce Fields wrote: >> > On Wed, Aug 08, 2018 at 11:51:07AM +1000, NeilBrown wrote: >> > > If you have a many-core machine, and have many t

RE: [PATCH 0/4] locks: avoid thundering-herd wake-ups

On Wed, Aug 08 2018, Frank Filz wrote: >> On Wed, Aug 08, 2018 at 03:54:45PM -0400, J. Bruce Fields wrote: >> > On Wed, Aug 08, 2018 at 11:51:07AM +1000, NeilBrown wrote: >> > > If you have a many-core machine, and have many threads all wanting >> > > to briefly lock a give file (udev is known to

[PATCH v2] perf ordered_events: fix crash in free_dup_event()

This patch fixes a bug in ordered_event.c:alloc_event(). An ordered_event struct was not initialized properly potentially causing crashes later on in free_dup_event() depending on the content of the memory. If it was NULL, then it would work fine, otherwise, it could cause crashes such as: $ perf

[PATCH] gpio: it87: Add support for IT8613

This was tested on actual hardware and found to work fine, but currently the official specifications of this chip could not be obtained to confirm the numbers. Signed-off-by: Leonid Bloch --- drivers/gpio/Kconfig | 3 ++- drivers/gpio/gpio-it87.c | 9 + 2 files changed, 11 insertions

[PATCH] ALSA: usb-audio: Mark expected switch fall-through

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Addresses-Coverity-ID: 1357413 ("Missing break in switch") Addresses-Coverity-ID: 114917 ("Missing break in switch") Signed-off-by: Gustavo A. R. Silva --- sound/usb/mixer.c | 2 ++ 1 fil

Re: [PATCH RFC ftrace/core] tracing: Directly call tracer and lockdep probes

On Wed, Aug 8, 2018 at 3:00 PM, Joel Fernandes (Google) wrote: > From: Steven Rostedt > I realize I kept your authorship since I started working based on your patch ;-) Well sorry about that, and you could change it to mine or keep it as is it is if you want ;-) thanks, - Joel > Due to vari

Re: [PATCH v12 3/3] tracing: Centralize preemptirq tracepoints and unify their usage

On Wed, Aug 8, 2018 at 1:18 PM, Paul E. McKenney wrote: [...] >> >> >> It does start to seem like a show stopper :-( >> >> > >> >> > I suppose that an srcu_read_lock_nmi() and srcu_read_unlock_nmi() could >> >> > be added, which would do atomic ops on sp->sda->srcu_lock_count. Not >> >> > sure >

  1   2   3   4   5   6   7   >