Re: [PATCH 3/3] sound: don't call skl_init_chip() to reset intel skl soc

On Mon, 10 Sep 2018 23:23:58 +0200, Yu Zhao wrote: > > Internally, skl_init_chip() calls snd_hdac_bus_init_chip() which > 1) sets bus->chip_init to prevent multiple entrances before device > is stopped; 2) enables interrupt. > > We shouldn't use it for the purpose of resetting device only because

Re: [PATCH v3 06/12] RISC-V: Rename riscv_of_processor_hart to riscv_of_processor_hartid

On Mon, Sep 10, 2018 at 06:36:52PM -0700, Atish Patra wrote: > On 9/10/18 4:26 AM, Christoph Hellwig wrote: > > On Thu, Sep 06, 2018 at 01:05:29AM -0700, Atish Patra wrote: > > > From: Palmer Dabbelt > > > > > > It's a bit confusing exactly what this function does: it actually > > > returns the h

[tip:x86/boot] x86/corruption-check: Fix panic in memory_corruption_check() when boot option without value is provided

Commit-ID: ccde460b9ae5c2bd5e4742af0a7f623c2daad566 Gitweb: https://git.kernel.org/tip/ccde460b9ae5c2bd5e4742af0a7f623c2daad566 Author: He Zhe AuthorDate: Tue, 14 Aug 2018 23:33:42 +0800 Committer: Ingo Molnar CommitDate: Mon, 10 Sep 2018 14:47:32 +0200 x86/corruption-check: Fix panic

[tip:x86/boot] x86/corruption-check: Use pr_*() instead of printk()

Commit-ID: b1e3a25f5879017fc50ca17f03118b26a19df49a Gitweb: https://git.kernel.org/tip/b1e3a25f5879017fc50ca17f03118b26a19df49a Author: He Zhe AuthorDate: Tue, 14 Aug 2018 23:33:43 +0800 Committer: Ingo Molnar CommitDate: Mon, 10 Sep 2018 14:47:33 +0200 x86/corruption-check: Use pr_*()

[tip:perf/core] perf/x86: Add __ro_after_init annotations

Commit-ID: 2766d2ee960c52adc415931130dd6910158dd04d Gitweb: https://git.kernel.org/tip/2766d2ee960c52adc415931130dd6910158dd04d Author: Zubin Mithra AuthorDate: Fri, 10 Aug 2018 08:43:14 -0700 Committer: Ingo Molnar CommitDate: Mon, 10 Sep 2018 14:55:36 +0200 perf/x86: Add __ro_after_i

[tip:x86/urgent] x86/doc: Fix Documentation/x86/earlyprintk.txt

Commit-ID: 07e846bace717729fd20b5d99521a5f8c7d7a9cb Gitweb: https://git.kernel.org/tip/07e846bace717729fd20b5d99521a5f8c7d7a9cb Author: Randy Dunlap AuthorDate: Sun, 5 Aug 2018 20:34:05 -0700 Committer: Ingo Molnar CommitDate: Mon, 10 Sep 2018 15:09:30 +0200 x86/doc: Fix Documentation/

[tip:x86/boot] x86/boot/KASLR: Remove return value from handle_mem_options()

Commit-ID: 44060e8a5189fd79220a94422b8249a85e91 Gitweb: https://git.kernel.org/tip/44060e8a5189fd79220a94422b8249a85e91 Author: Chao Fan AuthorDate: Tue, 7 Aug 2018 09:57:05 +0800 Committer: Ingo Molnar CommitDate: Mon, 10 Sep 2018 15:07:11 +0200 x86/boot/KASLR: Remove return v

[tip:sched/core] sched/topology: Make local variables static

Commit-ID: ace8031099f91480799b5929b4cccf2dcacc5136 Gitweb: https://git.kernel.org/tip/ace8031099f91480799b5929b4cccf2dcacc5136 Author: zhong jiang AuthorDate: Fri, 3 Aug 2018 20:37:32 +0800 Committer: Ingo Molnar CommitDate: Mon, 10 Sep 2018 15:10:57 +0200 sched/topology: Make local v

Re: [PATCH v2 3/5] irqchip: RISC-V Local Interrupt Controller Driver

On Tue, Sep 11, 2018 at 09:27:45AM +0530, Anup Patel wrote: > The list of currently defined RISC-V local interrupts will definitely grow > based on my experience from ARM/ARM64 world. > > Like Thomas mentioned, we will definitely end-up having separate > irqchip and irq_domain for RISC-V local int

Re: [PATCH] sched/fair: Disable LB_BIAS by default

