Re: [PATCH v2 6/8] gpio: 104-idi-48: Implement get_multiple callback

-Breathitt-Gray/Implement-get_multiple-for-ACCES-and-PC-104-drivers/20180317-224135 config: x86_64-randconfig-x016-201810 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones

Re: [PATCH v2 6/8] gpio: 104-idi-48: Implement get_multiple callback

-Breathitt-Gray/Implement-get_multiple-for-ACCES-and-PC-104-drivers/20180317-224135 config: x86_64-randconfig-x016-201810 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones

Re: [PATCH 3/4] ima: Improvements in ima_appraise_measurement()

Quoting Thiago Jung Bauermann (bauer...@linux.vnet.ibm.com): > > Mimi Zohar writes: > > On Wed, 2018-03-14 at 21:03 -0300, Thiago Jung Bauermann wrote: > >> Hello Serge, > >> > >> Thanks for quickly reviewing these patches! > >> > >> Serge E. Hallyn

Re: [PATCH 3/4] ima: Improvements in ima_appraise_measurement()

Quoting Thiago Jung Bauermann (bauer...@linux.vnet.ibm.com): > > Mimi Zohar writes: > > On Wed, 2018-03-14 at 21:03 -0300, Thiago Jung Bauermann wrote: > >> Hello Serge, > >> > >> Thanks for quickly reviewing these patches! > >> > >> Serge E. Hallyn writes: > >> > >> > Quoting Thiago Jung

[PATCH] powerpc: wii.dts: Add drive slot LED

The Wii has a blue LED in the disk drive slot, which is controlled via a GPIO line. Add this LED to wii.dts, and mark it as a panic-indicator. Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/boot/dts/wii.dts | 12 1 file changed, 12 insertions(+) diff

[PATCH] powerpc: wii.dts: Add drive slot LED

The Wii has a blue LED in the disk drive slot, which is controlled via a GPIO line. Add this LED to wii.dts, and mark it as a panic-indicator. Signed-off-by: Jonathan Neuschäfer --- arch/powerpc/boot/dts/wii.dts | 12 1 file changed, 12 insertions(+) diff --git

Re: [PATCH v3 18/18] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

On Sat, Mar 17, 2018 at 12:25:14AM -0400, Sinan Kaya wrote: > On 3/17/2018 12:03 AM, Sinan Kaya wrote: > > On 3/16/2018 11:40 PM, Sinan Kaya wrote: > >> I'll change writel_relaxed() with __raw_writel() in the series like you > >> suggested > >> and also look at your other comments. > > > > I

Re: [PATCH v3 18/18] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

On Sat, Mar 17, 2018 at 12:25:14AM -0400, Sinan Kaya wrote: > On 3/17/2018 12:03 AM, Sinan Kaya wrote: > > On 3/16/2018 11:40 PM, Sinan Kaya wrote: > >> I'll change writel_relaxed() with __raw_writel() in the series like you > >> suggested > >> and also look at your other comments. > > > > I

Re: [PATCH] locks: change POSIX lock ownership on execve when files_struct is displaced

On Sat, Mar 17, 2018 at 10:25:20AM -0400, Jeff Layton wrote: > From: Jeff Layton > > POSIX mandates that open fds and their associated file locks should be > preserved across an execve. This works, unless the process is > multithreaded at the time that execve is called. > >

Re: [PATCH] locks: change POSIX lock ownership on execve when files_struct is displaced

On Sat, Mar 17, 2018 at 10:25:20AM -0400, Jeff Layton wrote: > From: Jeff Layton > > POSIX mandates that open fds and their associated file locks should be > preserved across an execve. This works, unless the process is > multithreaded at the time that execve is called. > > In that case, we'll

Re: [PATCH 1/2] ARM: dts: pfuze3000: update sw1a/vldo4 voltage range

