[PATCH V2 0/2] arm64/mm: Enable memory hot remove

This series enables memory hot remove on arm64 after fixing a memblock removal ordering problem in generic __remove_memory(). This is based on the following arm64 working tree. git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core Testing: Tested hot remove on arm64 for

[PATCH 3/3] ARM: mvebu: add SPDX license identifier

The license is clearly identified as GPL V2 - so just add in the appropriate SPDX license identifier. Signed-off-by: Nicholas Mc Guire --- Problem reported by checkpatch WARNING: Missing or malformed SPDX-License-Identifier tag in line 1 #1: FILE: arch/arm/mach-mvebu/board-v7.c:1: +/* Patch

[PATCH 1/3 RFC] ARM: mvebu: at least warn on kzalloc failure

Although it is very unlikely that the allocation during init would fail any such failure should point to the original cause rather than waiting for a null-pointer dereference to splat. Signed-off-by: Nicholas Mc Guire --- Problem located with experimental coccinelle script While this will not

[PATCH 2/3] ARM: mvebu: drop return from void function

The return statement is unnecessary here - so drop it. Signed-off-by: Nicholas Mc Guire --- Problem reported by checkpatch WARNING: void function return statements are not generally useful #141: FILE: arch/arm/mach-mvebu/board-v7.c:141: + return; +} Patch was compile-tested:

Re: INFO: task hung in do_exit

syzbot has bisected this bug to: commit 430e48ecf31f4f897047f22e02abdfa75730cad8 Author: Amitoj Kaur Chawla Date: Thu Aug 10 16:28:09 2017 + leds: lm3533: constify attribute_group structure bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f4cee320 start commit:

Re: [PATCH 5/6] iio: imx7d_adc: Use imx7d_adc_resume() in imx7d_adc_probe()

On Sun, Apr 7, 2019 at 4:15 AM Jonathan Cameron wrote: > > On Wed, 3 Apr 2019 00:03:24 -0700 > Andrey Smirnov wrote: > > > Initialization sequence performed in imx7d_adc_resume() is exactley > > the same as what's being done in imx7d_adc_probe(). Make use of the > > former in the latter to

Re: [PATCH 3/6] iio: imx7d_adc: Use devm_iio_device_register()

On Sun, Apr 7, 2019 at 4:07 AM Jonathan Cameron wrote: > > On Wed, 3 Apr 2019 00:03:22 -0700 > Andrey Smirnov wrote: > > > Use devm_iio_device_register() and drop explicit call to > > iio_device_unregister(). > > > > Signed-off-by: Andrey Smirnov > > Cc: Jonathan Cameron > > Cc: Hartmut

Re: [PATCH] new flag COPY_FILE_RANGE_FILESIZE for copy_file_range()

On Sat, Apr 13, 2019 at 03:54:39PM -0500, Shawn Landden wrote: /me pulls out his close-reading glasses and the copy_file_range manpage... > If flags includes COPY_FILE_RANGE_FILESIZE then the length > copied is the length of the file. off_in and off_out are > ignored. len must be 0 or the file

Re: perf tools:Is there any tools to found out the max latency by irq or cpu idle

On 4/13/19 2:01 AM, Linhaifeng wrote: > Sorry, the value 131081408 is just for example. Actually the result is like > this: > sqrt 2019-04-10 23:53:50: 43968 > sqrt 2019-04-10 23:53:51: 44060 > sqrt 2019-04-10 23:53:52: 49012 > sqrt 2019-04-10 23:53:53: 38172 > sqrt 2019-04-10 23:53:54:

Re: [PATCH 4/4] ARM: imx legacy: add an SPDX license identifier

On Sat, Apr 13, 2019 at 11:11:05AM -0300, Fabio Estevam wrote: > On Sat, Apr 13, 2019 at 4:30 AM Nicholas Mc Guire wrote: > > > > The header clearly identifies this code as GPL V2 or later - so pop > > in the SPDX license identifier. > > > > Signed-off-by: Nicholas Mc Guire > > --- > >

Re: [PATCH v5 4/5] xtensa: Replace CONFIG_DEBUG_KERNEL with CONFIG_DEBUG_MISC

On Sat, Apr 13, 2019 at 3:44 PM Sinan Kaya wrote: > > CONFIG_DEBUG_KERNEL should not impact code generation. Use the newly > defined CONFIG_DEBUG_MISC instead to keep the current code. > > Signed-off-by: Sinan Kaya > Reviewed-by: Josh Triplett > --- > arch/xtensa/include/asm/irqflags.h | 2 +-

[PATCH v5 3/5] mips: Replace CONFIG_DEBUG_KERNEL with CONFIG_DEBUG_MISC

