[tip:x86/urgent] perf/x86: Always store regs->ip in perf_callchain_kernel()

2019-06-27 Thread tip-bot for Song Liu
Commit-ID: 83f44ae0f8afcc9da659799db8693f74847e66b3 Gitweb: https://git.kernel.org/tip/83f44ae0f8afcc9da659799db8693f74847e66b3 Author: Song Liu AuthorDate: Wed, 26 Jun 2019 19:33:52 -0500 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:11:20 +0200 perf/x86: Always store reg

[tip:x86/urgent] x86/unwind/orc: Fall back to using frame pointers for generated code

2019-06-27 Thread tip-bot for Josh Poimboeuf
Commit-ID: ae6a45a0868986f69039a2150d3b2b9ca294c378 Gitweb: https://git.kernel.org/tip/ae6a45a0868986f69039a2150d3b2b9ca294c378 Author: Josh Poimboeuf AuthorDate: Wed, 26 Jun 2019 19:33:55 -0500 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:11:21 +0200 x86/unwind/orc: Fall

[PATCH] clk: rockchip: Fix -Wunused-const-variable

2019-06-27 Thread Nathan Huckleberry
Clang produces the following warning drivers/clk/rockchip/clk-rv1108.c:125:7: warning: unused variable 'mux_pll_src_3plls_p' [-Wunused-const-variable] PNAME(mux_pll_src_3plls_p) = { "apll", "gpll", "dpll" }; Looks like this variable was never used. Deleting it to remove the warning. Cc: cla

Re: [PATCH 0/2] timekeeping: cleanup _fast_ variety of functions

2019-06-27 Thread Thomas Gleixner
On Tue, 25 Jun 2019, Arnd Bergmann wrote: > On Tue, Jun 25, 2019 at 10:19 AM Jason A. Donenfeld wrote: > > > > When Arnd and I discussed this prior, he thought it best that I separate > > these two commits out into a separate patchset, because they might > > require additional discussion or consid

[GIT PULL rcu/next + tools/memory-model] RCU and LKMM commits for 5.3

2019-06-27 Thread Paul E. McKenney
Hello, Ingo, This pull request contains the following changes: 1. RCU flavor consolidation cleanups and optmizations. http://lkml.kernel.org/r/20190530145204.ga28...@linux.ibm.com 2. Documentation updates. http://lkml.kernel.org/r/20190530145504.ga29...@linux.ibm.com

[PATCH] media: gp8psk: check return value in gp8psk_power_ctrl

2019-06-27 Thread Willem de Bruijn
From: Willem de Bruijn One caller of gp8psk_power_ctrl fails to check the return value. Syzbot KMSAN found a use of uninitialized data. This path is also exercised when no such device exists, as in this cloud environment. Argument status is not set if gp8psk_power_ctrl returns early. Tests its

[tip:x86/entry] selftests/x86: Add a test for process_vm_readv() on the vsyscall page

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: 7f0a5e0755832301e7b010eab46fb715c483ba60 Gitweb: https://git.kernel.org/tip/7f0a5e0755832301e7b010eab46fb715c483ba60 Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:09 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:40 +0200 selftests/x86: Add

Re: [PATCH] ftrace: Remove possible deadlock between register_kprobe() and ftrace_run_update_code()

2019-06-27 Thread Thomas Gleixner
On Thu, 27 Jun 2019, Petr Mladek wrote: > Fortunately, the problematic fix is needed only on x86_64. It is > the only architecture that calls set_all_modules_text_rw() > in ftrace path and supports livepatching at the same time. > > Therefore it is enough to move text_mutex handling from the gener

[tip:x86/entry] x86/vsyscall: Add __ro_after_init to global variables

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: 441cedab2dfca18fe4983cbc795de04536ed421e Gitweb: https://git.kernel.org/tip/441cedab2dfca18fe4983cbc795de04536ed421e Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:08 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:40 +0200 x86/vsyscall: Add _

[tip:x86/entry] x86/vsyscall: Change the default vsyscall mode to xonly

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: 625b7b7f79c66626fb2b7687fc1a58309a57edd5 Gitweb: https://git.kernel.org/tip/625b7b7f79c66626fb2b7687fc1a58309a57edd5 Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:07 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:39 +0200 x86/vsyscall: Chang

[tip:x86/entry] selftests/x86/vsyscall: Verify that vsyscall=none blocks execution

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: b0386979867168575118501104f3d135067eab4f Gitweb: https://git.kernel.org/tip/b0386979867168575118501104f3d135067eab4f Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:06 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:39 +0200 selftests/x86/vsysc

[PATCH] clk: mediatek: Fix -Wunused-const-variable