Hi Anson, On Sat, Mar 17, 2018 at 3:57 AM, Anson Huang wrote: > Update sw1a/vldo4's voltage range according to latest pfuze3000 > datasheet from: > > http://cache.freescale.com/files/analog/doc/data_sheet/PF3000.pdf?fsrch=1=1=1 > > Signed-off-by: Anson Huang

Re: [PATCH 1/2] ARM: dts: pfuze3000: update sw1a/vldo4 voltage range

Hi Anson, On Sat, Mar 17, 2018 at 3:57 AM, Anson Huang wrote: > Update sw1a/vldo4's voltage range according to latest pfuze3000 > datasheet from: > > http://cache.freescale.com/files/analog/doc/data_sheet/PF3000.pdf?fsrch=1=1=1 > > Signed-off-by: Anson Huang > Signed-off-by: Robin Gong > --- >

[tracing] 45382b2a36: WARNING:at_kernel/locking/lockdep.c:#check_flags

FYI, we noticed the following commit (built with gcc-6): commit: 45382b2a369a50f62c64e07cb6f59992baeb9479 ("tracing: Improve design of preemptirq tracepoints and its users") url: https://github.com/0day-ci/linux/commits/Joel-Fernandes/Improve-preemptirq-tracepoint-usage/20180

[tracing] 45382b2a36: WARNING:at_kernel/locking/lockdep.c:#check_flags

FYI, we noticed the following commit (built with gcc-6): commit: 45382b2a369a50f62c64e07cb6f59992baeb9479 ("tracing: Improve design of preemptirq tracepoints and its users") url: https://github.com/0day-ci/linux/commits/Joel-Fernandes/Improve-preemptirq-tracepoint-usage/20180

Re: [PATCH 4.15 000/128] 4.15.11-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.15.11 release. There are 128 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.15 000/128] 4.15.11-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.15.11 release. There are 128 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.14 000/109] 4.14.28-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.14.28 release. There are 109 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.14 000/109] 4.14.28-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.14.28 release. There are 109 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.9 00/86] 4.9.88-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.88 release. There are 86 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.9 00/86] 4.9.88-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.88 release. There are 86 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.4 00/63] 4.4.122-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.122 release. There are 63 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.4 00/63] 4.4.122-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.122 release. There are 63 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 3.18 00/25] 3.18.100-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 3.18.100 release. There are 25 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 3.18 00/25] 3.18.100-stable review

On 03/16/2018 08:22 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 3.18.100 release. There are 25 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

[PATCH v4.16-rc5 2/2] x86/vdso: VDSO should handle clock_gettime(CLOCK_MONOTONIC_RAW) without syscall

This patch allows compilation to succeed with compilers that support -DRETPOLINE - it was kindly contributed by H.J. Liu in GCC Bugzilla: 84908 : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 Apparently the GCC retpoline implementation has a limitation

[PATCH v4.16-rc5 2/2] x86/vdso: VDSO should handle clock_gettime(CLOCK_MONOTONIC_RAW) without syscall

This patch allows compilation to succeed with compilers that support -DRETPOLINE - it was kindly contributed by H.J. Liu in GCC Bugzilla: 84908 : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84908 Apparently the GCC retpoline implementation has a limitation

[PATCH v4.16-rc5 (2)] x86/vdso: VDSO should handle clock_gettime(CLOCK_MONOTONIC_RAW) without syscall

Resent to address reviewer comments, and allow builds with compilers that support -DRETPOLINE to succeed. Currently, the VDSO does not handle clock_gettime( CLOCK_MONOTONIC_RAW, ) on Intel / AMD - it calls vdso_fallback_gettime() for this clock, which issues a syscall,

[PATCH v4.16-rc5 (2)] x86/vdso: VDSO should handle clock_gettime(CLOCK_MONOTONIC_RAW) without syscall

Resent to address reviewer comments, and allow builds with compilers that support -DRETPOLINE to succeed. Currently, the VDSO does not handle clock_gettime( CLOCK_MONOTONIC_RAW, ) on Intel / AMD - it calls vdso_fallback_gettime() for this clock, which issues a syscall,