CONFIG_DEBUG_KERNEL should not impact code generation. Use the newly defined CONFIG_DEBUG_MISC instead to keep the current code. Signed-off-by: Sinan Kaya Reviewed-by: Josh Triplett --- arch/mips/kernel/setup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v5 4/5] xtensa: Replace CONFIG_DEBUG_KERNEL with CONFIG_DEBUG_MISC

CONFIG_DEBUG_KERNEL should not impact code generation. Use the newly defined CONFIG_DEBUG_MISC instead to keep the current code. Signed-off-by: Sinan Kaya Reviewed-by: Josh Triplett --- arch/xtensa/include/asm/irqflags.h | 2 +- arch/xtensa/kernel/smp.c | 2 +- 2 files changed, 2

[PATCH v5 0/5] init: Do not select DEBUG_KERNEL by default

CONFIG_DEBUG_KERNEL has been designed to just enable Kconfig options. Kernel code generatoin should not depend on CONFIG_DEBUG_KERNEL. Proposed alternative plan: let's add a new symbol, something like DEBUG_MISC ("Miscellaneous debug code that should be under a more specific debug option but

[PATCH v5 1/5] init: Introduce DEBUG_MISC option

Introduce DEBUG_MISC ("Miscellaneous debug code that should be under a more specific debug option but isn't"), make it depend on DEBUG_KERNEL and be "default DEBUG_KERNEL" but allow itself to be turned off, and then mechanically change the small handful of "#ifdef CONFIG_DEBUG_KERNEL" to "#ifdef

[PATCH v5 2/5] powerpc: Replace CONFIG_DEBUG_KERNEL with CONFIG_DEBUG_MISC

CONFIG_DEBUG_KERNEL should not impact code generation. Use the newly defined CONFIG_DEBUG_MISC instead to keep the current code. Signed-off-by: Sinan Kaya Reviewed-by: Josh Triplett --- arch/powerpc/kernel/sysfs.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

Re: [GIT PULL] Please pull NFS client bugfixes

The pull request you sent on Sat, 13 Apr 2019 14:56:35 +: > git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.1-4 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/b60bc0665e6af8c55b946b67ea8cb235823bb74e Thank you! -- Deet-doot-dot, I am a

Re: [GIT PULL] clk fixes for v5.1-rc4

The pull request you sent on Fri, 12 Apr 2019 16:21:07 -0700: > https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git > tags/clk-fixes-for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/09bad0df3974ef9e682447f48bb7fd55c48513f3 Thank you! --

Re: [GIT PULL] PCI fixes for v5.1

The pull request you sent on Fri, 12 Apr 2019 10:38:38 -0500: > git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git > tags/pci-v5.1-fixes-2 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/a3b84248628df52c39c8724fb69da1ea0f2c0dc7 Thank you! --

Re: [PATCH] new flag COPY_FILE_RANGE_FILESIZE for copy_file_range()

> On Apr 13, 2019, at 1:49 PM, Shawn Landden wrote: > > If flags includes COPY_FILE_RANGE_FILESIZE then the length > copied is the length of the file. off_in and off_out are > ignored. len must be 0 or the file size. > > This implementation saves a call to stat() in the common case > of

Re: Adding plain accesses and detecting data races in the LKMM

On Tue, Apr 09, 2019 at 08:01:32AM -0700, Paul E. McKenney wrote: > On Tue, Apr 09, 2019 at 03:36:18AM +0200, Andrea Parri wrote: > > > > The formula was more along the line of "do not assume either of these > > > > cases to hold; use barrier() is you need an unconditional barrier..." > > > >

[tip:x86/fpu] x86/pkeys: Add PKRU value to init_fpstate

Commit-ID: a5eff7259790d5314eff10563d6e59d358cce482 Gitweb: https://git.kernel.org/tip/a5eff7259790d5314eff10563d6e59d358cce482 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:56 +0200 Committer: Borislav Petkov CommitDate: Fri, 12 Apr 2019 20:21:10 +0200

[tip:x86/fpu] x86/fpu: Restore regs in copy_fpstate_to_sigframe() in order to use the fastpath

Commit-ID: 06b251dff78704c7d122bd109384d970a7dbe94d Gitweb: https://git.kernel.org/tip/06b251dff78704c7d122bd109384d970a7dbe94d Author: Sebastian Andrzej Siewior AuthorDate: Fri, 12 Apr 2019 20:16:15 +0200 Committer: Borislav Petkov CommitDate: Fri, 12 Apr 2019 20:16:15 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Add a fastpath to copy_fpstate_to_sigframe()

Commit-ID: da2f32fb8dc7cbd9433cb2e990693734b30a2465 Gitweb: https://git.kernel.org/tip/da2f32fb8dc7cbd9433cb2e990693734b30a2465 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:54 +0200 Committer: Borislav Petkov CommitDate: Fri, 12 Apr 2019 20:05:36 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Add a fastpath to __fpu__restore_sig()

