[PATCH v12 01/10] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

From: "David A. Long" Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64. Signed-off-by: David A. Long --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/ptrace.h | 33 ++- arch/arm64/kernel/ptrace.c | 118

[PATCH v12 02/10] arm64: Add more test functions to insn.c

From: "David A. Long" Certain instructions are hard to execute correctly out-of-line (as in kprobes). Test functions are added to insn.[hc] to identify these. The instructions include any that use PC-relative addressing, change the PC, or change interrupt masking. For

Re: [PATCH 1/3] lightnvm: do not free unused metadata on rrpc

On 04/27/2016 07:28 PM, Javier González wrote: rrpc does not save any metadata on a given request. Thus, do not attempt to free the metadata dma region. Signed-off-by: Javier González --- drivers/lightnvm/rrpc.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH v12 01/10] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

From: "David A. Long" Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64. Signed-off-by: David A. Long --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/ptrace.h | 33 ++- arch/arm64/kernel/ptrace.c | 118 3 files

[PATCH v12 02/10] arm64: Add more test functions to insn.c

From: "David A. Long" Certain instructions are hard to execute correctly out-of-line (as in kprobes). Test functions are added to insn.[hc] to identify these. The instructions include any that use PC-relative addressing, change the PC, or change interrupt masking. For efficiency and simplicity

Re: [PATCH 1/3] lightnvm: do not free unused metadata on rrpc

On 04/27/2016 07:28 PM, Javier González wrote: rrpc does not save any metadata on a given request. Thus, do not attempt to free the metadata dma region. Signed-off-by: Javier González --- drivers/lightnvm/rrpc.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/lightnvm/rrpc.c

[PATCH v12 00/10] arm64: Add kernel probes (kprobes) support

From: "David A. Long" This patchset is heavily based on Sandeepa Prabhu's ARM v8 kprobes patches, first seen in October 2013. This version attempts to address concerns raised by reviewers and also fixes problems discovered during testing. This patchset adds support for

[PATCH v12 00/10] arm64: Add kernel probes (kprobes) support

From: "David A. Long" This patchset is heavily based on Sandeepa Prabhu's ARM v8 kprobes patches, first seen in October 2013. This version attempts to address concerns raised by reviewers and also fixes problems discovered during testing. This patchset adds support for kernel probes(kprobes),

[PATCH v12 04/10] arm64: Blacklist non-kprobe-able symbols

From: Pratyush Anand Add all function symbols which are called from do_debug_exception under NOKPROBE_SYMBOL, as they can not kprobed. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/arm64ksyms.c | 2 ++ arch/arm64/kernel/debug-monitors.c | 18

Re: [PATCH v2] net: Add Qualcomm IPC router

From: Bjorn Andersson Date: Wed, 27 Apr 2016 10:14:45 -0700 > On Wed 27 Apr 09:22 PDT 2016, David Miller wrote: > >> This code can now only be build tested on ARCH_QCOM architectures, and >> that's a serious negative downside. > > For normal usage the QRTR_SMD

[PATCH v12 04/10] arm64: Blacklist non-kprobe-able symbols

From: Pratyush Anand Add all function symbols which are called from do_debug_exception under NOKPROBE_SYMBOL, as they can not kprobed. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/arm64ksyms.c | 2 ++ arch/arm64/kernel/debug-monitors.c | 18 ++

Re: [PATCH v2] net: Add Qualcomm IPC router

From: Bjorn Andersson Date: Wed, 27 Apr 2016 10:14:45 -0700 > On Wed 27 Apr 09:22 PDT 2016, David Miller wrote: > >> This code can now only be build tested on ARCH_QCOM architectures, and >> that's a serious negative downside. > > For normal usage the QRTR_SMD doesn't make much sense to be

Re: [PATCH V10 2/6] mfd: max77620: add core driver for MAX77620/MAX20024