[PATCH v4.16-rc5 1/2] x86/vdso: VDSO should handle clock_gettime(CLOCK_MONOTONIC_RAW) without syscall

This patch makes the vDSO handle clock_gettime(CLOCK_MONOTONIC_RAW,) calls in the same way it handles clock_gettime(CLOCK_MONOTONIC,) calls, reducing latency from @ 200-1000ns to @ 20ns. diff --git a/arch/x86/entry/vdso/vclock_gettime.c

[PATCH v4.16-rc5 1/2] x86/vdso: VDSO should handle clock_gettime(CLOCK_MONOTONIC_RAW) without syscall

This patch makes the vDSO handle clock_gettime(CLOCK_MONOTONIC_RAW,) calls in the same way it handles clock_gettime(CLOCK_MONOTONIC,) calls, reducing latency from @ 200-1000ns to @ 20ns. diff --git a/arch/x86/entry/vdso/vclock_gettime.c

Re: [PATCH 4.14 064/109] dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free

On Fri, Mar 16, 2018 at 01:46:40PM -0500, Dan Rue wrote: > On Fri, Mar 16, 2018 at 04:23:33PM +0100, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Peter Ujfalusi > > > >

Re: [PATCH 4.14 064/109] dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free

On Fri, Mar 16, 2018 at 01:46:40PM -0500, Dan Rue wrote: > On Fri, Mar 16, 2018 at 04:23:33PM +0100, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Peter Ujfalusi > > > > > > [ Upstream commit

[PATCH] locks: change POSIX lock ownership on execve when files_struct is displaced

From: Jeff Layton POSIX mandates that open fds and their associated file locks should be preserved across an execve. This works, unless the process is multithreaded at the time that execve is called. In that case, we'll end up unsharing the files_struct but the locks will

[PATCH] locks: change POSIX lock ownership on execve when files_struct is displaced

From: Jeff Layton POSIX mandates that open fds and their associated file locks should be preserved across an execve. This works, unless the process is multithreaded at the time that execve is called. In that case, we'll end up unsharing the files_struct but the locks will still have their

Re: [PATCH v6 00/21] tracing: probeevent: Improve fetcharg features

On Sat, 17 Mar 2018 21:37:21 +0900 Masami Hiramatsu wrote: > Hi, > > This is the 6th version of the fetch-arg improvement series. > This includes variable changes on fetcharg framework like, > > - Add fetcharg testcases (syntax, argN, symbol, string and array) > and

Re: [PATCH v6 00/21] tracing: probeevent: Improve fetcharg features

On Sat, 17 Mar 2018 21:37:21 +0900 Masami Hiramatsu wrote: > Hi, > > This is the 6th version of the fetch-arg improvement series. > This includes variable changes on fetcharg framework like, > > - Add fetcharg testcases (syntax, argN, symbol, string and array) > and probepoint testcase. > -

Re: [PATCH v2] irqchip/gic-v3: Ensure GICR_CTLR.EnableLPI=0 is observed before enabling

On Thu, 15 Mar 2018 09:31:27 -0500 Shanker Donthineni wrote: > The definition of the GICR_CTLR.RWP control bit was expanded to indicate > status of changing GICR_CTLR.EnableLPI from 1 to 0 is being in progress > or completed. Software must observe GICR_CTLR.RWP==0 after

Re: [PATCH v2] irqchip/gic-v3: Ensure GICR_CTLR.EnableLPI=0 is observed before enabling

On Thu, 15 Mar 2018 09:31:27 -0500 Shanker Donthineni wrote: > The definition of the GICR_CTLR.RWP control bit was expanded to indicate > status of changing GICR_CTLR.EnableLPI from 1 to 0 is being in progress > or completed. Software must observe GICR_CTLR.RWP==0 after clearing >

Re: [PATCH v3 18/18] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

From: Sinan Kaya Date: Sat, 17 Mar 2018 00:25:14 -0400 > I think I finally got what you mean. > > Code seems to have > > wmb() > writel()/writeq() > wmb() > > this can be safely replaced with > > wmb() > __raw_writel()/__raw_writeq() > wmb() > > This will work on all

Re: [PATCH v3 18/18] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

From: Sinan Kaya Date: Sat, 17 Mar 2018 00:25:14 -0400 > I think I finally got what you mean. > > Code seems to have > > wmb() > writel()/writeq() > wmb() > > this can be safely replaced with > > wmb() > __raw_writel()/__raw_writeq() > wmb() > > This will work on all arches. Below is the

Re: linux-next: manual merge of the rtc tree with the asm-generic tree

Hi Stephen, On 15/03/2018 at 18:59:17 +1100, Stephen Rothwell wrote: > Hi Alexandre, > > Today's linux-next merge of the rtc tree got a conflict in: > > drivers/rtc/rtc-tile.c > > between commit: > > 909ce75a0665 ("rtc: remove tile driver") > > from the asm-generic tree and commit: > >

RE: [PATCH v3 18/18] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

> > On 3/17/2018 12:03 AM, Sinan Kaya wrote: > > On 3/16/2018 11:40 PM, Sinan Kaya wrote: > >> I'll change writel_relaxed() with __raw_writel() in the series like you > suggested > >> and also look at your other comments. > > > > I spoke too soon. > > > > Now that I realized, code needs to follow

Re: linux-next: manual merge of the rtc tree with the asm-generic tree

Hi Stephen, On 15/03/2018 at 18:59:17 +1100, Stephen Rothwell wrote: > Hi Alexandre, > > Today's linux-next merge of the rtc tree got a conflict in: > > drivers/rtc/rtc-tile.c > > between commit: > > 909ce75a0665 ("rtc: remove tile driver") > > from the asm-generic tree and commit: > >

RE: [PATCH v3 18/18] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

> > On 3/17/2018 12:03 AM, Sinan Kaya wrote: > > On 3/16/2018 11:40 PM, Sinan Kaya wrote: > >> I'll change writel_relaxed() with __raw_writel() in the series like you > suggested > >> and also look at your other comments. > > > > I spoke too soon. > > > > Now that I realized, code needs to follow

[PATCH v6 21/21] perf-probe: Add array argument support

Since kprobes events support an array argument, perf-probe can also support dumping array now. The syntax are [] or [] where the is ... e.g. array[0..5]. This can also be available with string type. In this case, the string array should be "char *array[]" or "char **array_ptr". Note that

[PATCH v6 21/21] perf-probe: Add array argument support

Since kprobes events support an array argument, perf-probe can also support dumping array now. The syntax are [] or [] where the is ... e.g. array[0..5]. This can also be available with string type. In this case, the string array should be "char *array[]" or "char **array_ptr". Note that

[PATCH v6 20/21] [RESEND] perf-probe: Fix to convert array type collectly

Fix to convert array element type collectly. Current perf-probe converts the type of array-elements incorrectly. It always converts the types as a pointer of array. This passes the "array" type DIE to the type converter so that it can get correct "element of array" type DIE from it. E.g.

[PATCH v6 20/21] [RESEND] perf-probe: Fix to convert array type collectly

Fix to convert array element type collectly. Current perf-probe converts the type of array-elements incorrectly. It always converts the types as a pointer of array. This passes the "array" type DIE to the type converter so that it can get correct "element of array" type DIE from it. E.g.

[PATCH v6 19/21] selftests: ftrace: Add a testcase for array type with kprobe_event

Add a testcase for array type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. If the kernel doesn't support array type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v4: -

[PATCH v6 19/21] selftests: ftrace: Add a testcase for array type with kprobe_event

Add a testcase for array type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. If the kernel doesn't support array type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v4: - Add format field tests.

[PATCH v6 18/21] selftests: ftrace: Add a testcase for $argN with kprobe_event

Add a testcase for $argN with kprobe event. This tests whether the traced data is correct or not. If the kernel doesn't support $argN (depends on arch), it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v5: - Fix description. ---

[PATCH v6 18/21] selftests: ftrace: Add a testcase for $argN with kprobe_event

Add a testcase for $argN with kprobe event. This tests whether the traced data is correct or not. If the kernel doesn't support $argN (depends on arch), it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v5: - Fix description. ---

[PATCH v6 17/21] selftests: ftrace: Add a testcase for symbol type

Add a testcase for symbol type with kprobe event. This tests good/bad syntax combinations and also the traced data. If the kernel doesn't support symbol type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Use IP/PC register to test

[PATCH v6 17/21] selftests: ftrace: Add a testcase for symbol type

Add a testcase for symbol type with kprobe event. This tests good/bad syntax combinations and also the traced data. If the kernel doesn't support symbol type, it skips the test as UNSUPPORTED. Signed-off-by: Masami Hiramatsu --- Changes in v3: - Use IP/PC register to test the symbol type ---

[PATCH v6 16/21] tracing: probeevent: Add array type support

Add array type support for probe events. This allows user to get arraied types from memory address. The array type syntax is TYPE[N] Where TYPE is one of types (u8/16/32/64,s8/16/32/64, x8/16/32/64, symbol, string) and N is a fixed value less than 64. The string array type is a bit

[PATCH v6 16/21] tracing: probeevent: Add array type support

Add array type support for probe events. This allows user to get arraied types from memory address. The array type syntax is TYPE[N] Where TYPE is one of types (u8/16/32/64,s8/16/32/64, x8/16/32/64, symbol, string) and N is a fixed value less than 64. The string array type is a bit

[PATCH v6 15/21] tracing: probeevent: Add $argN for accessing function args

Add $argN special fetch variable for accessing function arguments. This allows user to trace the Nth argument easily at the function entry. Note that this returns most probably assignment of registers and stacks. In some case, it may not work well. If you need to access correct registers or

[PATCH v6 15/21] tracing: probeevent: Add $argN for accessing function args

Add $argN special fetch variable for accessing function arguments. This allows user to trace the Nth argument easily at the function entry. Note that this returns most probably assignment of registers and stacks. In some case, it may not work well. If you need to access correct registers or

[PATCH v6 14/21] x86: ptrace: Add function argument access API

Add regs_get_argument() which returns N th argument of the function call. Note that this chooses most probably assignment, in some case it can be incorrect (e.g. passing data structure or floating point etc.) This is expected to be called from kprobes or ftrace with regs where the top of stack is

[PATCH v6 14/21] x86: ptrace: Add function argument access API

Add regs_get_argument() which returns N th argument of the function call. Note that this chooses most probably assignment, in some case it can be incorrect (e.g. passing data structure or floating point etc.) This is expected to be called from kprobes or ftrace with regs where the top of stack is

[PATCH v6 13/21] tracing: probeevent: Add symbol type

Add "symbol" type to probeevent, which is an alias of u32 or u64 (depends on BITS_PER_LONG). This shows the result value in symbol+offset style. This type is only available with kprobe events. Signed-off-by: Masami Hiramatsu --- Changes in v2: - Add symbol type to README

[PATCH v6 13/21] tracing: probeevent: Add symbol type

Add "symbol" type to probeevent, which is an alias of u32 or u64 (depends on BITS_PER_LONG). This shows the result value in symbol+offset style. This type is only available with kprobe events. Signed-off-by: Masami Hiramatsu --- Changes in v2: - Add symbol type to README file. ---

[PATCH v6 12/21] tracing: probeevent: Unify fetch_insn processing common part

Unify the fetch_insn bottom process (from stage 2: dereference indirect data) from kprobe and uprobe events, since those are mostly same. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 47 +

[PATCH v6 12/21] tracing: probeevent: Unify fetch_insn processing common part

Unify the fetch_insn bottom process (from stage 2: dereference indirect data) from kprobe and uprobe events, since those are mostly same. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 47 + kernel/trace/trace_probe_tmpl.h | 55

[PATCH v6 11/21] tracing: probeevent: Append traceprobe_ for exported function

Append traceprobe_ for exported function set_print_fmt() as same as other functions. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c |4 ++-- kernel/trace/trace_probe.c |2 +- kernel/trace/trace_probe.h |2 +- kernel/trace/trace_uprobe.c |4

[PATCH v6 11/21] tracing: probeevent: Append traceprobe_ for exported function

Append traceprobe_ for exported function set_print_fmt() as same as other functions. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c |4 ++-- kernel/trace/trace_probe.c |2 +- kernel/trace/trace_probe.h |2 +- kernel/trace/trace_uprobe.c |4 ++-- 4 files

[PATCH v6 10/21] tracing: probeevent: Return consumed bytes of dynamic area

Cleanup string fetching routine so that returns the consumed bytes of dynamic area and store the string information as data_loc format instead of data_rloc. This simplifies the fetcharg loop. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 51

[PATCH v6 10/21] tracing: probeevent: Return consumed bytes of dynamic area

Cleanup string fetching routine so that returns the consumed bytes of dynamic area and store the string information as data_loc format instead of data_rloc. This simplifies the fetcharg loop. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 51

[PATCH v6 08/21] tracing: probeevent: Introduce new argument fetching code

Replace {k,u}probe event argument fetching framework with switch-case based. Currently that is implemented with structures, macros and chain of function-pointers, which is more complicated than necessary and may get a performance penalty by retpoline. This simplify that with an array of

[PATCH v6 09/21] tracing: probeevent: Unify fetch type tables

Unify {k,u}probe_fetch_type_table to probe_fetch_type_table because the main difference of those type tables (fetcharg methods) are gone. Now we can consolidate it. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 27 +-

[PATCH v6 08/21] tracing: probeevent: Introduce new argument fetching code

Replace {k,u}probe event argument fetching framework with switch-case based. Currently that is implemented with structures, macros and chain of function-pointers, which is more complicated than necessary and may get a performance penalty by retpoline. This simplify that with an array of

[PATCH v6 09/21] tracing: probeevent: Unify fetch type tables

Unify {k,u}probe_fetch_type_table to probe_fetch_type_table because the main difference of those type tables (fetcharg methods) are gone. Now we can consolidate it. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 27 +- kernel/trace/trace_probe.c | 54

Re: [RFT][PATCH v5 0/7] sched/cpuidle: Idle loop rework

Over the last week I tested v4+pollv2 and now v5+pollv3. With v5, I observe a particular idle behavior, that I have not seen before with v4. On a dual-socket Skylake system the idle power increases from 74.1 W (system total) to 85.5 W with a 300 HZ build and even to 138.3 W with a 1000 HZ build.

Re: [RFT][PATCH v5 0/7] sched/cpuidle: Idle loop rework

Over the last week I tested v4+pollv2 and now v5+pollv3. With v5, I observe a particular idle behavior, that I have not seen before with v4. On a dual-socket Skylake system the idle power increases from 74.1 W (system total) to 85.5 W with a 300 HZ build and even to 138.3 W with a 1000 HZ build.

[PATCH v6 07/21] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions

Remove unneeded NOKPROBE_SYMBOL from print functions since the print functions are only used when printing out the trace data, and not from kprobe handler. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_probe.c |4 +--- 1 file changed, 1 insertion(+), 3

[PATCH v6 07/21] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions

Remove unneeded NOKPROBE_SYMBOL from print functions since the print functions are only used when printing out the trace data, and not from kprobe handler. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_probe.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH v6 06/21] tracing: probeevent: Cleanup argument field definition