2019-06-27 Thread Nathan Huckleberry
Clang produces the following warning drivers/clk/mediatek/clk-mt8516.c:234:27: warning: unused variable 'ddrphycfg_parents' [-Wunused-const-variable] static const char * const ddrphycfg_parents[] __initconst = { This variable has never been used. Deleting it to cleanup the warning. Cc: clang-bui

[tip:x86/entry] x86/vsyscall: Document odd SIGSEGV error code for vsyscalls

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: e0a446ce394a7915f2ffc03f9bb610c5ac4dbbf1 Gitweb: https://git.kernel.org/tip/e0a446ce394a7915f2ffc03f9bb610c5ac4dbbf1 Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:05 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:39 +0200 x86/vsyscall: Docum

Re: [PATCH] platform/chrome: lightbar: Get drvdata from parent in suspend/resume

2019-06-27 Thread Gwendal Grignou
Reviewed-by: Gwendal Grignou On Thu, Jun 27, 2019 at 2:47 PM Rajat Jain wrote: > > The lightbar driver never assigned the drvdata in probe method, and > thus there is nothing there. Need to get the ec_dev from the parent's > drvdata. > > Signed-off-by: Rajat Jain > --- > drivers/platform/chro

[tip:x86/entry] x86/vsyscall: Add a new vsyscall=xonly mode

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: bd49e16e3339f052fae05fb3e955c5db0c9c6445 Gitweb: https://git.kernel.org/tip/bd49e16e3339f052fae05fb3e955c5db0c9c6445 Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:03 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:38 +0200 x86/vsyscall: Add a

Re: [RFC PATCH bpf-next v2 0/6] bpf: add BPF_MAP_DUMP command to

2019-06-27 Thread Alexei Starovoitov
On Thu, Jun 27, 2019 at 01:24:11PM -0700, Brian Vazquez wrote: > This introduces a new command to retrieve a variable number of entries > from a bpf map. > > This new command can be executed from the existing BPF syscall as > follows: > > err = bpf(BPF_MAP_DUMP, union bpf_attr *attr, u32 size) >

[tip:x86/entry] x86/vsyscall: Show something useful on a read fault

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: 918ce325098a4eef99daad7b6796da33cebaf03a Gitweb: https://git.kernel.org/tip/918ce325098a4eef99daad7b6796da33cebaf03a Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:04 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:39 +0200 x86/vsyscall: Show

[tip:x86/entry] Documentation/admin: Remove the vsyscall=native documentation

2019-06-27 Thread tip-bot for Andy Lutomirski
Commit-ID: d974ffcfb7447db5f29a4b662a3eaf99a4e1109e Gitweb: https://git.kernel.org/tip/d974ffcfb7447db5f29a4b662a3eaf99a4e1109e Author: Andy Lutomirski AuthorDate: Wed, 26 Jun 2019 21:45:02 -0700 Committer: Thomas Gleixner CommitDate: Fri, 28 Jun 2019 00:04:38 +0200 Documentation/admin

Re: [RFC PATCH bpf-next v2 2/6] bpf: add BPF_MAP_DUMP command to access more than one entry per call

2019-06-27 Thread Alexei Starovoitov
On Thu, Jun 27, 2019 at 01:24:13PM -0700, Brian Vazquez wrote: > This introduces a new command to retrieve a variable number of entries > from a bpf map wrapping the existing bpf methods: > map_get_next_key and map_lookup_elem > > Note that map_dump doesn't guarantee that reading the entire table

Re: [PATCH 8/9] keys: Network namespace domain tag [ver #4]

2019-06-27 Thread David Howells
Willem de Bruijn wrote: > > +#ifdef CONFIG_KEYS > > +out_free_2: > > + kmem_cache_free(net_cachep, net); > > needs > net = NULL; > > to signal failure > > > +#endif I've folded that into the patch and retagged, remerged and repushed. David

[PATCH] clk: qoriq: Fix -Wunused-const-variable

2019-06-27 Thread Nathan Huckleberry
drivers/clk/clk-qoriq.c:138:38: warning: unused variable 'p5020_cmux_grp1' [-Wunused-const-variable] static const struct clockgen_muxinfo p5020_cmux_grp1 drivers/clk/clk-qoriq.c:146:38: warning: unused variable 'p5020_cmux_grp2' [-Wunused-const-variable] static const struct clockgen_muxinfo p5020_

Re: [PATCH bpf v5 2/2] xdp: fix hang while unregistering device bound to xdp socket

2019-06-27 Thread Jonathan Lemon
On 27 Jun 2019, at 3:15, Ilya Maximets wrote: Device that bound to XDP socket will not have zero refcount until the userspace application will not close it. This leads to hang inside 'netdev_wait_allrefs()' if device unregistering requested: # ip link del p1 < hang on recvmsg on netlink soc

Re: [PATCH bpf v5 1/2] xdp: hold device for umem regardless of zero-copy mode

2019-06-27 Thread Jonathan Lemon
On 27 Jun 2019, at 3:15, Ilya Maximets wrote: Device pointer stored in umem regardless of zero-copy mode, so we heed to hold the device in all cases. Fixes: c9b47cc1fabc ("xsk: fix bug when trying to use both copy and zero-copy on one queue id") Signed-off-by: Ilya Maximets Acked-by: Jonat

Re: WARNING in mark_lock

2019-06-27 Thread syzbot
syzbot has bisected this bug to: commit e9db4ef6bf4ca9894bb324c76e01b8f1a16b2650 Author: John Fastabend Date: Sat Jun 30 13:17:47 2018 + bpf: sockhash fix omitted bucket lock in sock_close bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1436e7e9a0 start commit: dc6

Re: [PATCH v4 net-next 1/4] net: core: page_pool: add user cnt preventing pool deletion

2019-06-27 Thread Ivan Khoronzhuk
Hi Jesper, thanks you remember about it. I don't think that "create" and "free" routines paring looks "more correct" together. Maybe we can scale back your solution(?), via creating a page_pool_get() and page_pool_put() API that can be used by your driver, to keep the page_pool object after a

Re: [PATCH 2/2] powercap/rapl: Add Ice Lake NNPI support to RAPL driver

2019-06-27 Thread Rafael J. Wysocki
On Friday, June 14, 2019 10:05:23 AM CEST Rajneesh Bhardwaj wrote: > Enables support for ICL-NNPI, which is a neural network processor for deep > learning inference. From RAPL point of view it is same as Ice Lake Mobile > processor. > > Cc: "Rafael J. Wysocki" > Cc: linux...@vger.kernel.org > Lin

Re: [PATCH] cpufreq: pcc-cpufreq: Fail initialization if driver cannot be registered

2019-06-27 Thread Rafael J. Wysocki
On Friday, June 7, 2019 5:05:46 AM CEST Viresh Kumar wrote: > On 06-06-19, 14:50, David Arcari wrote: > > Make pcc_cpufreq_init() return error codes when the driver cannot be > > registered. Otherwise the driver can shows up loaded via lsmod even > > though it failed initialization. This is confu

Re: [PATCH v2] powerpc/power: Expose pfn_is_nosave prototype

2019-06-27 Thread Rafael J. Wysocki
On Friday, May 24, 2019 12:44:18 PM CEST Mathieu Malaterre wrote: > The declaration for pfn_is_nosave is only available in > kernel/power/power.h. Since this function can be override in arch, > expose it globally. Having a prototype will make sure to avoid warning > (sometime treated as error with

Re: [PATCH 1/2] iio: common: cros_ec_sensors: determine protocol version

2019-06-27 Thread Gwendal Grignou
On Thu, Jun 27, 2019 at 8:59 AM Enric Balletbo i Serra wrote: > > Hi, > > cc'ing Doug, Gwendal and Enrico that might be interested to give a review. > > This patch can be picked alone without 2/2, an is needed to have > cros-ec-sensors > legacy support on ARM (see [1] and [2]) > > Jonathan, as [1

Re: [GIT PULL] cpupower update for Linux 5.2-rc6

2019-06-27 Thread Rafael J. Wysocki
On Wednesday, June 12, 2019 10:27:03 PM CEST Shuah Khan wrote: > This is a multi-part message in MIME format. > --DA1BC82BAC95C219E9AB2661 > Content-Type: text/plain; charset=utf-8; format=flowed > Content-Transfer-Encoding: 7bit > > Hi Rafael, > > Please pull the following update fo

[tip:x86/pti] x86/tls: Fix possible spectre-v1 in do_get_thread_area()

2019-06-27 Thread tip-bot for Dianzhang Chen
Commit-ID: 993773d11d45c90cb1c6481c2638c3d9f092ea5b Gitweb: https://git.kernel.org/tip/993773d11d45c90cb1c6481c2638c3d9f092ea5b Author: Dianzhang Chen AuthorDate: Wed, 26 Jun 2019 12:50:30 +0800 Committer: Thomas Gleixner CommitDate: Thu, 27 Jun 2019 23:48:04 +0200 x86/tls: Fix possibl

Re: [PATCH V2 3/5] cpufreq: Use has_target() instead of !setpolicy

2019-06-27 Thread Rafael J. Wysocki
On Thursday, June 20, 2019 5:05:48 AM CEST Viresh Kumar wrote: > For code consistency, use has_target() instead of !setpolicy everywhere, > as it is already done at several places. Maybe we should also use > "!has_target()" instead of "cpufreq_driver->setpolicy" where we need to > check if the driv

Re: [PATCH V2 1/5] cpufreq: Remove the redundant !setpolicy check

2019-06-27 Thread Rafael J. Wysocki
On Thursday, June 20, 2019 5:05:46 AM CEST Viresh Kumar wrote: > cpufreq_start_governor() is only called for !setpolicy case, checking it > again is not required. > > Signed-off-by: Viresh Kumar > --- > drivers/cpufreq/cpufreq.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff -

[tip:x86/pti] x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()

2019-06-27 Thread tip-bot for Dianzhang Chen
Commit-ID: 31a2fbb390fee4231281b939e1979e810f945415 Gitweb: https://git.kernel.org/tip/31a2fbb390fee4231281b939e1979e810f945415 Author: Dianzhang Chen AuthorDate: Tue, 25 Jun 2019 23:30:17 +0800 Committer: Thomas Gleixner CommitDate: Thu, 27 Jun 2019 23:48:04 +0200 x86/ptrace: Fix poss

[PATCH] platform/chrome: lightbar: Get drvdata from parent in suspend/resume

2019-06-27 Thread Rajat Jain
The lightbar driver never assigned the drvdata in probe method, and thus there is nothing there. Need to get the ec_dev from the parent's drvdata. Signed-off-by: Rajat Jain --- drivers/platform/chrome/cros_ec_lightbar.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/driv

Re: [PATCH v2, resend] device property: Add helpers to count items in an array

2019-06-27 Thread Rafael J. Wysocki
On Thursday, June 13, 2019 6:59:51 PM CEST Andy Shevchenko wrote: > The usual pattern to allocate the necessary space for an array of properties > is > to count them first by calling: > > count = device_property_read_uXX_array(dev, propname, NULL, 0); > if (count < 0) > return count; >

Re: [PATCH] perf cgroups: Don't rotate events for cgroups unnecessarily

2019-06-27 Thread Ian Rogers
group_index On Mon, Jun 24, 2019 at 12:55 AM Peter Zijlstra wrote: > > On Fri, Jun 21, 2019 at 11:01:29AM -0700, Ian Rogers wrote: > > On Fri, Jun 21, 2019 at 1:24 AM Peter Zijlstra wrote: > > > > > > On Sat, Jun 01, 2019 at 01:27:22AM -0700, Ian Rogers wrote: > > > > @@ -3325,6 +3331,15 @@ stati

Re: [PATCH 07/13] xfs: allow merging ioends over append boundaries

2019-06-27 Thread Luis Chamberlain
On Thu, Jun 27, 2019 at 11:23:09AM -0700, Darrick J. Wong wrote: > On Thu, Jun 27, 2019 at 12:48:30PM +0200, Christoph Hellwig wrote: > > There is no real problem merging ioends that go beyond i_size into an > > ioend that doesn't. We just need to move the append transaction to the > > base ioend.

Re: [PATCH] platform/chrome: lightbar: Assign drvdata during probe

2019-06-27 Thread Rajat Jain
Hi Enric, On Wed, Jun 26, 2019 at 1:34 PM Enric Balletbo i Serra wrote: > > Hi Rajat, > > On 25/6/19 22:51, Rajat Jain wrote: > > The lightbar driver never assigned the drvdata in probe method, and thus > > causes a panic when it is accessed at the suspend time. > > Good catch, that's one of the

Re: [PATCH v3 2/5] x86: hv: hv_init.c: Add functions to allocate/deallocate page for Hyper-V

2019-06-27 Thread Thomas Gleixner
Maya, On Tue, 18 Jun 2019, Maya Nakamura wrote: > diff --git a/arch/x86/hyperv/hv_init.c b/arch/x86/hyperv/hv_init.c > index 0e033ef11a9f..e8960a83add7 100644 > --- a/arch/x86/hyperv/hv_init.c > +++ b/arch/x86/hyperv/hv_init.c > @@ -37,6 +37,20 @@ EXPORT_SYMBOL_GPL(hyperv_pcpu_input_arg); > u32

[PATCH] ARM: mm: only adjust sections of valid mm structures

2019-06-27 Thread Doug Berger
A timing hazard exists when an early fork/exec thread begins exiting and sets its mm pointer to NULL while a separate core tries to update the section information. This commit ensures that the mm pointer is not NULL before setting its section parameters. The arguments provided by commit 11ce4b33ae

Re: [PATCH V4 1/3] cpufreq: Move the IS_ENABLED(CPU_THERMAL) macro in a stub

2019-06-27 Thread Rafael J. Wysocki
On Thu, Jun 27, 2019 at 11:02 PM Daniel Lezcano wrote: > > The cpufreq_online and the cpufreq_offline [un]register the driver as > a cooling device. This is done if the driver is flagged as a cooling > device in addition with a IS_ENABLED macro to compile out the branching > code. > > Group this t

Re: [PATCH] kbuild: Add ability to test Clang's integrated assembler

2019-06-27 Thread Nick Desaulniers
On Thu, Jun 27, 2019 at 12:15 PM Nathan Chancellor wrote: > > There are some people interested in experimenting with Clang's > integrated assembler. To make it easy to do so without source > modification, allow the user to specify 'AS=clang' as part of the > make command to avoid adding '-no-integ

[PATCH] .gitignore: ignore *.rej files

2019-06-27 Thread Nick Desaulniers
Such as those produced by the `patch` utility. We already ignore *.orig files, and there are currently no *.rej files in the tree at this time. Signed-off-by: Nick Desaulniers --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 7587ef56b92d..f97430cb2

Re: [PATCH 2/2] mm, slab: Extend vm/drop_caches to shrink kmem slabs

2019-06-27 Thread Roman Gushchin
On Thu, Jun 27, 2019 at 04:57:50PM -0400, Waiman Long wrote: > On 6/26/19 4:19 PM, Roman Gushchin wrote: > >> > >> +#ifdef CONFIG_MEMCG_KMEM > >> +static void kmem_cache_shrink_memcg(struct mem_cgroup *memcg, > >> + void __maybe_unused *arg) > >> +{ > >> + struct kme

Re: [PATCH RESEND] Revert "x86/paravirt: Set up the virt_spin_lock_key after static keys get initialized"

2019-06-27 Thread Thomas Gleixner
On Wed, 26 Jun 2019, Zhenzhong Duan wrote: > This reverts commit ca5d376e17072c1b60c3fee66f3be58ef018952d. > > Commit 8990cac6e5ea ("x86/jump_label: Initialize static branching > early") adds jump_label_init() call in setup_arch() to make static > keys initialized early, so we could use the origi

Re: linux-next: manual merge of the nand tree with Linus' tree

2019-06-27 Thread Miquel Raynal
Hi Stephen, Miquel Raynal wrote on Thu, 27 Jun 2019 16:51:37 +0200: > Hi Stephen, > > Stephen Rothwell wrote on Tue, 4 Jun 2019 > 10:54:18 +1000: > > > Hi all, > > > > Today's linux-next merge of the nand tree got a conflict in: > > > > Documentation/devicetree/bindings/mtd/brcm,brcmnand.

power9 NUMA crash while reading debugfs imc_cmd

2019-06-27 Thread Qian Cai
mdio ahci libahci tg3 libphy libata firmware_class dm_mirror dm_region_hash dm_log dm_mod [ 1139.415595][ T5301] CPU: 67 PID: 5301 Comm: cat Not tainted 5.2.0-rc6-next- 20190627+ #19 [ 1139.415634][ T5301] NIP:  c00d0d58 LR: c049aa18 CTR: c00d0d50 [ 1139.415675][ T5301]

Re: [PATCH v3] platform/chrome: Expose resume result via debugfs

2019-06-27 Thread Enric Balletbo Serra
Hi Evan, Lee, Missatge de Evan Green del dia dj., 27 de juny 2019 a les 22:46: > > For ECs that support it, the EC returns the number of slp_s0 > transitions and whether or not there was a timeout in the resume > response. Expose the last resume result to usermode via debugfs so > that usermode c

[PATCH v3 05/22] PM / devfreq: tegra30: Set up watermarks properly

2019-06-27 Thread Dmitry Osipenko
The current implementation is inaccurate and results in very intensive interrupt activity, which neglects the whole idea of polling offload to hardware. The reason of the shortcoming is that watermarks are not set up correctly and this results in ACTMON constantly asking to change freq and then the

[PATCH v3 00/22] More improvements for Tegra30 devfreq driver

2019-06-27 Thread Dmitry Osipenko
Hello, This series addresses some additional review comments that were made by Thierry Reding to [1] and makes several important changes to the driver, fixing excessive interrupts activity. In the end I'm proposing myself as a maintainer for the Tegra devfreq drivers. [1] https://lore.kernel.org

[PATCH v3 06/22] PM / devfreq: tegra30: Tune up boosting thresholds

2019-06-27 Thread Dmitry Osipenko
Now that average-sustain coefficient / multiplier is gone, it won't hurt to re-tune the boosting thresholds to get a bit harder boosting for MCALL clients, resulting in a more reactive governing in a case of multimedia applications usage like 3d / video. Signed-off-by: Dmitry Osipenko --- driver

[PATCH v3 07/22] PM / devfreq: tegra30: Use CPUFreq notifier

2019-06-27 Thread Dmitry Osipenko
The CPU's client need to take into account that CPUFreq may change while memory activity not, staying high. Thus an appropriate frequency notifier should be used in addition to the clk-notifier. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 105 +-

Re: your mail

2019-06-27 Thread Tejun Heo
On Wed, Jun 26, 2019 at 04:52:36PM +0200, Sebastian Andrzej Siewior wrote: > A small series of tiny cleanups. Applied 1-2 to wq/for-5.3. Thanks. -- tejun

[PATCH v3 04/22] PM / devfreq: tegra30: Drop write-barrier

2019-06-27 Thread Dmitry Osipenko
There is no need in a write-barrier now, given that interrupt masking is handled by CPU's GIC now. Hence we know exactly that interrupt won't fire after stopping the devfreq's governor. In other cases we don't care about potential buffering of the writes to hardware and thus there is no need to sta

[PATCH v3 09/22] PM / devfreq: tegra30: Reset boosting on startup

2019-06-27 Thread Dmitry Osipenko
Governor could be stopped while boosting is active. We have assumption that everything is reset on governor's restart, including the boosting value, which was missed. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drive

[PATCH v3 08/22] PM / devfreq: tegra30: Move clk-notifier's registration to governor's start

2019-06-27 Thread Dmitry Osipenko
There is no point in receiving of the notifications while governor is stopped, let's keep them disabled like we do for the CPU freq-change notifications. This also fixes a potential use-after-free bug if notification happens after device's removal. Signed-off-by: Dmitry Osipenko --- drivers/devf

[PATCH v3 12/22] PM / devfreq: tegra30: Inline all one-line functions

2019-06-27 Thread Dmitry Osipenko
Depending on a kernel's configuration, a single line functions may not be inlined by compiler (like enabled ftracing for example). Let's inline such functions explicitly for consistency. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 13 +++-- 1 file changed, 7 in

[PATCH v3 02/22] PM / devfreq: tegra30: Keep interrupt disabled while governor is stopped

2019-06-27 Thread Dmitry Osipenko
There is no real need to keep interrupt always-enabled, will be nicer to keep it disabled while governor is inactive. Suggested-by: Thierry Reding Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 43 --- 1 file changed, 22 insertions(+), 21 dele

[PATCH v3 20/22] PM / devfreq: tegra30: Optimize upper average watermark selection

2019-06-27 Thread Dmitry Osipenko
I noticed that CPU may be crossing the dependency threshold very frequently for some workloads and this results in a lot of interrupts which could be avoided if MCALL client is keeping actual EMC frequency at a higher rate. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 2

[PATCH v3 15/22] PM / devfreq: tegra30: Fix integer overflow on CPU's freq max out

2019-06-27 Thread Dmitry Osipenko
There is another kHz-conversion bug in the code, resulting in integer overflow. Although, this time the resulting value is 4294966296 and it's close to ULONG_MAX, which is okay in this case. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 2 +- 1 file changed, 1 insertion(

[PATCH v3 13/22] PM / devfreq: tegra30: Constify structs

2019-06-27 Thread Dmitry Osipenko
Constify unmodifiable structs for consistency. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/devfreq/tegra30-devfreq.c b/drivers/devfreq/tegra30-devfreq.c index ecbd58504cd8..d3e117d827d2 10

[PATCH v3 22/22] PM / devfreq: tegra20/30: Add Dmitry as a maintainer

2019-06-27 Thread Dmitry Osipenko
I was contributing to the NVIDIA Tegra20+ devfreq drivers recently and want to help keep them working and evolving in the future. Signed-off-by: Dmitry Osipenko --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 792d2d927712..bfd827417a27

[PATCH v3 17/22] PM / devfreq: tegra30: Use tracepoints for debugging

2019-06-27 Thread Dmitry Osipenko
Debug messages create too much CPU and memory activity by themselves, so it's difficult to debug lower rates and catch unwanted interrupts that happen rarely. Tracepoints are ideal in that regards because they do not contribute to the sampled date at all. This allowed me to catch few problems which

[PATCH v3 14/22] PM / devfreq: tegra30: Ensure that target freq won't overflow

2019-06-27 Thread Dmitry Osipenko
Potentially very high boosting could cause an integer overflow for a highly clocked memory after conversion to MHz. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/devfreq/tegra30-devfreq.c b/drivers/devfreq/tegra3

[PATCH v3 21/22] PM / devfreq: tegra30: Include appropriate header

2019-06-27 Thread Dmitry Osipenko
It's not very correct to include mod_devicetable.h for the OF device drivers and of_device.h should be included instead. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/devfreq/tegra30-devfreq.c b/d

[PATCH v3 10/22] PM / devfreq: tegra30: Don't enable consecutive-down interrupt on startup

2019-06-27 Thread Dmitry Osipenko
The consecutive-down event tells that we should perform frequency de-boosting, but boosting is in a reset state on start and hence the event won't do anything useful for us and it will be just a dummy interrupt request. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 1 -

[PATCH v3 18/22] PM / devfreq: tegra30: Optimize CPUFreq notifier

2019-06-27 Thread Dmitry Osipenko
When CPU's memory activity is low or memory activity is high such that CPU's frequency contribution to the boosting is not taken into account, then there is no need to schedule devfreq's update. This eliminates unnecessary CPU activity during of idling caused by the scheduled work. Signed-off-by:

[PATCH v3 03/22] PM / devfreq: tegra30: Handle possible round-rate error

2019-06-27 Thread Dmitry Osipenko
The EMC clock rate rounding technically could fail, hence let's handle the error cases properly. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 17 +++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/drivers/devfreq/tegra30-devfreq.c b/driver

[PATCH v3 11/22] PM / devfreq: tegra30: Add debug messages

2019-06-27 Thread Dmitry Osipenko
Add debug messages to know about what's happening in hardware and how driver reacts. Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 35 +++ 1 file changed, 35 insertions(+) diff --git a/drivers/devfreq/tegra30-devfreq.c b/drivers/devfreq/tegr

[PATCH v3 19/22] PM / devfreq: tegra30: Optimize upper consecutive watermark selection

2019-06-27 Thread Dmitry Osipenko
The memory activity counter may get a bit higher than a watermark which is selected based on OPP that corresponds to a highest EMC rate, in this case watermark is lower than the actual memory activity is and thus results in unwanted "upper" interrupts. Signed-off-by: Dmitry Osipenko --- drivers/

[PATCH v3 16/22] PM / devfreq: tegra30: Use kHz units uniformly in the code

2019-06-27 Thread Dmitry Osipenko
Now that all kHz-conversion related bugs are fixed, we can use the kHz uniformly. This makes code cleaner and avoids integer divisions in the code, which is useful in a case of Tegra30 that has Cortex A9 CPU that doesn't support integer division instructions, hence all divisions are actually made i

[PATCH v3 01/22] PM / devfreq: tegra30: Change irq type to unsigned int

2019-06-27 Thread Dmitry Osipenko
IRQ numbers are always positive, hence the corresponding variable should be unsigned to keep types consistent. This is a minor change that cleans up code a tad more. Suggested-by: Thierry Reding Acked-by: MyungJoo Ham Signed-off-by: Dmitry Osipenko --- drivers/devfreq/tegra30-devfreq.c | 8 +++

Re: [PATCH v2] timer: document TIMER_PINNED

2019-06-27 Thread Thomas Gleixner
On Thu, 27 Jun 2019, Peter Xu wrote: > + * @TIMER_PINNED: A pinned timer will not be affected by any timer > + * placement heuristics (like, NOHZ) and will always be run on the CPU > + * when the timer was enqueued. s/when/on which/ > + * > + * Note: Because enqueuing of timers can actually migra

Re: [PATCH v3] clk: Add Si5341/Si5340 driver

2019-06-27 Thread Stephen Boyd
Quoting Mike Looijmans (2019-05-17 06:23:52) > Adds a driver for the Si5341 and Si5340 chips. The driver does not fully > support all features of these chips, but allows the chip to be used > without any support from the "clockbuilder pro" software. > > If the chip is preprogrammed, that is, you b

[PATCH V4 3/3] thermal/drivers/cpu_cooling: cpufreq_cooling_register returns an int

2019-06-27 Thread Daniel Lezcano
It looks like after the changes in the patch the only reason for returning (struct thermal_cooling_device *) from cpufreq_cooling_register() is error checking, but it would be much more straightforward to return int for this purpose. Moreover, that would prevent the callers of it from doing incorr

[PATCH V4 2/3] thermal/drivers/cpu_cooling: Unregister with the policy

2019-06-27 Thread Daniel Lezcano
Currently the function cpufreq_cooling_register() returns a cooling device pointer which is used back as a pointer to call the function cpufreq_cooling_unregister(). Even if it is correct, it would make sense to not leak the structure inside a cpufreq driver and keep the code thermal code self-enca

[PATCH V4 1/3] cpufreq: Move the IS_ENABLED(CPU_THERMAL) macro in a stub

2019-06-27 Thread Daniel Lezcano
The cpufreq_online and the cpufreq_offline [un]register the driver as a cooling device. This is done if the driver is flagged as a cooling device in addition with a IS_ENABLED macro to compile out the branching code. Group this test in a stub function added in the cpufreq header instead of having

Re: [PATCH] memcg: Add kmem.slabinfo to v2 for debugging purpose

2019-06-27 Thread Waiman Long
On 6/27/19 10:20 AM, Tejun Heo wrote: > Hello, Waiman. > > On Wed, Jun 26, 2019 at 12:56:14PM -0400, Waiman Long wrote: >> With memory cgroup v1, there is a kmem.slabinfo file that can be >> used to view what slabs are allocated to the memory cgroup. There >> is currently no such equivalent in memo

Re: [PATCH v3] dt-bindings: clock: Add silabs,si5341

2019-06-27 Thread Stephen Boyd
Quoting Mike Looijmans (2019-05-17 06:20:20) > Adds the devicetree bindings for the Si5341 and Si5340 chips from > Silicon Labs. These are multiple-input multiple-output clock > synthesizers. > > Signed-off-by: Mike Looijmans > > --- Applied to clk-next

Re: [PATCH v2] rcu: Change return type of rcu_spawn_one_boost_kthread()

2019-06-27 Thread Paul E. McKenney
On Thu, Jun 27, 2019 at 09:42:40AM -0400, Joel Fernandes wrote: > On Thu, Jun 27, 2019 at 04:07:46PM +0900, Byungchul Park wrote: > > Hello, > > > > I tested if the WARN_ON_ONCE() is fired with my box and it was ok. > > Looks pretty safe to me and nice clean up! > > Acked-by: Joel Fernandes (Goo

Re: [PATCH 8/9] keys: Network namespace domain tag [ver #4]

2019-06-27 Thread Willem de Bruijn
On Wed, Jun 19, 2019 at 12:49 PM David Howells wrote: > > Create key domain tags for network namespaces and make it possible to > automatically tag keys that are used by networked services (e.g. AF_RXRPC, > AFS, DNS) with the default network namespace if not set by the caller. > > This allows keys

Re: [PATCH] dt-bindings: Add silabs,si5341

2019-06-27 Thread Stephen Boyd
Quoting Mike Looijmans (2019-06-27 04:38:16) > On 26-06-19 23:24, Stephen Boyd wrote: > > Sorry, I'm getting through my inbox pile and saw this one. > > > > Quoting Mike Looijmans (2019-04-30 22:46:55) > >> On 30-04-19 02:17, Stephen Boyd wrote: > >>> > >>> Why can't that driver call clk_prepare_e

Re: [PATCH] clk: clk-si544: Implement small frequency change support

2019-06-27 Thread Stephen Boyd
Quoting Mike Looijmans (2019-05-07 06:51:10) > The Si544 supports changing frequencies "on the fly" when the change is > less than 950 ppm from the current center frequency. The driver now > uses the small adjustment routine for implementing this. > > Signed-off-by: Mike Looijmans > --- Applied

Re: [RFC PATCH RT 4/4] rcutorture: Avoid problematic critical section nesting

2019-06-27 Thread Paul E. McKenney
On Thu, Jun 27, 2019 at 03:16:09PM -0500, Scott Wood wrote: > On Thu, 2019-06-27 at 11:00 -0700, Paul E. McKenney wrote: > > On Wed, Jun 26, 2019 at 11:49:16AM -0500, Scott Wood wrote: > > > On Wed, 2019-06-26 at 11:08 -0400, Steven Rostedt wrote: > > > > On Fri, 21 Jun 2019 16:59:55 -0700 > > > >

Re: [PATCH 01/13] list.h: add list_pop and list_pop_entry helpers

2019-06-27 Thread Darrick J. Wong
On Thu, Jun 27, 2019 at 12:48:24PM +0200, Christoph Hellwig wrote: > We have a very common pattern where we want to delete the first entry > from a list and return it as the properly typed container structure. > > Add two helpers to implement this behavior. > > Signed-off-by: Christoph Hellwig

Re: [RFC] Deadlock via recursive wakeup via RCU with threadirqs

2019-06-27 Thread Paul E. McKenney
On Thu, Jun 27, 2019 at 11:30:22AM -0700, Paul E. McKenney wrote: > On Thu, Jun 27, 2019 at 11:11:12AM -0700, Paul E. McKenney wrote: > > On Thu, Jun 27, 2019 at 01:46:27PM -0400, Joel Fernandes wrote: > > > On Thu, Jun 27, 2019 at 1:43 PM Joel Fernandes > > > wrote: > > > > > > > > On Thu, Jun 2

Re: [PATCH 04/13] xfs: initialize iomap->flags in xfs_bmbt_to_iomap

2019-06-27 Thread Darrick J. Wong
On Thu, Jun 27, 2019 at 12:48:27PM +0200, Christoph Hellwig wrote: > Currently we don't overwrite the flags field in the iomap in > xfs_bmbt_to_iomap. This works fine with 0-initialized iomaps on stack, > but is harmful once we want to be able to reuse an iomap in the > writeback code. Replace th

[PATCH v3] platform/chrome: Expose resume result via debugfs

2019-06-27 Thread Evan Green
For ECs that support it, the EC returns the number of slp_s0 transitions and whether or not there was a timeout in the resume response. Expose the last resume result to usermode via debugfs so that usermode can detect and report S0ix timeouts. Signed-off-by: Evan Green --- Changes in v3: - Expo

[PATCH 1/5] cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages

2019-06-27 Thread Tejun Heo
btrfs is going to use css_put() and wbc helpers to improve cgroup writeback support. Add dummy css_get() definition and export wbc helpers to prepare for module and !CONFIG_CGROUP builds. Signed-off-by: Tejun Heo Reported-by: kbuild test robot Reviewed-by: Jan Kara --- block/blk-cgroup.c

Re: [PATCH 0/2] Speed MTRR programming up when we can

2019-06-27 Thread Thomas Gleixner
On Thu, 27 Jun 2019, Ricardo Neri wrote: > By measuring the execution time of mtrr_aps_init() (from which MTRRs > in all CPUs are programmed in lock-step at boot), I find savings in the > time required to program MTRRs as follows: > > Platform time-with-wbinvd(ms) time-no-wbin

Re: [PATCH 1/2] x86/cpu/intel: Clear cache self-snoop capability in CPUs with known errata

2019-06-27 Thread Thomas Gleixner
Ricardo, On Thu, 27 Jun 2019, Ricardo Neri wrote: > > +/* > + * Processors which have self-snooping capability can handle conflicting > + * memory type across CPUs by snooping its own cache. However, there exists > + * CPU models in which having conflicting memory types still leads to > + * unpr

Re: [PATCH] xtensa: remove unneeded BITS_PER_LONG define

2019-06-27 Thread Max Filippov
Hi Yamada-san, On Thu, Jun 27, 2019 at 12:01 AM Masahiro Yamada wrote: > > Xtensa does not define CONFIG_64BIT. The generic definition in > include/asm-generic/bitsperlong.h should work. > > Signed-off-by: Masahiro Yamada > --- > > arch/xtensa/include/asm/types.h | 8 > 1 file changed,

Re: [RFC] Deadlock via recursive wakeup via RCU with threadirqs

2019-06-27 Thread Paul E. McKenney
On Thu, Jun 27, 2019 at 03:17:27PM -0500, Scott Wood wrote: > On Thu, 2019-06-27 at 11:41 -0700, Paul E. McKenney wrote: > > On Thu, Jun 27, 2019 at 02:16:38PM -0400, Joel Fernandes wrote: > > > > > > I think the fix should be to prevent the wake-up not based on whether we > > > are > > > in hard/

RE: [PATCH v20 22/28] x86/traps: Attempt to fixup exceptions in vDSO before signaling

2019-06-27 Thread Xing, Cedric
> From: linux-sgx-ow...@vger.kernel.org [mailto:linux-sgx- > ow...@vger.kernel.org] On Behalf Of Jarkko Sakkinen > Sent: Tuesday, June 25, 2019 8:44 AM > > I went through the vDSO changes just to revisit couple of details that I > had forgotten. Sean, if you don't mind I'd squash this and prependi

[GIT PULL] clk fixes for v5.2-rc6

2019-06-27 Thread Stephen Boyd
The following changes since commit 1cc54078d104f5b4d7e9f8d55362efa5a8daffdb: clk: ti: clkctrl: Fix clkdm_clk handling (2019-05-21 11:43:40 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to fetch

[RFC PATCH bpf-next v2 5/6] selftests/bpf: test BPF_MAP_DUMP command on a bpf hashmap

2019-06-27 Thread Brian Vazquez
This tests exercise the new command on a bpf hashmap and make sure it works as expected. Signed-off-by: Brian Vazquez --- tools/testing/selftests/bpf/test_maps.c | 70 - 1 file changed, 68 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/bpf/test_maps.c

[RFC PATCH bpf-next v2 0/6] bpf: add BPF_MAP_DUMP command to

2019-06-27 Thread Brian Vazquez
This introduces a new command to retrieve a variable number of entries from a bpf map. This new command can be executed from the existing BPF syscall as follows: err = bpf(BPF_MAP_DUMP, union bpf_attr *attr, u32 size) using attr->dump.map_fd, attr->dump.prev_key, attr->dump.buf, attr->dump.buf_l

[RFC PATCH bpf-next v2 3/6] bpf: keep bpf.h in sync with tools/

2019-06-27 Thread Brian Vazquez
Adds bpf_attr.dump structure to libbpf. Suggested-by: Stanislav Fomichev Signed-off-by: Brian Vazquez --- tools/include/uapi/linux/bpf.h | 9 + 1 file changed, 9 insertions(+) diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h index b077507efa3f3..1d753958874d

[RFC PATCH bpf-next v2 2/6] bpf: add BPF_MAP_DUMP command to access more than one entry per call

2019-06-27 Thread Brian Vazquez
This introduces a new command to retrieve a variable number of entries from a bpf map wrapping the existing bpf methods: map_get_next_key and map_lookup_elem Note that map_dump doesn't guarantee that reading the entire table is consistent since this function is always racing with kernel and user c

<    1   2   3   4   5   6   7   8   9   10   >