On Wednesday 27 April 2016 08:49 PM, Lee Jones wrote: On Wed, 30 Mar 2016, Laxman Dewangan wrote: What are 20 and 40? I think you're going to need a comment to describe what's going on in this function. + int x, i; + + for (i = 0; i < 0x7; i++) { It's unsual to use hex values

Re: [PATCH V10 2/6] mfd: max77620: add core driver for MAX77620/MAX20024

On Wednesday 27 April 2016 08:49 PM, Lee Jones wrote: On Wed, 30 Mar 2016, Laxman Dewangan wrote: What are 20 and 40? I think you're going to need a comment to describe what's going on in this function. + int x, i; + + for (i = 0; i < 0x7; i++) { It's unsual to use hex values

[PATCH v12 06/10] arm64: Treat all entry code as non-kprobe-able

From: Pratyush Anand Entry symbols are not kprobe safe. So blacklist them for kprobing. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/entry.S | 3 +++ arch/arm64/kernel/kprobes.c | 10 ++ arch/arm64/kernel/vmlinux.lds.S | 1 + 3

Re: [PATCH 3/3] lightnvm: rename dma helper functions

On 04/27/2016 07:28 PM, Javier González wrote: Until now, the dma pool have been exclusively used to allocate the ppa list being sent to the device. In pblk (upcoming), we use these pools to allocate metadata too. Thus, we generalize the names of some variables on the dma helper functions to

[PATCH v12 06/10] arm64: Treat all entry code as non-kprobe-able

From: Pratyush Anand Entry symbols are not kprobe safe. So blacklist them for kprobing. Signed-off-by: Pratyush Anand --- arch/arm64/kernel/entry.S | 3 +++ arch/arm64/kernel/kprobes.c | 10 ++ arch/arm64/kernel/vmlinux.lds.S | 1 + 3 files changed, 14 insertions(+) diff

Re: [PATCH 3/3] lightnvm: rename dma helper functions

On 04/27/2016 07:28 PM, Javier González wrote: Until now, the dma pool have been exclusively used to allocate the ppa list being sent to the device. In pblk (upcoming), we use these pools to allocate metadata too. Thus, we generalize the names of some variables on the dma helper functions to

[PATCH v12 05/10] arm64: Kprobes with single stepping support

From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exceptions supported on ARM v8. A software breakpoint is placed at the probe address to trap the

[PATCH v12 09/10] arm64: Add kernel return probes support (kretprobes)

From: Sandeepa Prabhu The pre-handler of this special 'trampoline' kprobe executes the return probe handler functions and restores original return address in ELR_EL1. This way the saved pt_regs still hold the original register context to be carried back to the probed

Re: [PATCH 2/2] ASoC: bcm2835: Add S16_LE support via packed DMA transfers

Matthias Reichl writes: > The bcm2835-i2s driver already has support for the S16_LE format but > that format hasn't been made available because dmaengine_pcm didn't > support packed data transfers. Acked-by: Eric Anholt signature.asc Description: PGP

[PATCH v12 09/10] arm64: Add kernel return probes support (kretprobes)

From: Sandeepa Prabhu The pre-handler of this special 'trampoline' kprobe executes the return probe handler functions and restores original return address in ELR_EL1. This way the saved pt_regs still hold the original register context to be carried back to the probed kernel function.

Re: [PATCH 2/2] ASoC: bcm2835: Add S16_LE support via packed DMA transfers

Matthias Reichl writes: > The bcm2835-i2s driver already has support for the S16_LE format but > that format hasn't been made available because dmaengine_pcm didn't > support packed data transfers. Acked-by: Eric Anholt signature.asc Description: PGP signature

[PATCH v12 05/10] arm64: Kprobes with single stepping support

From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exceptions supported on ARM v8. A software breakpoint is placed at the probe address to trap the kernel execution into the kprobe

[PATCH v12 07/10] arm64: kprobes instruction simulation support

From: Sandeepa Prabhu Kprobes needs simulation of instructions that cannot be stepped from a different memory location, e.g.: those instructions that uses PC-relative addressing. In simulation, the behaviour of the instruction is implemented using a copy of pt_regs.

[PATCH v12 07/10] arm64: kprobes instruction simulation support

From: Sandeepa Prabhu Kprobes needs simulation of instructions that cannot be stepped from a different memory location, e.g.: those instructions that uses PC-relative addressing. In simulation, the behaviour of the instruction is implemented using a copy of pt_regs. The following instruction

[PATCH v12 10/10] kprobes: Add arm64 case in kprobe example module

From: Sandeepa Prabhu Add info prints in sample kprobe handlers for ARM64 Signed-off-by: Sandeepa Prabhu --- samples/kprobes/kprobe_example.c | 8 1 file changed, 8 insertions(+) diff --git a/samples/kprobes/kprobe_example.c

[PATCH v12 10/10] kprobes: Add arm64 case in kprobe example module

From: Sandeepa Prabhu Add info prints in sample kprobe handlers for ARM64 Signed-off-by: Sandeepa Prabhu --- samples/kprobes/kprobe_example.c | 8 1 file changed, 8 insertions(+) diff --git a/samples/kprobes/kprobe_example.c b/samples/kprobes/kprobe_example.c index 727eb21..0c72b8a

[PATCH v12 08/10] arm64: Add trampoline code for kretprobes

From: William Cohen The trampoline code is used by kretprobes to capture a return from a probed function. This is done by saving the registers, calling the handler, and restoring the registers. The code then returns to the original saved caller return address. It is necessary

[PATCH v12 08/10] arm64: Add trampoline code for kretprobes

From: William Cohen The trampoline code is used by kretprobes to capture a return from a probed function. This is done by saving the registers, calling the handler, and restoring the registers. The code then returns to the original saved caller return address. It is necessary to do this

[PATCH v12 03/10] arm64: add conditional instruction simulation support

From: "David A. Long" Cease using the arm32 arm_check_condition() function and replace it with a local version for use in deprecated instruction support on arm64. Also make the function table used by this available for future use by kprobes and/or uprobes. This function is

[PATCH v12 03/10] arm64: add conditional instruction simulation support

From: "David A. Long" Cease using the arm32 arm_check_condition() function and replace it with a local version for use in deprecated instruction support on arm64. Also make the function table used by this available for future use by kprobes and/or uprobes. This function is dervied from code

Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot

On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel

Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot

On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel

Re: [PATCH perf/core v4 18/19] perf probe: Allow wildcard for cached events

On Wed, 27 Apr 2016 21:04:53 +0530 Hemant Kumar wrote: > > > On 04/26/2016 02:34 PM, Masami Hiramatsu wrote: > > Allo glob wildcard for reusing cached/SDT events. This also > > automatically find the target binaries, e.g. > > > ># perf probe -a %sdt_libc:\* > > >

Re: [PATCH perf/core v4 18/19] perf probe: Allow wildcard for cached events

On Wed, 27 Apr 2016 21:04:53 +0530 Hemant Kumar wrote: > > > On 04/26/2016 02:34 PM, Masami Hiramatsu wrote: > > Allo glob wildcard for reusing cached/SDT events. This also > > automatically find the target binaries, e.g. > > > ># perf probe -a %sdt_libc:\* > > > > This example adds probes

Re: [GIT PULL] workqueue fixes for v4.6-rc5

On Wed, Apr 27, 2016 at 9:11 AM, Tejun Heo wrote: > > Unfortunately, we were missing a smp_rmb() after clearing PENDING for > execution, so nothing guaranteed visibility of the changes that a > queueing loser has made, which manifested as a reproducible blk-mq > stall. That

Re: [GIT PULL] workqueue fixes for v4.6-rc5

On Wed, Apr 27, 2016 at 9:11 AM, Tejun Heo wrote: > > Unfortunately, we were missing a smp_rmb() after clearing PENDING for > execution, so nothing guaranteed visibility of the changes that a > queueing loser has made, which manifested as a reproducible blk-mq > stall. That explanation makes no

Re: [PATCH perf/core v4 01/19] perf probe: Use strbuf for making strings

On Tue, 26 Apr 2016 11:59:34 -0300 Arnaldo Carvalho de Melo wrote: > Em Tue, Apr 26, 2016 at 11:40:47PM +0900, Masami Hiramatsu escreveu: > > On Tue, 26 Apr 2016 10:36:57 -0300 > > Arnaldo Carvalho de Melo wrote: > > > > > Em Tue, Apr 26, 2016 at 06:02:11PM

Re: [PATCH perf/core v4 01/19] perf probe: Use strbuf for making strings

On Tue, 26 Apr 2016 11:59:34 -0300 Arnaldo Carvalho de Melo wrote: > Em Tue, Apr 26, 2016 at 11:40:47PM +0900, Masami Hiramatsu escreveu: > > On Tue, 26 Apr 2016 10:36:57 -0300 > > Arnaldo Carvalho de Melo wrote: > > > > > Em Tue, Apr 26, 2016 at 06:02:11PM +0900, Masami Hiramatsu escreveu: >

Re: [PATCH perf/core v5 14/15] perf probe: Allow wildcard for cached events

Oops, I missed to fix the SEGV bug. I'll fix it and resend as 5.1. Thanks, On Thu, 28 Apr 2016 03:39:17 +0900 Masami Hiramatsu wrote: > Allo glob wildcard for reusing cached/SDT events. This also > automatically find the target binaries, e.g. > > # perf probe -a

Re: [PATCH perf/core v5 14/15] perf probe: Allow wildcard for cached events

Oops, I missed to fix the SEGV bug. I'll fix it and resend as 5.1. Thanks, On Thu, 28 Apr 2016 03:39:17 +0900 Masami Hiramatsu wrote: > Allo glob wildcard for reusing cached/SDT events. This also > automatically find the target binaries, e.g. > > # perf probe -a %sdt_libc:\* > > This

Re: livepatch: Add some basic LivePatch documentation

+++ Petr Mladek [25/04/16 17:14 +0200]: LivePatch framework deserves some documentation, definitely. This is an attempt to provide some basic info. I hope that it will be useful for both LivePatch producers and also potential developers of the framework itself. Signed-off-by: Petr Mladek

Re: livepatch: Add some basic LivePatch documentation

+++ Petr Mladek [25/04/16 17:14 +0200]: LivePatch framework deserves some documentation, definitely. This is an attempt to provide some basic info. I hope that it will be useful for both LivePatch producers and also potential developers of the framework itself. Signed-off-by: Petr Mladek

[PATCH perf/core v5 10/15] perf buildid-cache: Scan and import user SDT events to probe cache

From: Masami Hiramatsu perf buildid-cache --add scans given binary and add the SDT events to probe cache. "sdt_" prefix is appended for all SDT providers to avoid event-name clash with other pre-defined events. It is possible to use the cached SDT events as

Re: [PATCH V10 2/6] mfd: max77620: add core driver for MAX77620/MAX20024

On Wednesday 27 April 2016 08:49 PM, Lee Jones wrote: On Wed, 30 Mar 2016, Laxman Dewangan wrote: +#define MAX77620_MFD_CELL_RES(_name, _res) \ + { \ + .name = (_name),

[PATCH perf/core v5 09/15] perf probe: Add group name support

From: Masami Hiramatsu Allow user to set group name for adding new event. Note that user must ensure that the group name doesn't conflict with existing group name carefully. E.g. Existing group name can conflict with other events. Especially, using the group name

[PATCH perf/core v5 15/15] perf probe: Support @BUILDID or @FILE suffix for SDT events

Support @BUILDID or @FILE suffix for SDT events. This allows perf to add probes on SDTs/pre-cached events on given FILE or the file which has given BUILDID (also, this complements BUILDID.) For example, both gcc and libstdc++ has same SDTs as below. If you would like to add a probe on

[PATCH perf/core v5 14/15] perf probe: Allow wildcard for cached events

Allo glob wildcard for reusing cached/SDT events. This also automatically find the target binaries, e.g. # perf probe -a %sdt_libc:\* This example adds probes for all SDT in libc. Note that the SDTs must have been scanned by perf buildid-cache. Signed-off-by: Masami Hiramatsu

[PATCH perf/core v5 09/15] perf probe: Add group name support

From: Masami Hiramatsu Allow user to set group name for adding new event. Note that user must ensure that the group name doesn't conflict with existing group name carefully. E.g. Existing group name can conflict with other events. Especially, using the group name reserved for kernel modules can

[PATCH perf/core v5 15/15] perf probe: Support @BUILDID or @FILE suffix for SDT events

Support @BUILDID or @FILE suffix for SDT events. This allows perf to add probes on SDTs/pre-cached events on given FILE or the file which has given BUILDID (also, this complements BUILDID.) For example, both gcc and libstdc++ has same SDTs as below. If you would like to add a probe on

[PATCH perf/core v5 14/15] perf probe: Allow wildcard for cached events

Allo glob wildcard for reusing cached/SDT events. This also automatically find the target binaries, e.g. # perf probe -a %sdt_libc:\* This example adds probes for all SDT in libc. Note that the SDTs must have been scanned by perf buildid-cache. Signed-off-by: Masami Hiramatsu ---

[PATCH perf/core v5 10/15] perf buildid-cache: Scan and import user SDT events to probe cache

From: Masami Hiramatsu perf buildid-cache --add scans given binary and add the SDT events to probe cache. "sdt_" prefix is appended for all SDT providers to avoid event-name clash with other pre-defined events. It is possible to use the cached SDT events as other cached events, via perf probe

Re: [PATCH V10 2/6] mfd: max77620: add core driver for MAX77620/MAX20024

On Wednesday 27 April 2016 08:49 PM, Lee Jones wrote: On Wed, 30 Mar 2016, Laxman Dewangan wrote: +#define MAX77620_MFD_CELL_RES(_name, _res) \ + { \ + .name = (_name),

[PATCH perf/core v5 12/15] perf-list: Show SDT and pre-cached events

From: Masami Hiramatsu Show SDT and pre-cached events by perf-list with "sdt". This also shows the binary and build-id where the events are placed only when there are same name events on different binaries. e.g. # perf list sdt List of pre-defined

[PATCH v3] regulator: axp20x: Fix axp22x ldo_io registration error on cold boot

The maximum supported voltage for ldo_io# is 3.3V, but on cold boot the selector comes up at 0x1f, which maps to 3.8V. This causes _regulator_get_voltage() to fail with -EINVAL which causes regulator registration to fail when constrains are used: [1.467788] vcc-touchscreen: failed to get the

[PATCH perf/core v5 13/15] perf-list: Skip SDTs placed in invalid binaries

From: Masami Hiramatsu Skip SDTs placed in invalid (non-exist, or older version) binaries. Note that perf-probe --cache --list and perf-probe --cache --del still handle all the caches including invalid binaries. Signed-off-by: Masami Hiramatsu

[PATCH perf/core v5 12/15] perf-list: Show SDT and pre-cached events

From: Masami Hiramatsu Show SDT and pre-cached events by perf-list with "sdt". This also shows the binary and build-id where the events are placed only when there are same name events on different binaries. e.g. # perf list sdt List of pre-defined events (to be used in -e):

[PATCH v3] regulator: axp20x: Fix axp22x ldo_io registration error on cold boot

The maximum supported voltage for ldo_io# is 3.3V, but on cold boot the selector comes up at 0x1f, which maps to 3.8V. This causes _regulator_get_voltage() to fail with -EINVAL which causes regulator registration to fail when constrains are used: [1.467788] vcc-touchscreen: failed to get the

[PATCH perf/core v5 13/15] perf-list: Skip SDTs placed in invalid binaries

From: Masami Hiramatsu Skip SDTs placed in invalid (non-exist, or older version) binaries. Note that perf-probe --cache --list and perf-probe --cache --del still handle all the caches including invalid binaries. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu --- Changes in

[PATCH perf/core v5 11/15] perf probe: Accept %sdt and %cached event name

From: Masami Hiramatsu To improbe usability, support %[PROVIDER:]SDTEVENT format to add new probes on SDT and cached events. e.g. # perf probe -x /lib/libc-2.17.so %lll_lock_wait_private Added new event: sdt_libc:lll_lock_wait_private (on

[PATCH perf/core v5 11/15] perf probe: Accept %sdt and %cached event name

From: Masami Hiramatsu To improbe usability, support %[PROVIDER:]SDTEVENT format to add new probes on SDT and cached events. e.g. # perf probe -x /lib/libc-2.17.so %lll_lock_wait_private Added new event: sdt_libc:lll_lock_wait_private (on %lll_lock_wait_private in

[PATCH perf/core v5 06/15] perf probe: Show all cached probes

From: Masami Hiramatsu perf probe --list shows all cached probes when --cache is given. Each caches are shown with on which binary that probed. e.g. - # perf probe --cache vfs_read \$params # perf probe --cache -x /lib64/libc-2.17.so getaddrinfo

[PATCH perf/core v5 03/15] perf-buildid-cache: Use lsdir for looking up buildid caches

From: Masami Hiramatsu Use new lsdir() for looking up buildid caches. This changes logic a bit to ignore all dot files, since the build-id cache must not start with dot. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami

[PATCH perf/core v5 02/15] perf-buildid-cache: Use path/to/bin/buildid/elf instead of path/to/bin/buildid

From: Masami Hiramatsu Use path/to/bin/buildid/elf instead of path/to/bin/buildid to store corresponding elf binary. This also stores vdso in buildid/vdso, kallsyms in buildid/kallsyms. Note that the existing caches are not updated until user adds or updates the

[PATCH perf/core v5 05/15] perf probe: Use cache entry if possible

From: Masami Hiramatsu Before analyzing debuginfo, try to find a corresponding entry from probe cache always. This does not depend on --cache, the --cache enables to store/update cache, but looking up the cache is always enabled. Signed-off-by: Masami Hiramatsu

[PATCH perf/core v5 06/15] perf probe: Show all cached probes

From: Masami Hiramatsu perf probe --list shows all cached probes when --cache is given. Each caches are shown with on which binary that probed. e.g. - # perf probe --cache vfs_read \$params # perf probe --cache -x /lib64/libc-2.17.so getaddrinfo \$params # perf probe --cache --list

[PATCH perf/core v5 03/15] perf-buildid-cache: Use lsdir for looking up buildid caches

From: Masami Hiramatsu Use new lsdir() for looking up buildid caches. This changes logic a bit to ignore all dot files, since the build-id cache must not start with dot. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu --- tools/perf/util/build-id.c | 30

[PATCH perf/core v5 02/15] perf-buildid-cache: Use path/to/bin/buildid/elf instead of path/to/bin/buildid

From: Masami Hiramatsu Use path/to/bin/buildid/elf instead of path/to/bin/buildid to store corresponding elf binary. This also stores vdso in buildid/vdso, kallsyms in buildid/kallsyms. Note that the existing caches are not updated until user adds or updates the cache. Anyway, if there is the

[PATCH perf/core v5 05/15] perf probe: Use cache entry if possible

From: Masami Hiramatsu Before analyzing debuginfo, try to find a corresponding entry from probe cache always. This does not depend on --cache, the --cache enables to store/update cache, but looking up the cache is always enabled. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu

[PATCH perf/core v5 08/15] perf/sdt: ELF support for SDT

From: Hemant Kumar This patch serves the initial support to identify and list SDT events in binaries. When programs containing SDT markers are compiled, gcc with the help of assembler directives identifies them and places them in the section ".note.stapsdt". To find

[PATCH perf/core v5 07/15] perf probe: Remove caches when --cache is given

From: Masami Hiramatsu perf-probe --del removes caches when --cache is given. Note that the delete pattern is not same as normal events. If you cached probes with event name, --del "eventname" works as expected. However, if you skipped it, the cached probes

[PATCH perf/core v5 08/15] perf/sdt: ELF support for SDT

From: Hemant Kumar This patch serves the initial support to identify and list SDT events in binaries. When programs containing SDT markers are compiled, gcc with the help of assembler directives identifies them and places them in the section ".note.stapsdt". To find these markers from the

[PATCH perf/core v5 07/15] perf probe: Remove caches when --cache is given

From: Masami Hiramatsu perf-probe --del removes caches when --cache is given. Note that the delete pattern is not same as normal events. If you cached probes with event name, --del "eventname" works as expected. However, if you skipped it, the cached probes doesn't have actual event name. In

[PATCH perf/core v5 04/15] perf probe: Add --cache option to cache the probe definitions

From: Masami Hiramatsu Add --cache option to cache the probe definitions. This just saves the result of the dwarf analysis to probe cache. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu ---

[PATCH perf/core v5 04/15] perf probe: Add --cache option to cache the probe definitions

From: Masami Hiramatsu Add --cache option to cache the probe definitions. This just saves the result of the dwarf analysis to probe cache. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu --- Changes in v5: - Move probe_cache* definitions. (code cleanup) Changes in v4: -

[PATCH perf/core v5 01/15] perf probe: Use strbuf for making strings

From: Masami Hiramatsu Replace many fixed-length char array with strbuf to stringify perf_probe_event and probe_trace_event etc. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu --- Changes

[PATCH perf/core v5 01/15] perf probe: Use strbuf for making strings

From: Masami Hiramatsu Replace many fixed-length char array with strbuf to stringify perf_probe_event and probe_trace_event etc. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu --- Changes in v4: - Update for the latest kernel. - Remove "probe-event.c" from title and body,

[PATCH perf/core v5 00/15] perf-probe --cache and SDT support

Hi, Here is the 5th version of the patchset for probe-cache and initial SDT support which are going to be perf-cache finally. The previous version is here; https://lkml.org/lkml/2016/4/26/179 This version fixes a build bug on "make build-test", removed accepted patches, and fold buildid-cache

[PATCH perf/core v5 00/15] perf-probe --cache and SDT support

Hi, Here is the 5th version of the patchset for probe-cache and initial SDT support which are going to be perf-cache finally. The previous version is here; https://lkml.org/lkml/2016/4/26/179 This version fixes a build bug on "make build-test", removed accepted patches, and fold buildid-cache

Re: [PATCH v2 3/3] regulator: axp20x: Fix axp22x ldo_io registration error on cold boot

Hi, On 27-04-16 18:30, Mark Brown wrote: On Wed, Apr 27, 2016 at 06:04:53PM +0200, Hans de Goede wrote: On 27-04-16 17:48, Mark Brown wrote: Well, I guess someone can just measure what happens? What happens will likely depend on the pmic input voltage, which can be either 5V from a

Re: [PATCH v2 3/3] regulator: axp20x: Fix axp22x ldo_io registration error on cold boot

Hi, On 27-04-16 18:30, Mark Brown wrote: On Wed, Apr 27, 2016 at 06:04:53PM +0200, Hans de Goede wrote: On 27-04-16 17:48, Mark Brown wrote: Well, I guess someone can just measure what happens? What happens will likely depend on the pmic input voltage, which can be either 5V from a

Re: [PATCH] xfs: idle aild if the AIL is pushed up to the target LSN

Am Dienstag, den 26.04.2016, 09:08 +1000 schrieb Dave Chinner: [...] > > > > > > > > That said, I'm not sure whether there's a notable benefit of > > > idling > > > for > > > 50ms over just scheduling out when we've hit the target lsn. It > > > seems > > > like that anybody who pushes the target

Re: [PATCH] xfs: idle aild if the AIL is pushed up to the target LSN

Am Dienstag, den 26.04.2016, 09:08 +1000 schrieb Dave Chinner: [...] > > > > > > > > That said, I'm not sure whether there's a notable benefit of > > > idling > > > for > > > 50ms over just scheduling out when we've hit the target lsn. It > > > seems > > > like that anybody who pushes the target

[PATCH] locking/rwsem: Add reader-owned state to the owner field

This patch adds a new state RWSEM_READER_OWNED to the owner field to indicate that readers currently own the lock. This enables us to address the following 2 issues in the rwsem optimistic spinning code: 1) rwsem_can_spin_on_owner() will disallow optimistic spinning if the owner field is

[PATCH] locking/rwsem: Add reader-owned state to the owner field

This patch adds a new state RWSEM_READER_OWNED to the owner field to indicate that readers currently own the lock. This enables us to address the following 2 issues in the rwsem optimistic spinning code: 1) rwsem_can_spin_on_owner() will disallow optimistic spinning if the owner field is