Cleanup event argument definition code in one place for maintenancability. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 32 kernel/trace/trace_probe.c | 21 + kernel/trace/trace_probe.h |2

[PATCH v6 06/21] tracing: probeevent: Cleanup argument field definition

Cleanup event argument definition code in one place for maintenancability. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 32 kernel/trace/trace_probe.c | 21 + kernel/trace/trace_probe.h |2 ++

[PATCH v6 05/21] tracing: probeevent: Cleanup print argument functions

Current print argument functions prints the argument name too. It is not good for printing out multiple values for one argument. This change it to just print out the value. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 20 ++--

[PATCH v6 05/21] tracing: probeevent: Cleanup print argument functions

Current print argument functions prints the argument name too. It is not good for printing out multiple values for one argument. This change it to just print out the value. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 20 ++-- kernel/trace/trace_probe.c |

[PATCH v6 04/21] selftests: ftrace: Add a testcase for probepoint

Add a testcase for probe point definition. This tests symbol, address and symbol+offset syntax. The offset must be positive and smaller than UINT_MAX. Signed-off-by: Masami Hiramatsu --- .../selftests/ftrace/test.d/kprobe/probepoint.tc | 43 1 file

[PATCH v6 04/21] selftests: ftrace: Add a testcase for probepoint

Add a testcase for probe point definition. This tests symbol, address and symbol+offset syntax. The offset must be positive and smaller than UINT_MAX. Signed-off-by: Masami Hiramatsu --- .../selftests/ftrace/test.d/kprobe/probepoint.tc | 43 1 file changed, 43