Commit-ID: 1d731e731c4cd7cbd3b1aa295f0932e7610da82f Gitweb: https://git.kernel.org/tip/1d731e731c4cd7cbd3b1aa295f0932e7610da82f Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:53 +0200 Committer: Borislav Petkov CommitDate: Fri, 12 Apr 2019 20:04:49 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Defer FPU state load until return to userspace

Commit-ID: 5f409e20b794565e2d60ad333e79334630a6c798 Gitweb: https://git.kernel.org/tip/5f409e20b794565e2d60ad333e79334630a6c798 Author: Rik van Riel AuthorDate: Wed, 3 Apr 2019 18:41:52 +0200 Committer: Borislav Petkov CommitDate: Fri, 12 Apr 2019 19:34:47 +0200 x86/fpu: Defer FPU

misuse of fget_raw() in perf_event_get()

What's the point of using fget_raw(), if you do _not_ accept O_PATH descriptors? That should be fget()...

[tip:x86/fpu] x86/fpu: Merge the two code paths in __fpu__restore_sig()

Commit-ID: c2ff9e9a3d9d6c019394a22989a228d02970a8b1 Gitweb: https://git.kernel.org/tip/c2ff9e9a3d9d6c019394a22989a228d02970a8b1 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:51 +0200 Committer: Borislav Petkov CommitDate: Fri, 12 Apr 2019 15:41:25 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Restore from kernel memory on the 64-bit path too

Commit-ID: 926b21f37b072ae4c117052de45a975c6d468fec Gitweb: https://git.kernel.org/tip/926b21f37b072ae4c117052de45a975c6d468fec Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:50 +0200 Committer: Borislav Petkov CommitDate: Fri, 12 Apr 2019 15:02:41 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Inline copy_user_to_fpregs_zeroing()

Commit-ID: e0d3602f933367881bddfff310a744e6e61c284c Gitweb: https://git.kernel.org/tip/e0d3602f933367881bddfff310a744e6e61c284c Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:49 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 20:45:20 +0200 x86/fpu:

[tip:x86/fpu] x86/entry: Add TIF_NEED_FPU_LOAD

Commit-ID: 383c252545edcc708128e2028a2318b05c45ede4 Gitweb: https://git.kernel.org/tip/383c252545edcc708128e2028a2318b05c45ede4 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:45 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 16:21:51 +0200

[tip:x86/fpu] x86/fpu: Update xstate's PKRU value on write_pkru()

Commit-ID: 0d714dba162620fd8b9f5b3104a487e041353c4d Gitweb: https://git.kernel.org/tip/0d714dba162620fd8b9f5b3104a487e041353c4d Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:48 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 20:33:29 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Prepare copy_fpstate_to_sigframe() for TIF_NEED_FPU_LOAD

Commit-ID: a352a3b7b7920212ee4c45a41500c66826318e92 Gitweb: https://git.kernel.org/tip/a352a3b7b7920212ee4c45a41500c66826318e92 Author: Rik van Riel AuthorDate: Wed, 3 Apr 2019 18:41:47 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 18:20:04 +0200 x86/fpu: Prepare

[tip:x86/fpu] x86/fpu: Always store the registers in copy_fpstate_to_sigframe()

Commit-ID: 69277c98f5eef0d9839699b7825923c3985f665f Gitweb: https://git.kernel.org/tip/69277c98f5eef0d9839699b7825923c3985f665f Author: Rik van Riel AuthorDate: Wed, 3 Apr 2019 18:41:46 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 18:08:57 +0200 x86/fpu: Always store

[tip:x86/fpu] x86/fpu: Eager switch PKRU state

Commit-ID: 0cecca9d03c964abbd2b7927d0670eb70db4ebf2 Gitweb: https://git.kernel.org/tip/0cecca9d03c964abbd2b7927d0670eb70db4ebf2 Author: Rik van Riel AuthorDate: Wed, 3 Apr 2019 18:41:44 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 15:57:10 +0200 x86/fpu: Eager switch

[tip:x86/fpu] x86/pkeys: Don't check if PKRU is zero before writing it

Commit-ID: 0556cbdc2fbcb3068e5b924a8b3d5386ae0dd27d Gitweb: https://git.kernel.org/tip/0556cbdc2fbcb3068e5b924a8b3d5386ae0dd27d Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:43 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 15:41:05 +0200

[tip:x86/fpu] x86/fpu: Use a feature number instead of mask in two more helpers

Commit-ID: abd16d68d65229e5acafdadc32704239131bf2ea Gitweb: https://git.kernel.org/tip/abd16d68d65229e5acafdadc32704239131bf2ea Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:40 +0200 Committer: Borislav Petkov CommitDate: Wed, 10 Apr 2019 18:20:27 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Only write PKRU if it is different from current