Re: [PATCHv2] musb_host: fix lockup on rxcsr_h_error

2016-04-27 18:46 GMT+03:00 Bin Liu : > Hi, > > On Wed, Apr 27, 2016 at 09:51:58AM +0300, Max Uvarov wrote: >> Fix soft lockup when resetting remote device attached >> to usb host. Configuration: >> pppd -> musb hub -> usb-serial -> gsm modem > > I have heard a few reports similar to

Re: [PATCHv2] musb_host: fix lockup on rxcsr_h_error

2016-04-27 18:46 GMT+03:00 Bin Liu : > Hi, > > On Wed, Apr 27, 2016 at 09:51:58AM +0300, Max Uvarov wrote: >> Fix soft lockup when resetting remote device attached >> to usb host. Configuration: >> pppd -> musb hub -> usb-serial -> gsm modem > > I have heard a few reports similar to this symptom,

[PATCH] coresight: etb10: adjust read pointer only when needed

The read pointer (read_ptr) needs to be adjusted only if its value has gone beyond the length of the memory buffer. Reported-by: Suzuki K Poulose Signed-off-by: Mathieu Poirier --- drivers/hwtracing/coresight/coresight-etb10.c | 3 ++- 1 file

[PATCH] coresight: etb10: adjust read pointer only when needed