* Peter Zijlstra wrote: > On Thu, Aug 09, 2018 at 02:57:53PM +0100, Dietmar Eggemann wrote: > > LB_BIAS allows the adjustment on how conservative load should be > > balanced. > > > It is very likely that LB_BIAS' influence on load balancing can be > > neglected (see test results below). This i

[tip:locking/core] locking/rtmutex: Fix the preprocessor logic with normal #ifdef #else #endif

Commit-ID: 84818af26350c245c8e1994493b7459c0822be5b Gitweb: https://git.kernel.org/tip/84818af26350c245c8e1994493b7459c0822be5b Author: Steven Rostedt (VMware) AuthorDate: Mon, 10 Sep 2018 21:46:38 -0400 Committer: Ingo Molnar CommitDate: Tue, 11 Sep 2018 08:12:00 +0200 locking/rtmutex

Re: [PATCH] sched/fair: vruntime should normalize when switching from fair

On 09/07/2018 12:58 AM, Vincent Guittot wrote: On Fri, 7 Sep 2018 at 09:16, Juri Lelli wrote: On 06/09/18 16:25, Dietmar Eggemann wrote: Hi Juri, On 08/23/2018 11:54 PM, Juri Lelli wrote: On 23/08/18 18:52, Dietmar Eggemann wrote: Hi, On 08/21/2018 01:54 AM, Miguel de Dios wrote: On 08/1

Re: [PATCH v6 01/16] x86/cpu: Create Hygon Dhyana architecture support file

On 2018/9/11 0:38, Borislav Petkov wrote: That sentence is not needed for the same reason as above. And select CPU_SUP_AMD to solve the dependency issues in kernel. No, this should say: "Since Dhyana uses AMD functionality to a large degree, select CPU_SUP_AMD which provides that functionalit

Re: possible deadlock in aio_poll

On Mon, Sep 10, 2018 at 08:14:20PM +0200, Miklos Szeredi wrote: > Why do pollable waitqueues need to disable interrupts generally? Any waitqueue needs to disable interrupts for consistency. We always use spin_lock_irqsave in __wake_up_common_lock() for example.

Re: [PATCH V2] perf tools: Fix maps__find_symbol_by_name()

On 10/09/18 17:34, Arnaldo Carvalho de Melo wrote: > Em Fri, Sep 07, 2018 at 11:51:16AM +0300, Adrian Hunter escreveu: >> Commit 1c5aae7710bb ("perf machine: Create maps for x86 PTI entry >> trampolines") revealed a problem with maps__find_symbol_by_name() that > > Can we have this with a Fixes: 1

Re: [PATCH v8 0/3]: perf: reduce data loss when profiling highly parallel CPU bound workloads

* Alexey Budankov wrote: > It may sound too optimistic but glibc API is expected to be backward > compatible > and for POSIX AIO API part too. Internal implementation also tends to evolve > to > better option overtime, more probably basing on modern kernel capabilities > mentioned here: ht

Re: [PATCH -tip 5/5] kprobes: Don't call BUG_ON if there is a kprobe in use on free list

On Mon, 10 Sep 2018 14:23:56 +0200 Ingo Molnar wrote: > > * Masami Hiramatsu wrote: > > > Instead of calling BUG_ON, if we find a kprobe in use on free kprobe > > list, just remove it from the list and keep it on kprobe hash list > > as same as other in-use kprobes. > > > > Signed-off-by: Mas

Re: [PATCH v6 03/16] x86/cpu/mtrr: Support TOP_MEM2 and get MTRR number

On 2018/9/11 2:06, Borislav Petkov wrote: On Mon, Sep 10, 2018 at 09:16:03PM +0800, Pu Wen wrote: The Hygon Dhyana CPU have a special magic MSR way to force WB for From the last review round: Also, it is "The ... CPU has a special..." Please take your time and incorporate *all* review feedb

Re: [PATCH] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.

On Mon, Sep 10, 2018 at 11:27:47PM +0530, Himanshu Jha wrote: > On Mon, Sep 10, 2018 at 10:42:59PM +0800, Song Qiang wrote: > > This driver was originally written by ST in 2016 as a misc input device, > > and hasn't been maintained for a long time. I grabbed some code from > > it's API and reformed

Re: [PATCH] kernel: prevent submission of creds with higher privileges inside container

Hi Xin, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.19-rc3 next-20180910] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Is it possible to add pid and comm members to the event structure to increase the display of user and thread information?

Inotify api cannot display information about users and processes. That is, you can only know that the file event is generated, but you don't know who triggered the event, which is not conducive to fault location. Is it possible to add pid and comm members to the event structure to increase the di

Re: [PATCH] kernel: prevent submission of creds with higher privileges inside container

Hi Xin, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.19-rc3 next-20180910] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

<    4   5   6   7   8   9