Commit-ID: 577ff465f5a6a5a0866d75a033844810baca20a0 Gitweb: https://git.kernel.org/tip/577ff465f5a6a5a0866d75a033844810baca20a0 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:42 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 15:41:05 +0200 x86/fpu:

[tip:x86/fpu] x86/pkeys: Provide *pkru() helpers

Commit-ID: c806e88734b9e9aea260bf2261c129aa23968fca Gitweb: https://git.kernel.org/tip/c806e88734b9e9aea260bf2261c129aa23968fca Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:41 +0200 Committer: Borislav Petkov CommitDate: Thu, 11 Apr 2019 15:40:58 +0200

[PATCH] new flag COPY_FILE_RANGE_FILESIZE for copy_file_range()

If flags includes COPY_FILE_RANGE_FILESIZE then the length copied is the length of the file. off_in and off_out are ignored. len must be 0 or the file size. This implementation saves a call to stat() in the common case of copying files. It does not fix any race conditions, but that is possible in

[tip:x86/fpu] x86/fpu: Make __raw_xsave_addr() use a feature number instead of mask

Commit-ID: 07baeb04f37c952981d63359ff840118ce8f5434 Gitweb: https://git.kernel.org/tip/07baeb04f37c952981d63359ff840118ce8f5434 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:39 +0200 Committer: Borislav Petkov CommitDate: Wed, 10 Apr 2019 16:33:45 +0200 x86/fpu:

bug disabling NX (noexec=off)