The read pointer (read_ptr) needs to be adjusted only if its value has gone beyond the length of the memory buffer. Reported-by: Suzuki K Poulose Signed-off-by: Mathieu Poirier --- drivers/hwtracing/coresight/coresight-etb10.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

Re: [BUG] x86/efi: MMRs no longer properly mapped after switch to isolated page table

On Wed, Apr 27, 2016 at 10:41:32AM -0500, Alex Thorlton wrote: Adding Boris to Cc. > Hey guys, > > We've hit an issue that we haven't seen before on recent community > kernels. Hoping that you can provide some insight. > > Late last week I hit this bad paging request in uv_system_init on one

Re: [BUG] x86/efi: MMRs no longer properly mapped after switch to isolated page table

On Wed, Apr 27, 2016 at 10:41:32AM -0500, Alex Thorlton wrote: Adding Boris to Cc. > Hey guys, > > We've hit an issue that we haven't seen before on recent community > kernels. Hoping that you can provide some insight. > > Late last week I hit this bad paging request in uv_system_init on one

Re: [PATCH] tty: provide tty_name() even without CONFIG_TTY

On 04/27/2016 10:24 AM, Arnd Bergmann wrote: > On Wednesday 27 April 2016 12:20:02 Paul Moore wrote: >>> diff --git a/include/linux/tty.h b/include/linux/tty.h >>> index 3b09f235db66..17b247c94440 100644 >>> --- a/include/linux/tty.h >>> +++ b/include/linux/tty.h >>> @@ -371,6 +371,7 @@ extern