[PATCH v6 03/21] selftests: ftrace: Add a testcase for string type with kprobe_event

Add a testcase for string type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_string.tc | 46 1 file changed,

[PATCH v6 03/21] selftests: ftrace: Add a testcase for string type with kprobe_event

Add a testcase for string type with kprobe event. This tests good/bad syntax combinations and also the traced data is correct in several way. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_string.tc | 46 1 file changed, 46 insertions(+)

[PATCH v6 02/21] selftests: ftrace: Add probe event argument syntax testcase

Add a testcase for probe event argument syntax which ensures the kprobe_events interface correctly parses given event arguments. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_syntax.tc | 97 1 file changed, 97

[PATCH v6 02/21] selftests: ftrace: Add probe event argument syntax testcase

Add a testcase for probe event argument syntax which ensures the kprobe_events interface correctly parses given event arguments. Signed-off-by: Masami Hiramatsu --- .../ftrace/test.d/kprobe/kprobe_args_syntax.tc | 97 1 file changed, 97 insertions(+) create mode

[PATCH v6 01/21] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol

In Documentation/trace/kprobetrace.txt, it says @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol) However, the parser doesn't parse minus offset correctly, since commit 2fba0c8867af ("tracing/kprobes: Fix probe offset to be unsigned") drops minus ("-") offset support