Hi, Intel Core i3-2120 + kernel-5.0.7 x86_64 from Fedora: [0.00] microcode: microcode updated early to revision 0x2e, date = 2018-04-10 [0.00] Linux version 5.0.7-300.fc30.x86_64 (mockbu...@bkernel04.phx2.fedoraproject.org) (gcc version 9.0.1 20190312 (Red Hat 9.0.1-0.10)

[tip:x86/fpu] x86/fpu: Add an __fpregs_load_activate() internal helper

Commit-ID: 4ee91519e1dccc175665fe24bb20a47c6053575c Gitweb: https://git.kernel.org/tip/4ee91519e1dccc175665fe24bb20a47c6053575c Author: Rik van Riel AuthorDate: Wed, 3 Apr 2019 18:41:38 +0200 Committer: Borislav Petkov CommitDate: Wed, 10 Apr 2019 16:23:14 +0200 x86/fpu: Add an

[tip:x86/fpu] x86/fpu: Remove user_fpu_begin()

Commit-ID: 0169f53e0d97bb675075506810494bd86b8c934e Gitweb: https://git.kernel.org/tip/0169f53e0d97bb675075506810494bd86b8c934e Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:37 +0200 Committer: Borislav Petkov CommitDate: Wed, 10 Apr 2019 15:58:44 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Remove fpu->initialized

Commit-ID: 2722146eb78451b30e4717a267a3a2b44e4ad317 Gitweb: https://git.kernel.org/tip/2722146eb78451b30e4717a267a3a2b44e4ad317 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:36 +0200 Committer: Borislav Petkov CommitDate: Wed, 10 Apr 2019 15:42:40 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Remove fpu->initialized usage in copy_fpstate_to_sigframe()

Commit-ID: fbcc9e0c37ba3186c41b5eb1aee2f7f3b711bc1e Gitweb: https://git.kernel.org/tip/fbcc9e0c37ba3186c41b5eb1aee2f7f3b711bc1e Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:34 +0200 Committer: Borislav Petkov CommitDate: Tue, 9 Apr 2019 20:48:11 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Don't save fxregs for ia32 frames in copy_fpstate_to_sigframe()

Commit-ID: 39388e80f9b0c3788bfb6efe3054bdce0c3ead45 Gitweb: https://git.kernel.org/tip/39388e80f9b0c3788bfb6efe3054bdce0c3ead45 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:35 +0200 Committer: Borislav Petkov CommitDate: Wed, 10 Apr 2019 14:46:35 +0200 x86/fpu:

[PATCH] new flag COPY_FILE_RANGE_FILESIZE for copy_file_range()

If flags includes COPY_FILE_RANGE_FILESIZE then the length copied is the length of the file. off_in and off_out are ignored. len must be 0 or the file size. This implementation saves a call to stat() in the common case of copying files. It does not fix any race conditions, but that is possible in

[tip:x86/fpu] x86/fpu: Always init the state in fpu__clear()

Commit-ID: 88f5260a3bf9bfb276b5b4aac2e81587e425a1d7 Gitweb: https://git.kernel.org/tip/88f5260a3bf9bfb276b5b4aac2e81587e425a1d7 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:33 +0200 Committer: Borislav Petkov CommitDate: Tue, 9 Apr 2019 19:28:06 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Remove preempt_disable() in fpu__clear()

Commit-ID: 60e528d6ce3f60a058bbb64f8acb2a07f84b172a Gitweb: https://git.kernel.org/tip/60e528d6ce3f60a058bbb64f8acb2a07f84b172a Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:32 +0200 Committer: Borislav Petkov CommitDate: Tue, 9 Apr 2019 19:27:46 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Remove fpu__restore()

Commit-ID: 6dd677a044e606fd343e31c2108b13d74aec1ca5 Gitweb: https://git.kernel.org/tip/6dd677a044e606fd343e31c2108b13d74aec1ca5 Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:31 +0200 Committer: Borislav Petkov CommitDate: Tue, 9 Apr 2019 19:27:42 +0200 x86/fpu:

[tip:x86/fpu] x86/fpu: Remove fpu->initialized usage in __fpu__restore_sig()

Commit-ID: 39ea9baffda91df8bfee9b45610242a3191ea1ec Gitweb: https://git.kernel.org/tip/39ea9baffda91df8bfee9b45610242a3191ea1ec Author: Sebastian Andrzej Siewior AuthorDate: Wed, 3 Apr 2019 18:41:30 +0200 Committer: Borislav Petkov CommitDate: Tue, 9 Apr 2019 19:27:29 +0200 x86/fpu:

Re: [PATCH 5/5] leds: lm3697: Introduce the lm3697 driver

On Mon 2019-03-25 09:24:03, Dan Murphy wrote: > Introduce the lm3697 LED driver for > backlighting and display. > > Datasheet location: > http://www.ti.com/lit/ds/symlink/lm3697.pdf > > Signed-off-by: Dan Murphy > --- > drivers/leds/Kconfig | 8 +- > drivers/leds/Makefile | 1 +

Re: [PATCH 1/2] vfs: pass ppos=NULL to .read()/.write() of FMODE_STREAM files

On Sat, Apr 13, 2019 at 10:27:00AM -0700, Linus Torvalds wrote: > On Sat, Apr 13, 2019 at 9:55 AM Kirill Smelkov wrote: > > > > --- a/fs/read_write.c > > +++ b/fs/read_write.c > > @@ -371,7 +371,7 @@ int rw_verify_area(int read_write, struct file *file, > > const loff_t *ppos, size_t > >

Re: [PATCH 0/3] 32-bit Meson: add the canvas module

Hi Martin, On Sat, Apr 13, 2019 at 7:15 PM Martin Blumenstingl wrote: > > This adds the canvas module on Meson8, Meson8b and Meson8m2. The canvas > IP is used by the video decoder hardware as well as the VPU (video > output) hardware. > > Neither the VPU nor the video decoder driver support the

Re: Alleged fix for writer stall on -rcu branch dev

On Sat, Apr 13, 2019 at 07:21:53AM -0700, Paul E. McKenney wrote: > On Wed, Apr 10, 2019 at 05:06:10PM -0700, Paul E. McKenney wrote: > > On Wed, Apr 10, 2019 at 01:33:02PM -0700, Paul E. McKenney wrote: > > > On Wed, Apr 10, 2019 at 09:19:18PM +0200, Sebastian Andrzej Siewior wrote: > > > > On

Re: [GIT PULL] arm64 fixes for -rc5

The pull request you sent on Fri, 12 Apr 2019 17:05:15 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/5ded88718aef7e92a9806f6ff4b89c7f2a4f1570 Thank you! -- Deet-doot-dot, I am

Re: [PATCH 1/2] vfs: pass ppos=NULL to .read()/.write() of FMODE_STREAM files

On Sat, Apr 13, 2019 at 10:27:00AM -0700, Linus Torvalds wrote: > And I'd really like to have people (Al?) look at this and go "yeah, > makes sense". I do think that moving to a model where we wither have a > (properly locked) file position or no pos pointer at all is the right > model (ie I'd

Re: [PATCH 1/2] vfs: pass ppos=NULL to .read()/.write() of FMODE_STREAM files

On Sat, Apr 13, 2019 at 9:55 AM Kirill Smelkov wrote: > > --- a/fs/read_write.c > +++ b/fs/read_write.c > @@ -371,7 +371,7 @@ int rw_verify_area(int read_write, struct file *file, > const loff_t *ppos, size_t > inode = file_inode(file); > if (unlikely((ssize_t) count < 0)) >

[PATCH v4 06/16] locking/rwsem: Code cleanup after files merging

After merging all the relevant rwsem code into one single file, there are a number of optimizations and cleanups that can be done: 1) Remove all the EXPORT_SYMBOL() calls for functions that are not accessed elsewhere. 2) Remove all the __visible tags as none of the functions will be

[PATCH v4 05/16] locking/rwsem: Merge rwsem.h and rwsem-xadd.c into rwsem.c

Now we only have one implementation of rwsem. Even though we still use xadd to handle reader locking, we use cmpxchg for writer instead. So the filename rwsem-xadd.c is not strictly correct. Also no one outside of the rwsem code need to know the internal implementation other than function

Re: [PATCH] pci/switchtec: fix stream_open.cocci warnings (fwd)

Hello everyone, On Sat, Apr 13, 2019 at 06:50:57PM +0200, Julia Lawall wrote: > Hello, > > Kirill will explain about this issue. pci/switchtec switching to stream_open is already queued to merge window and it was acked by Logan Gunthorpe:

[PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

This patch enables readers to optimistically spin on a rwsem when it is owned by a writer instead of going to sleep directly. The rwsem_can_spin_on_owner() function is extracted out of rwsem_optimistic_spin() and is called directly by __rwsem_down_read_failed_common() and

[PATCH v4 10/16] locking/rwsem: Wake up almost all readers in wait queue

When the front of the wait queue is a reader, other readers immediately following the first reader will also be woken up at the same time. However, if there is a writer in between. Those readers behind the writer will not be woken up. Because of optimistic spinning, the lock acquisition order is

[PATCH 2/2] vfs: use >f_pos directly on files that have position

Long ago vfs read/write operations were passing ppos=>f_pos directly to .read / .write file_operations methods. That changed in 2004 in 55f09ec0087c ("read/write: pass down a copy of f_pos, not f_pos itself.") which started to pass ppos=_var trying to avoid simultaneous read/write/lseek stepping

[PATCH 1/2] vfs: pass ppos=NULL to .read()/.write() of FMODE_STREAM files

This amends commit 10dce8af3422 ("fs: stream_open - opener for stream-like files so that read and write can run simultaneously without deadlock") in how position is passed into .read()/.write() handler for stream-like files: Rasmus noticed that we currently pass 0 as position and ignore any

[PATCH v4 09/16] locking/rwsem: Ensure an RT task will not spin on reader

An RT task can do optimistic spinning only if the lock holder is actually running. If the state of the lock holder isn't known, there is a possibility that high priority of the RT task may block forward progress of the lock holder if it happens to reside on the same CPU. This will lead to

[PATCH v4 04/16] locking/rwsem: Implement a new locking scheme

The current way of using various reader, writer and waiting biases in the rwsem code are confusing and hard to understand. I have to reread the rwsem count guide in the rwsem-xadd.c file from time to time to remind myself how this whole thing works. It also makes the rwsem code harder to be

[PATCH v4 15/16] locking/rwsem: Merge owner into count on x86-64

With separate count and owner, there are timing windows where the two values are inconsistent. That can cause problem when trying to figure out the exact state of the rwsem. For instance, a RT task will stop optimistic spinning if the lock is acquired by a writer but the owner field isn't set yet.

[PATCH v4 14/16] locking/rwsem: Guard against making count negative

The upper bits of the count field is used as reader count. When sufficient number of active readers are present, the most significant bit will be set and the count becomes negative. If the number of active readers keep on piling up, we may eventually overflow the reader counts. This is not likely

[PATCH v4 08/16] locking/rwsem: Make rwsem_spin_on_owner() return owner state

This patch modifies rwsem_spin_on_owner() to return four possible values to better reflect the state of lock holder which enables us to make a better decision of what to do next. In the special case that there is no active lock and the handoff bit is set, optimistic spinning has to be stopped.

[PATCH v4 13/16] locking/rwsem: Add more rwsem owner access helpers

Before combining owner and count, we are adding two new helpers for accessing the owner value in the rwsem. 1) struct task_struct *rwsem_get_owner(struct rw_semaphore *sem) 2) bool is_rwsem_reader_owned(struct rw_semaphore *sem) Signed-off-by: Waiman Long --- kernel/locking/rwsem.c | 50