Re: [PATCH] tty: provide tty_name() even without CONFIG_TTY

On 04/27/2016 10:24 AM, Arnd Bergmann wrote: > On Wednesday 27 April 2016 12:20:02 Paul Moore wrote: >>> diff --git a/include/linux/tty.h b/include/linux/tty.h >>> index 3b09f235db66..17b247c94440 100644 >>> --- a/include/linux/tty.h >>> +++ b/include/linux/tty.h >>> @@ -371,6 +371,7 @@ extern

Re: [RFC PATCH] lightnvm: expose configuration through sysfs

On 04/27/2016 07:41 PM, Greg KH wrote: On Wed, Apr 27, 2016 at 10:18:57AM -0700, Simon A. F. Lund wrote: --- a/include/linux/lightnvm.h +++ b/include/linux/lightnvm.h @@ -174,6 +174,7 @@ struct nvm_id_group { u16 cpar; struct nvm_id_lp_tbl lptbl; + struct kobject

Re: [RFC PATCH] lightnvm: expose configuration through sysfs

On 04/27/2016 07:41 PM, Greg KH wrote: On Wed, Apr 27, 2016 at 10:18:57AM -0700, Simon A. F. Lund wrote: --- a/include/linux/lightnvm.h +++ b/include/linux/lightnvm.h @@ -174,6 +174,7 @@ struct nvm_id_group { u16 cpar; struct nvm_id_lp_tbl lptbl; + struct kobject

[PATCH v3 0/7] drm: Add fbdev deferred io support to helpers

This patchset adds fbdev deferred io support to drm_fb_helper and drm_fb_cma_helper. It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage through the (struct drm_framebuffer_funcs)->dirty callback on the fb_helper framebuffer which will always run in process context. I have

Re: [PATCH V2 RFC] fixup! virtio: convert to use DMA api

On Wed, Apr 27, 2016 at 04:15:35PM +0100, David Woodhouse wrote: > On Wed, 2016-04-27 at 18:05 +0300, Michael S. Tsirkin wrote: > > > > I really don't get it. > > > > There's exactly one device that works now and needs the work-around and > > so that we need to support, and that is virtio. It

[PATCH v3 6/7] drm/qxl: Use drm_fb_helper deferred_io support

Use the fbdev deferred io support in drm_fb_helper which mirrors the one qxl has had. This patch has only been compile tested. Signed-off-by: Noralf Trønnes --- Changes since v2: - The drm_clip_rect_{width/height} functions are dropped, so open code it Changes since v1: -

[PATCH v3 0/7] drm: Add fbdev deferred io support to helpers

This patchset adds fbdev deferred io support to drm_fb_helper and drm_fb_cma_helper. It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage through the (struct drm_framebuffer_funcs)->dirty callback on the fb_helper framebuffer which will always run in process context. I have

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