[PATCH v6 01/21] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol

In Documentation/trace/kprobetrace.txt, it says @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol) However, the parser doesn't parse minus offset correctly, since commit 2fba0c8867af ("tracing/kprobes: Fix probe offset to be unsigned") drops minus ("-") offset support

[PATCH v6 00/21] tracing: probeevent: Improve fetcharg features

Hi, This is the 6th version of the fetch-arg improvement series. This includes variable changes on fetcharg framework like, - Add fetcharg testcases (syntax, argN, symbol, string and array) and probepoint testcase. - Rewrite fetcharg framework with fetch_insn, switch-case based instead of

[PATCH v6 00/21] tracing: probeevent: Improve fetcharg features

Hi, This is the 6th version of the fetch-arg improvement series. This includes variable changes on fetcharg framework like, - Add fetcharg testcases (syntax, argN, symbol, string and array) and probepoint testcase. - Rewrite fetcharg framework with fetch_insn, switch-case based instead of

Re: [PATCH 2/2] regulator: pfuze100: update voltage setting for pfuze3000 sw1a

Hi Anson, > Anson Huang hat am 17. März 2018 um 07:57 geschrieben: > > > Latest pfuze3000 datasheet from: > > http://cache.freescale.com/files/analog/doc/data_sheet/PF3000.pdf?fsrch=1=1=1 this link goes to Rev. 7.0, 9/2016, which isn't the latest one. I guess Rev. 9.0,