[PATCH v4 16/16] locking/rwsem: Remove redundant computation of writer lock word

On 64-bit architectures, each rwsem writer will have its unique lock word for acquiring the lock. Right now, the writer code recomputes the lock word every time it tries to acquire the lock. This is a waste of time. The lock word is now cached and reused when it is needed. On 32-bit

[PATCH v4 12/16] locking/rwsem: Enable time-based spinning on reader-owned rwsem

When the rwsem is owned by reader, writers stop optimistic spinning simply because there is no easy way to figure out if all the readers are actively running or not. However, there are scenarios where the readers are unlikely to sleep and optimistic spinning can help performance. This patch

[PATCH v4 00/16] locking/rwsem: Rwsem rearchitecture part 2

v4: - Fix the missing initialization bug with !CONFIG_RWSEM_SPIN_ON_OWNER in patch 2. - Move the "Remove rwsem_wake() wakeup optimization" patch before the "Implement a new locking scheme" patch. - Add two new patches to merge the relevant content of rwsem.h and rwsem-xadd.c

[PATCH v4 03/16] locking/rwsem: Remove rwsem_wake() wakeup optimization

With the commit 59aabfc7e959 ("locking/rwsem: Reduce spinlock contention in wakeup after up_read()/up_write()"), the rwsem_wake() forgoes doing a wakeup if the wait_lock cannot be directly acquired and an optimistic spinning locker is present. This can help performance by avoiding spinning on the