Re: [PATCH 2/2] regulator: pfuze100: update voltage setting for pfuze3000 sw1a

Hi Anson, > Anson Huang hat am 17. März 2018 um 07:57 geschrieben: > > > Latest pfuze3000 datasheet from: > > http://cache.freescale.com/files/analog/doc/data_sheet/PF3000.pdf?fsrch=1=1=1 this link goes to Rev. 7.0, 9/2016, which isn't the latest one. I guess Rev. 9.0, 8/2017 is the latest.

Re: [ANNOUNCE] v4.14.27-rt21

On 2018-03-17 12:49:20 [+0100], To Thomas Gleixner wrote: > The delta patch against v4.14.27-rt20 is appended below and can be found here: diff --git a/block/blk-core.c b/block/blk-core.c index ff1258ca236c..b37ea6bb739c 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -799,7 +799,7 @@ int

Re: [ANNOUNCE] v4.14.27-rt21

On 2018-03-17 12:49:20 [+0100], To Thomas Gleixner wrote: > The delta patch against v4.14.27-rt20 is appended below and can be found here: diff --git a/block/blk-core.c b/block/blk-core.c index ff1258ca236c..b37ea6bb739c 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -799,7 +799,7 @@ int

Re: [PATCH] w1: gpio: fix problem with platfom data in w1-gpio