[PATCH v4 01/16] locking/rwsem: Prevent unneeded warning during locking selftest

Disable the DEBUG_RWSEMS check when locking selftest is running with debug_locks_silent flag set. Signed-off-by: Waiman Long --- kernel/locking/rwsem.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/kernel/locking/rwsem.h b/kernel/locking/rwsem.h index

[PATCH v4 02/16] locking/rwsem: Make owner available even if !CONFIG_RWSEM_SPIN_ON_OWNER

The owner field in the rw_semaphore structure is used primarily for optimistic spinning. However, identifying the rwsem owner can also be helpful in debugging as well as tracing locking related issues when analyzing crash dump. The owner field may also store state information that can be important

[PATCH v4 07/16] locking/rwsem: Implement lock handoff to prevent lock starvation

Because of writer lock stealing, it is possible that a constant stream of incoming writers will cause a waiting writer or reader to wait indefinitely leading to lock starvation. This patch implements a lock handoff mechanism to disable lock stealing and force lock handoff to the first waiter or

[PATCH 1/3] ARM: dts: meson8: add the canvas module

Add the canvas module to Meson8 because it's required for the VPU (video output) and video decoders. The canvas module is located inside thie "DMC bus" (where also some of the memory controller registers are located). The "DMC bus" itself is part of the so-called "MMC bus". Amlogic's vendor

[PATCH 2/3] ARM: dts: meson8m2: update the offset of the canvas module

With the Meson8m2 SoC the canvas module was moved from offset 0x20 (Meson8) to offset 0x48 (same as on Meson8b). The offsets inside the canvas module are identical. Correct the offset so the driver uses the correct registers. Signed-off-by: Martin Blumenstingl ---

[PATCH 3/3] ARM: dts: meson8b: add the canvas module

Add the canvas module to Meson8b because it's required for the VPU (video output) and video decoders. The canvas module is located inside the "DMC bus" (where also some of the memory controller registers are located). The "DMC bus" itself is part of the so-called "MMC bus". Signed-off-by: Martin

[PATCH 0/3] 32-bit Meson: add the canvas module

This adds the canvas module on Meson8, Meson8b and Meson8m2. The canvas IP is used by the video decoder hardware as well as the VPU (video output) hardware. Neither the VPU nor the video decoder driver support the 32-bit SoCs yet. However, we can still add the canvas module to have it available

Re: [PATCH 1/3] fs: stream_open - opener for stream-like files so that read and write can run simultaneously without deadlock

On Fri, Apr 12, 2019 at 03:41:44PM +0300, Kirill Smelkov wrote: > On Thu, Apr 11, 2019 at 09:22:56AM -0700, Linus Torvalds wrote: > > On Thu, Apr 11, 2019 at 5:38 AM Kirill Smelkov wrote: > > > > > > However file->f_pos writing is still there and it will bug under race > > > detector, e.g. under

Re: [PATCH 1/2] driver core: printk to pr_*

On Fri, 2019-04-12 at 16:47 +0100, Willy Wolff wrote: > Signed-off-by: Willy Wolff Most people seem to prefer some type of commit message before your sign-off. And trivia: > diff --git a/drivers/base/dd.c b/drivers/base/dd.c [] > @@ -602,8 +601,8 @@ static int really_probe_debug(struct device

Re: [PATCH] pci/switchtec: fix stream_open.cocci warnings (fwd)

On 2019-04-13 10:50 a.m., Julia Lawall wrote: > Hello, > > Kirill will explain about this issue. I'm aware of this effort and Acked Kirill's original monolithic patch. So, for this patch: Acked-by: Logan Gunthorpe julia > > -- Forwarded message -- > Date: Sat, 13 Apr 2019

[PATCH] pci/switchtec: fix stream_open.cocci warnings (fwd)

Hello, Kirill will explain about this issue. julia -- Forwarded message -- Date: Sat, 13 Apr 2019 11:22:51 +0800 From: kbuild test robot To: kbu...@01.org Cc: Julia Lawall Subject: [PATCH] pci/switchtec: fix stream_open.cocci warnings CC: kbuild-...@01.org TO: Sebastian

[PATCH 0/3] Meson8b: add support for the RTC on EC-100 and Odroid-C1

This adds support for the RTC on the Meson8b EC-100 and Odroid-C1 boards. Example kernel log snippet while booting my EC-100: [5.713750] meson-rtc c8100740.rtc: setting system clock to 2019-04-13T16:21:48 UTC (1555172508) I am only 99% sure about the naming of the clock in patch 2 and 3.

[PATCH 2/3] ARM: dts: meson8b: ec100: enable the RTC

The RTC is always enabled on this board since the battery is already connected in the factory. According to the schematics the VCC_RTC regulator (which is either powered by the internal 3.3V or a battery) is connected to the 0.9V RTC_VDD input of the SoCs. Signed-off-by: Martin Blumenstingl ---

[PATCH 1/3] ARM: dts: meson: add support for the RTC

The 32-bit Meson SoCs have an RTC block in the AO (always on) area. The RTC requires an external 32.768 kHz oscillator to work properly. Whether or not this crystal exists depends on the board, so it has to be added for each board.dts (instead of adding it somewhere in a generic .dtsi).

[PATCH 3/3] ARM: dts: meson8b: odroid-c1: prepare support for the RTC

The Odroid-C1 has the 32.768 kHz oscillator (X3 in the schematics) which is required for the RTC. A battery can be connected separately (to the BT1 header) - then the "rtc" node can be enabled manually. By default the RTC is disabled because the boards typically come without the RTC battery.

[PATCH 1/1] arm: mm: Export __sync_icache_dcache() for xen-privcmd

This patch avoids ERROR: "__sync_icache_dcache" [drivers/xen/xen-privcmd.ko] undefined! observed when compiling v4.19.34. The xen-privcmd driver, which can be modular, calls set_pte_at() which in turn may call __sync_icache_dcache(). Cc: sta...@vger.kernel.org Signed-off-by: Heinrich Schuchardt

[PATCH] staging: axis-fifo: Add elaborate description in Kconfig

- The Xilinx AXI-Stream FIFO IP core driver description is elaborated. - References: Xilinx PG080 document, axis-fifo.txt Signed-off-by: Moses Christopher --- drivers/staging/axis-fifo/Kconfig | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

Re: [PATCH v3 00/26] Add support for PCIe RC and EP mode in TI's AM654 SoC

On Fri, Apr 12, 2019 at 04:48:36PM +0100, Lorenzo Pieralisi wrote: > On Mon, Mar 25, 2019 at 03:09:21PM +0530, Kishon Vijay Abraham I wrote: > > Add PCIe RC support for TI's AM654 SoC. The PCIe controller in AM654 > > uses Synopsys core revision 4.90a and uses the same TI wrapper as used > > in

Re: [PATCH v2 23/26] PCI: designware-ep: Configure RESBAR to advertise the smallest size

On Mon, Mar 25, 2019 at 02:04:58PM +0530, Kishon Vijay Abraham I wrote: > Configure RESBAR capability to advertise the smallest size (1MB) for > couple of reasons. A) Host side resource allocation of BAR fails for > larger sizes. B) Endpoint function driver does not allocate memory > for all

[PATCH] RDMA/cxgb4: fix null pointer dereference on alloc_skb failure

From: Colin Ian King Currently if alloc_skb fails to allocate the skb a null skb is passed to t4_set_arp_err_handler and this ends up dereferencing the null skb. Avoid the null pointer dereference by checking for a null skb and returning early. Addresses-Coverity: ("Dereference null return")

Re: [PATCH v3 24/26] PCI: designware-ep: Use aligned ATU window for raising MSI interrupts

On Mon, Mar 25, 2019 at 03:09:45PM +0530, Kishon Vijay Abraham I wrote: > Certain platforms like K2G reguires the outbound ATU window to be s/reguires/require/ (note two changes: "g->q" and drop s)

Re: [PATCH v3 20/26] PCI: dwc: Fix dw_pcie_ep_find_capability to return correct capability offset

On Mon, Mar 25, 2019 at 03:09:41PM +0530, Kishon Vijay Abraham I wrote: > commit beb4641a787df79a ("PCI: dwc: Add MSI-X callbacks handler") while > adding MSI-X callback handler, introduced dw_pcie_ep_find_capability and > __dw_pcie_ep_find_next_cap for finding the MSI and MSIX capability. > >

[PATCH v2 2/3] RISC-V: Add interrupt related SCAUSE defines in asm/encoding.h

This patch adds SCAUSE interrupt flag and SCAUSE interrupt cause related defines to asm/encoding.h. We also use these defines in arch/riscv/kernel/irq.c and express SIE/SIP flag in-terms of interrupt causes. Signed-off-by: Anup Patel --- arch/riscv/include/asm/encoding.h | 25

[PATCH v2 3/3] RISC-V: Access CSRs using CSR numbers

We should prefer accessing CSRs using their CSR numbers because: 1. It compiles fine with older toolchains. 2. We can use latest CSR names in #define macro names of CSR numbers as-per RISC-V spec. 3. We can access newly added CSRs even if toolchain does not recognize newly addes CSRs by

  1   2   3   >