On Sat, Mar 17, 2018 at 11:39:11AM +0100, Paweł Dembicki wrote: > 2018-03-14 14:59 GMT+01:00 Greg Kroah-Hartman : > > > > > Patch does not apply at all to my tree :( > > Patch works with stable kernels (e.g 4.9 and 4.14). > On which tip You test? Where is this patch

Re: [PATCH] w1: gpio: fix problem with platfom data in w1-gpio

On Sat, Mar 17, 2018 at 11:39:11AM +0100, Paweł Dembicki wrote: > 2018-03-14 14:59 GMT+01:00 Greg Kroah-Hartman : > > > > > Patch does not apply at all to my tree :( > > Patch works with stable kernels (e.g 4.9 and 4.14). > On which tip You test? Where is this patch supposed to go? Is this a

Re: [PATCH v2] earlycon: Fix __earlycon_table stride... again

/Daniel-Kurtz/earlycon-Fix-__earlycon_table-stride-again/20180317-180525 config: alpha-allyesconfig (attached as .config) compiler: alpha-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross

Re: [PATCH v2] earlycon: Fix __earlycon_table stride... again

/Daniel-Kurtz/earlycon-Fix-__earlycon_table-stride-again/20180317-180525 config: alpha-allyesconfig (attached as .config) compiler: alpha-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross

[ANNOUNCE] v4.14.27-rt21

Dear RT folks! I'm pleased to announce the v4.14.27-rt21 patch set. Changes since v4.14.27-rt20: - The blk-queue triggered a warning in swake_up_all() because it invoked the function with disabled interrupts in !RT configs. Reported by Corey Minyard. - The cpu_chill() function

[ANNOUNCE] v4.14.27-rt21

Dear RT folks! I'm pleased to announce the v4.14.27-rt21 patch set. Changes since v4.14.27-rt20: - The blk-queue triggered a warning in swake_up_all() because it invoked the function with disabled interrupts in !RT configs. Reported by Corey Minyard. - The cpu_chill() function

<    1   2   3   4   5   6   >