[tip:perf/urgent] trace_kprobe: Remove warning message "Could not insert probe at..."

Commit-ID: 5c8dad48e4f53d6fd0a7e4f95d7c1c983374de88 Gitweb: https://git.kernel.org/tip/5c8dad48e4f53d6fd0a7e4f95d7c1c983374de88 Author: Song Liu AuthorDate: Fri, 13 Apr 2018 11:55:13 -0700 Committer: Ingo Molnar CommitDate: Tue, 17 Apr 2018

[tip:perf/urgent] trace_kprobe: Remove warning message "Could not insert probe at..."

Commit-ID: 5c8dad48e4f53d6fd0a7e4f95d7c1c983374de88 Gitweb: https://git.kernel.org/tip/5c8dad48e4f53d6fd0a7e4f95d7c1c983374de88 Author: Song Liu AuthorDate: Fri, 13 Apr 2018 11:55:13 -0700 Committer: Ingo Molnar CommitDate: Tue, 17 Apr 2018 07:54:57 +0200 trace_kprobe: Remove warning

Re: [PATCH 0/3] clk: add duty cycle support

Quoting Jerome Brunet (2018-04-16 10:57:40) > This patchset adds the possibility to control the duty cycle ratio of a > clock within the clock framework. > > This useful when the duty cycle ratio depends on another parameter > controlled by the clock framework. For example, the duty cycle ratio

Re: [PATCH 0/3] clk: add duty cycle support

Quoting Jerome Brunet (2018-04-16 10:57:40) > This patchset adds the possibility to control the duty cycle ratio of a > clock within the clock framework. > > This useful when the duty cycle ratio depends on another parameter > controlled by the clock framework. For example, the duty cycle ratio

[PATCH 2/3] KVM: X86: Allow userspace to disable ioport intercept

From: Wanpeng Li Allow to disable ioport intercept by userspace. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Tim Shearer Cc: Liran Alon Signed-off-by: Wanpeng Li

[PATCH 1/3] KVM: VMX: Introduce per-VM I/O permission bitmaps

From: Wanpeng Li This patch introduces per-VM I/O permission bitmaps, it will be used by later patches. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Tim Shearer Cc: Liran Alon

[PATCH 3/3] KVM: VMX: Allow I/O port 0x80 bypass when userspace prefer

From: Wanpeng Li Tim Shearer reported that "There is a guest which is running a packet forwarding app based on the DPDK (dpdk.org). The packet receive routine writes to 0xc070 using glibc's "outw_p" function which does an additional write to I/O port 80. It does this

[PATCH 1/3] KVM: VMX: Introduce per-VM I/O permission bitmaps

From: Wanpeng Li This patch introduces per-VM I/O permission bitmaps, it will be used by later patches. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Tim Shearer Cc: Liran Alon Signed-off-by: Wanpeng Li --- arch/x86/kvm/vmx.c | 34 +++--- 1 file changed, 31

[PATCH 3/3] KVM: VMX: Allow I/O port 0x80 bypass when userspace prefer

From: Wanpeng Li Tim Shearer reported that "There is a guest which is running a packet forwarding app based on the DPDK (dpdk.org). The packet receive routine writes to 0xc070 using glibc's "outw_p" function which does an additional write to I/O port 80. It does this write for every packet

[PATCH 2/3] KVM: X86: Allow userspace to disable ioport intercept

From: Wanpeng Li Allow to disable ioport intercept by userspace. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Tim Shearer Cc: Liran Alon Signed-off-by: Wanpeng Li --- Documentation/virtual/kvm/api.txt | 11 +++ arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/kvm/x86.c

[PATCH 0/3] KVM: VMX: Allow to disable ioport intercept per-VM by userspace

Tim Shearer reported that "There is a guest which is running a packet forwarding app based on the DPDK (dpdk.org). The packet receive routine writes to 0xc070 using glibc's "outw_p" function which does an additional write to I/O port 0x80. It does this write for every packet that's received,

[PATCH 0/3] KVM: VMX: Allow to disable ioport intercept per-VM by userspace

Tim Shearer reported that "There is a guest which is running a packet forwarding app based on the DPDK (dpdk.org). The packet receive routine writes to 0xc070 using glibc's "outw_p" function which does an additional write to I/O port 0x80. It does this write for every packet that's received,

Re: [PATCH 1/3] clk: add duty cycle support

Quoting Jerome Brunet (2018-04-16 10:57:41) > diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c > index 7af555f0e60c..fff7890ae355 100644 > --- a/drivers/clk/clk.c > +++ b/drivers/clk/clk.c > @@ -68,6 +68,8 @@ struct clk_core { > unsigned long max_rate; > unsigned long

Re: [PATCH 1/3] clk: add duty cycle support

Quoting Jerome Brunet (2018-04-16 10:57:41) > diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c > index 7af555f0e60c..fff7890ae355 100644 > --- a/drivers/clk/clk.c > +++ b/drivers/clk/clk.c > @@ -68,6 +68,8 @@ struct clk_core { > unsigned long max_rate; > unsigned long

Re: [PATCH 4/7] ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

On 17/04/18 12:09, Alastair D'Silva wrote: From: Alastair D'Silva The function removes the process element from NPU cache. Signed-off-by: Alastair D'Silva Hmm, personally I'd suggest pnv_ocxl_spa_clear_cache() because it's just a wrapper around

Re: [PATCH 4/7] ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action

On 17/04/18 12:09, Alastair D'Silva wrote: From: Alastair D'Silva The function removes the process element from NPU cache. Signed-off-by: Alastair D'Silva Hmm, personally I'd suggest pnv_ocxl_spa_clear_cache() because it's just a wrapper around the OPAL call of a similar name. But I

Re: [PATCH 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

On Tue, 2018-04-17 at 14:21 +1000, Andrew Donnellan wrote: > On 17/04/18 12:09, Alastair D'Silva wrote: > > From: Alastair D'Silva > > > > Switch the use of TIDR on it's CPU feature, rather than assuming it > > is available based on architecture. > > > > Signed-off-by:

Re: [PATCH 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

On Tue, 2018-04-17 at 14:21 +1000, Andrew Donnellan wrote: > On 17/04/18 12:09, Alastair D'Silva wrote: > > From: Alastair D'Silva > > > > Switch the use of TIDR on it's CPU feature, rather than assuming it > > is available based on architecture. > > > > Signed-off-by: Alastair D'Silva > >

Re: [lustre-devel] [PATCH 1/6] staging: lustre: move stack-check macros to libcfs_debug.h

On Apr 16, 2018, at 16:48, Doug Oucharek wrote: > >> >> On Apr 16, 2018, at 3:42 PM, James Simmons wrote: >> >> >>> James, >>> >>> If I understand correctly, you're saying you want to be able to build >>> without debug support...? I'm not

Re: [lustre-devel] [PATCH 1/6] staging: lustre: move stack-check macros to libcfs_debug.h

On Apr 16, 2018, at 16:48, Doug Oucharek wrote: > >> >> On Apr 16, 2018, at 3:42 PM, James Simmons wrote: >> >> >>> James, >>> >>> If I understand correctly, you're saying you want to be able to build >>> without debug support...? I'm not convinced that building a client without >>>

Re: [PATCH] security: remove security_settime

On Sun, 1 Apr 2018, Sargun Dhillon wrote: > security_settime was a wrapper around security_settime64. There are no more > users of it. Therefore it can be removed. It was removed in: > commit 4eb1bca17933 ("time: Use do_settimeofday64() internally") > > Signed-off-by: Sargun Dhillon

Re: [PATCH] security: remove security_settime

On Sun, 1 Apr 2018, Sargun Dhillon wrote: > security_settime was a wrapper around security_settime64. There are no more > users of it. Therefore it can be removed. It was removed in: > commit 4eb1bca17933 ("time: Use do_settimeofday64() internally") > > Signed-off-by: Sargun Dhillon Applied to

[PATCH] usb: always build usb/common/ targets; fixes extcon-axp288 build error

From: Randy Dunlap The extcon-axp288 driver selects USB_ROLE_SWITCH, but the USB Makefile does not currently build drivers/usb/common/ (where USB_ROLE_SWITCH code is) unless USB_COMMON is set, so modify the USB Makefile to always descend into drivers/usb/common/ to build

[PATCH] usb: always build usb/common/ targets; fixes extcon-axp288 build error

From: Randy Dunlap The extcon-axp288 driver selects USB_ROLE_SWITCH, but the USB Makefile does not currently build drivers/usb/common/ (where USB_ROLE_SWITCH code is) unless USB_COMMON is set, so modify the USB Makefile to always descend into drivers/usb/common/ to build its configured targets.

Re: [PATCH 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On 4/17/2018 8:39 AM, Anshuman Khandual wrote: On 04/16/2018 05:39 PM, Chintan Pandya wrote: On 4/13/2018 5:31 PM, Anshuman Khandual wrote: On 04/13/2018 05:03 PM, Chintan Pandya wrote: Client can call vunmap with some intermediate 'addr' which may not be the start of the VM area. Entire

Re: [PATCH 2/2] mm: vmalloc: Pass proper vm_start into debugobjects

On 4/17/2018 8:39 AM, Anshuman Khandual wrote: On 04/16/2018 05:39 PM, Chintan Pandya wrote: On 4/13/2018 5:31 PM, Anshuman Khandual wrote: On 04/13/2018 05:03 PM, Chintan Pandya wrote: Client can call vunmap with some intermediate 'addr' which may not be the start of the VM area. Entire

[PATCH] staging: bcm2835-audio: Disconnect and free vchi_instance on module_exit()

In the current implementation, vchi_instance is inited during the first call of bcm2835_audio_open_connection(), and is never freed. It causes a memory leak when the module `snd_bcm2835` is removed. Here is how this commit fixes it: * the VCHI context (including vchi_instance) is created once in

[PATCH] staging: bcm2835-audio: Disconnect and free vchi_instance on module_exit()

In the current implementation, vchi_instance is inited during the first call of bcm2835_audio_open_connection(), and is never freed. It causes a memory leak when the module `snd_bcm2835` is removed. Here is how this commit fixes it: * the VCHI context (including vchi_instance) is created once in

[PATCH 4/4] ASoC: amd: enabling bt i2s config after acp reset

On ST/CZ based platforms, for specific platform bt uart mux to be defined for bt i2s. By default, these pins will be used for uart. After acp reset , it requires to reprogram bt i2s config mux pins to enable bt i2s instance. added bt i2s enablement sequence during acp init. Signed-off-by:

[PATCH 4/4] ASoC: amd: enabling bt i2s config after acp reset

On ST/CZ based platforms, for specific platform bt uart mux to be defined for bt i2s. By default, these pins will be used for uart. After acp reset , it requires to reprogram bt i2s config mux pins to enable bt i2s instance. added bt i2s enablement sequence during acp init. Signed-off-by:

[PATCH 2/4] ASoC: amd: fixed checkpatch pl warnings

fixed checkpatch pl warnings. Signed-off-by: Vijendar Mukunda --- sound/soc/amd/acp-pcm-dma.c | 259 sound/soc/amd/acp.h | 22 ++-- 2 files changed, 153 insertions(+), 128 deletions(-) diff --git

[PATCH 2/4] ASoC: amd: fixed checkpatch pl warnings

fixed checkpatch pl warnings. Signed-off-by: Vijendar Mukunda --- sound/soc/amd/acp-pcm-dma.c | 259 sound/soc/amd/acp.h | 22 ++-- 2 files changed, 153 insertions(+), 128 deletions(-) diff --git a/sound/soc/amd/acp-pcm-dma.c

[PATCH 3/4] ASoC: amd: dma driver changes for BT I2S instance

With in ACP, There are three I2S controllers can be configured/enabled ( I2S SP, I2S MICSP, I2S BT). Default enabled I2S controller instance is I2S SP. This patch provides required changes to support I2S BT controller Instance. Signed-off-by: Vijendar Mukunda ---

[PATCH 3/4] ASoC: amd: dma driver changes for BT I2S instance

With in ACP, There are three I2S controllers can be configured/enabled ( I2S SP, I2S MICSP, I2S BT). Default enabled I2S controller instance is I2S SP. This patch provides required changes to support I2S BT controller Instance. Signed-off-by: Vijendar Mukunda --- sound/soc/amd/Kconfig |

[PATCH 1/4] ASoC: dwc: I2S Controller instance param added

When multiple I2S controller instances created, i2s_instance parameter refers to i2s controller instance value. Signed-off-by: Vijendar Mukunda Reviewed-by: Alex Deucher --- include/sound/designware_i2s.h | 6 ++ sound/soc/dwc/dwc-i2s.c

[PATCH 1/4] ASoC: dwc: I2S Controller instance param added

When multiple I2S controller instances created, i2s_instance parameter refers to i2s controller instance value. Signed-off-by: Vijendar Mukunda Reviewed-by: Alex Deucher --- include/sound/designware_i2s.h | 6 ++ sound/soc/dwc/dwc-i2s.c| 1 + sound/soc/dwc/local.h | 1 + 3

Re: [PATCH 2/2] parisc: use the asm-generic version for readX()

Hi Sinan, Thank you for the patch! Yet something to improve: [auto build test ERROR on hp-parisc/for-next] [also build test ERROR on v4.17-rc1 next-20180416] [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

Re: [PATCH 2/2] parisc: use the asm-generic version for readX()

Hi Sinan, Thank you for the patch! Yet something to improve: [auto build test ERROR on hp-parisc/for-next] [also build test ERROR on v4.17-rc1 next-20180416] [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

Re: [PATCH] blk-mq: start request gstate with gen 1

On Tue, Apr 17, 2018 at 11:46:20AM +0800, Jianchao Wang wrote: > rq->gstate and rq->aborted_gstate both are zero before rqs are > allocated. If we have a small timeout, when the timer fires, > there could be rqs that are never allocated, and also there could > be rq that has been allocated but not

Re: [PATCH] blk-mq: start request gstate with gen 1

On Tue, Apr 17, 2018 at 11:46:20AM +0800, Jianchao Wang wrote: > rq->gstate and rq->aborted_gstate both are zero before rqs are > allocated. If we have a small timeout, when the timer fires, > there could be rqs that are never allocated, and also there could > be rq that has been allocated but not

[PATCH] x86/headers/UAPI: Move DISABLE_EXITS KVM capability bits to the UAPI

Move DISABLE_EXITS KVM capability bits to the UAPI just like the rest of capabilities. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Thomas Gleixner Cc: Ingo Molnar Cc: H. Peter Anvin Cc: x...@kernel.org

[PATCH] x86/headers/UAPI: Move DISABLE_EXITS KVM capability bits to the UAPI

Move DISABLE_EXITS KVM capability bits to the UAPI just like the rest of capabilities. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Thomas Gleixner Cc: Ingo Molnar Cc: H. Peter Anvin Cc: x...@kernel.org Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed ---

Re: [PATCH v4 3/3] clk: qcom: Add Global Clock controller (GCC) driver for SDM845

Quoting Amit Nischal (2018-04-08 23:14:53) > From: Taniya Das > > Add support for the global clock controller found on SDM845 > based devices. This should allow most non-multimedia device > drivers to probe and control their clocks. > > Signed-off-by: Taniya Das

Re: [PATCH v4 3/3] clk: qcom: Add Global Clock controller (GCC) driver for SDM845

Quoting Amit Nischal (2018-04-08 23:14:53) > From: Taniya Das > > Add support for the global clock controller found on SDM845 > based devices. This should allow most non-multimedia device > drivers to probe and control their clocks. > > Signed-off-by: Taniya Das > Signed-off-by: Amit Nischal

Re: [PATCH v4 1/3] clk: qcom: Clear hardware clock control bit of RCG

Quoting Amit Nischal (2018-04-08 23:14:51) > For upcoming targets like sdm845, POR value of the hardware clock control > bit is set for most of root clocks which needs to be cleared for software > to be able to control. For older targets like MSM8996, this bit is reserved > bit and having POR

Re: [PATCH v4 1/3] clk: qcom: Clear hardware clock control bit of RCG

Quoting Amit Nischal (2018-04-08 23:14:51) > For upcoming targets like sdm845, POR value of the hardware clock control > bit is set for most of root clocks which needs to be cleared for software > to be able to control. For older targets like MSM8996, this bit is reserved > bit and having POR

[PATCH v3 0/9] trace_uprobe: Support SDT markers having reference count (semaphore)

Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. Applications like PostgreSQL, MySQL, Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc have these markers embedded in them. These markers are added by developer at important places

[PATCH v3 0/9] trace_uprobe: Support SDT markers having reference count (semaphore)

Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. Applications like PostgreSQL, MySQL, Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc have these markers embedded in them. These markers are added by developer at important places

[PATCH v3 5/9] Uprobe: Export uprobe_map_info along with uprobe_{build/free}_map_info()

From: Ravi Bangoria Given the file(inode) and offset, build_map_info() finds all existing mm that map the portion of file containing offset. Exporting these functions and data structure will help to use them in other set of files. Signed-off-by: Ravi Bangoria

[PATCH v3 5/9] Uprobe: Export uprobe_map_info along with uprobe_{build/free}_map_info()

From: Ravi Bangoria Given the file(inode) and offset, build_map_info() finds all existing mm that map the portion of file containing offset. Exporting these functions and data structure will help to use them in other set of files. Signed-off-by: Ravi Bangoria Reviewed-by: Jérôme Glisse ---

[PATCH v3 6/9] trace_uprobe: Support SDT markers having reference count (semaphore)

From: Ravi Bangoria Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. Applications like PostgreSQL, MySQL, Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc have these markers embedded in them. These

[PATCH v3 6/9] trace_uprobe: Support SDT markers having reference count (semaphore)

From: Ravi Bangoria Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. Applications like PostgreSQL, MySQL, Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc have these markers embedded in them. These markers are added by

[PATCH v3 9/9] perf probe: Support SDT markers having reference counter (semaphore)

From: Ravi Bangoria With this, perf buildid-cache will save SDT markers with reference counter in probe cache. Perf probe will be able to probe markers having reference counter. Ex, # readelf -n /tmp/tick | grep -A1 loop2 Name: loop2 ... Semaphore:

[PATCH v3 8/9] trace_uprobe/sdt: Document about reference counter

From: Ravi Bangoria Reference counter gate the invocation of probe. If present, by default reference count is 0. Kernel needs to increment it before tracing the probe and decrement it when done. This is identical to semaphore in Userspace Statically Defined

[PATCH v3 9/9] perf probe: Support SDT markers having reference counter (semaphore)

From: Ravi Bangoria With this, perf buildid-cache will save SDT markers with reference counter in probe cache. Perf probe will be able to probe markers having reference counter. Ex, # readelf -n /tmp/tick | grep -A1 loop2 Name: loop2 ... Semaphore: 0x10020036 # ./perf

[PATCH v3 8/9] trace_uprobe/sdt: Document about reference counter

From: Ravi Bangoria Reference counter gate the invocation of probe. If present, by default reference count is 0. Kernel needs to increment it before tracing the probe and decrement it when done. This is identical to semaphore in Userspace Statically Defined Tracepoints (USDT). Document usage of

[PATCH v3 7/9] trace_uprobe/sdt: Fix multiple update of same reference counter

From: Ravi Bangoria When virtual memory map for binary/library is being prepared, there is no direct one to one mapping between mmap() and virtual memory area. Ex, when loader loads the library, it first calls mmap(size = total_size), where total_size is addition of

[PATCH v3 7/9] trace_uprobe/sdt: Fix multiple update of same reference counter

From: Ravi Bangoria When virtual memory map for binary/library is being prepared, there is no direct one to one mapping between mmap() and virtual memory area. Ex, when loader loads the library, it first calls mmap(size = total_size), where total_size is addition of size of all elf sections that

[PATCH v3 3/9] Uprobe: Move mmput() into free_map_info()

From: Oleg Nesterov build_map_info() has a side effect like one need to perform mmput() when done with the mm. Add mmput() in free_map_info() so that user does not have to call it explicitly. Signed-off-by: Oleg Nesterov Signed-off-by: Ravi Bangoria

[PATCH v3 3/9] Uprobe: Move mmput() into free_map_info()

From: Oleg Nesterov build_map_info() has a side effect like one need to perform mmput() when done with the mm. Add mmput() in free_map_info() so that user does not have to call it explicitly. Signed-off-by: Oleg Nesterov Signed-off-by: Ravi Bangoria --- kernel/events/uprobes.c | 9 ++---

[PATCH v3 1/9] Uprobe: Export vaddr <-> offset conversion functions

From: Ravi Bangoria These are generic functions which operates on file offset and virtual address. Make these functions available outside of uprobe code so that other can use it as well. Signed-off-by: Ravi Bangoria Reviewed-by: Jérôme

[PATCH v3 1/9] Uprobe: Export vaddr <-> offset conversion functions

From: Ravi Bangoria These are generic functions which operates on file offset and virtual address. Make these functions available outside of uprobe code so that other can use it as well. Signed-off-by: Ravi Bangoria Reviewed-by: Jérôme Glisse --- include/linux/mm.h | 12

[PATCH v3 2/9] mm: Prefix vma_ to vaddr_to_offset() and offset_to_vaddr()

From: Ravi Bangoria Make function names more meaningful by adding vma_ prefix to them. Signed-off-by: Ravi Bangoria Reviewed-by: Jérôme Glisse --- include/linux/mm.h | 4 ++-- kernel/events/uprobes.c | 14

[PATCH v3 4/9] Uprobe: Rename map_info to uprobe_map_info

From: Ravi Bangoria map_info is very generic name, rename it to uprobe_map_info. Renaming will help to export this structure outside of the file. Also rename free_map_info() to uprobe_free_map_info() and build_map_info() to uprobe_build_map_info(). Signed-off-by:

[PATCH v3 4/9] Uprobe: Rename map_info to uprobe_map_info

From: Ravi Bangoria map_info is very generic name, rename it to uprobe_map_info. Renaming will help to export this structure outside of the file. Also rename free_map_info() to uprobe_free_map_info() and build_map_info() to uprobe_build_map_info(). Signed-off-by: Ravi Bangoria Reviewed-by:

[PATCH v3 2/9] mm: Prefix vma_ to vaddr_to_offset() and offset_to_vaddr()

From: Ravi Bangoria Make function names more meaningful by adding vma_ prefix to them. Signed-off-by: Ravi Bangoria Reviewed-by: Jérôme Glisse --- include/linux/mm.h | 4 ++-- kernel/events/uprobes.c | 14 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git

Re: [PATCH 1/2] parisc: use the asm-generic version for writeX()

Hi Sinan, Thank you for the patch! Yet something to improve: [auto build test ERROR on hp-parisc/for-next] [also build test ERROR on v4.17-rc1 next-20180416] [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

Re: [PATCH 1/2] parisc: use the asm-generic version for writeX()

Hi Sinan, Thank you for the patch! Yet something to improve: [auto build test ERROR on hp-parisc/for-next] [also build test ERROR on v4.17-rc1 next-20180416] [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

Re: [PATCH v2 3/3] clk: qcom: gdsc: Add support to poll CFG register to check GDSC state

Quoting Taniya Das (2018-04-09 01:41:46) > @@ -64,18 +69,43 @@ static int gdsc_hwctrl(struct gdsc *sc, bool en) > return regmap_update_bits(sc->regmap, sc->gdscr, HW_CONTROL_MASK, > val); > } > > +static int gdsc_is_enabled_by_poll_cfg_reg(struct gdsc *sc, bool en) > +{ > + u32

Re: [PATCH v2 3/3] clk: qcom: gdsc: Add support to poll CFG register to check GDSC state

Quoting Taniya Das (2018-04-09 01:41:46) > @@ -64,18 +69,43 @@ static int gdsc_hwctrl(struct gdsc *sc, bool en) > return regmap_update_bits(sc->regmap, sc->gdscr, HW_CONTROL_MASK, > val); > } > > +static int gdsc_is_enabled_by_poll_cfg_reg(struct gdsc *sc, bool en) > +{ > + u32

linux-next: Tree for Apr 17

Hi all, Changes since 20180416: The bpf tree lost its build failure. The netfilter tree gained a build failure for which I applied a patch. The sound-asoc tree gained a build failure so I used the version from next-20180416. The efi-lock-down tree gained a conflict against the modules tree

linux-next: Tree for Apr 17

Hi all, Changes since 20180416: The bpf tree lost its build failure. The netfilter tree gained a build failure for which I applied a patch. The sound-asoc tree gained a build failure so I used the version from next-20180416. The efi-lock-down tree gained a conflict against the modules tree

[PATCH RESEND net-next] net/ncsi: Refactor MAC, VLAN filters

The NCSI driver defines a generic ncsi_channel_filter struct that can be used to store arbitrarily formatted filters, and several generic methods of accessing data stored in such a filter. However in both the driver and as defined in the NCSI specification there are only two actual filters: VLAN

[PATCH RESEND net-next] net/ncsi: Refactor MAC, VLAN filters

The NCSI driver defines a generic ncsi_channel_filter struct that can be used to store arbitrarily formatted filters, and several generic methods of accessing data stored in such a filter. However in both the driver and as defined in the NCSI specification there are only two actual filters: VLAN

Re: [PATCH 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

On 17/04/18 12:09, Alastair D'Silva wrote: From: Alastair D'Silva Switch the use of TIDR on it's CPU feature, rather than assuming it is available based on architecture. Signed-off-by: Alastair D'Silva There's a use of TIDR in restore_sprs()

Re: [PATCH 2/7] powerpc: Use TIDR CPU feature to control TIDR allocation

On 17/04/18 12:09, Alastair D'Silva wrote: From: Alastair D'Silva Switch the use of TIDR on it's CPU feature, rather than assuming it is available based on architecture. Signed-off-by: Alastair D'Silva There's a use of TIDR in restore_sprs() that's behind the ARCH_300 flag as well,

[PATCH v2 3/3] perf/buildid-cache: Support --purge-all option

User can remove files from cache using --remove/--purge options but both needs list of files as an argument. It's not convenient when you want to flush out entire cache. Add an option to purge all files from cache. Ex, # perf buildid-cache -l 8a86ef73e44067bca52cc3f6cd3e5446c783391c

[PATCH v2 3/3] perf/buildid-cache: Support --purge-all option

User can remove files from cache using --remove/--purge options but both needs list of files as an argument. It's not convenient when you want to flush out entire cache. Add an option to purge all files from cache. Ex, # perf buildid-cache -l 8a86ef73e44067bca52cc3f6cd3e5446c783391c

[PATCH v2 1/3] tools/parse-options: Add '\n' at the end of error messages

Few error messages does not have '\n' at the end and thus next prompt gets printed in the same line. Ex, linux~$ perf buildid-cache -verbose --add ./a.out Error: did you mean `--verbose` (with two dashes ?)linux~$ Fix it. Signed-off-by: Ravi Bangoria

[PATCH v2 0/3] perf/buildid-cache: Add --list and --purge-all options

First patch is a trivial error message fix. Second and third adds new options --list and --purge-all to 'buildid-cache' subcommand. v2 changes: - [PATCH v2 2/3] Display optput of 'perf buildid-cache -l' same as 'perf buildid-list'. - [PATCH v2 2/3] Other minor changes as suggested by Jiri.

[PATCH v2 1/3] tools/parse-options: Add '\n' at the end of error messages

Few error messages does not have '\n' at the end and thus next prompt gets printed in the same line. Ex, linux~$ perf buildid-cache -verbose --add ./a.out Error: did you mean `--verbose` (with two dashes ?)linux~$ Fix it. Signed-off-by: Ravi Bangoria Reviewed-by: Masami Hiramatsu ---

[PATCH v2 0/3] perf/buildid-cache: Add --list and --purge-all options

First patch is a trivial error message fix. Second and third adds new options --list and --purge-all to 'buildid-cache' subcommand. v2 changes: - [PATCH v2 2/3] Display optput of 'perf buildid-cache -l' same as 'perf buildid-list'. - [PATCH v2 2/3] Other minor changes as suggested by Jiri.

[PATCH v2 2/3] perf/buildid-cache: Support --list option

Perf buildid-cache allows to add/remove files into cache but there is no option to list all cached files. Add --list option to list all _valid_ cached files. Ex, # perf buildid-cache --add /tmp/a.out # perf buildid-cache -l 8a86ef73e44067bca52cc3f6cd3e5446c783391c /tmp/a.out

[PATCH v2 2/3] perf/buildid-cache: Support --list option

Perf buildid-cache allows to add/remove files into cache but there is no option to list all cached files. Add --list option to list all _valid_ cached files. Ex, # perf buildid-cache --add /tmp/a.out # perf buildid-cache -l 8a86ef73e44067bca52cc3f6cd3e5446c783391c /tmp/a.out

Re: [PATCH v2 2/3] clk: qcom: gdsc: Add support to poll for higher timeout value

Quoting Taniya Das (2018-04-09 01:41:45) > From: Amit Nischal > > For some gdscs, it might take longer time up to 500us for updating their > status. Update the timeout value for all GDSC polling status. > > Signed-off-by: Amit Nischal >

Re: [PATCH v2 1/3] clk: qcom: gdsc: Add support to reset AON and block reset logic

Quoting Taniya Das (2018-04-09 01:41:44) > From: Amit Nischal > > For some of the gdsc power domains, there could be need to reset the > AON logic or assert/deassert the block control reset before removing > the clamp_io. Add support for the same by introducing new flags

Re: [PATCH v2 2/3] clk: qcom: gdsc: Add support to poll for higher timeout value

Quoting Taniya Das (2018-04-09 01:41:45) > From: Amit Nischal > > For some gdscs, it might take longer time up to 500us for updating their > status. Update the timeout value for all GDSC polling status. > > Signed-off-by: Amit Nischal > Signed-off-by: Taniya Das > --- Applied to clk-next

Re: [PATCH v2 1/3] clk: qcom: gdsc: Add support to reset AON and block reset logic

Quoting Taniya Das (2018-04-09 01:41:44) > From: Amit Nischal > > For some of the gdsc power domains, there could be need to reset the > AON logic or assert/deassert the block control reset before removing > the clamp_io. Add support for the same by introducing new flags > SW_RESET and

Re: [PATCH 1/2] parisc: use the asm-generic version for writeX()

On 4/16/2018 7:48 PM, Sinan Kaya wrote: > On 4/16/2018 7:44 PM, Sinan Kaya wrote: >>> John David Anglin  dave.ang...@bell.net >>> >>> >>> io.log >>> >>> >>> CC arch/parisc/kernel/asm-offsets.s >>> In file included from ./arch/parisc/include/asm/io.h:262:0, >>> from

Re: [PATCH 1/2] parisc: use the asm-generic version for writeX()

On 4/16/2018 7:48 PM, Sinan Kaya wrote: > On 4/16/2018 7:44 PM, Sinan Kaya wrote: >>> John David Anglin  dave.ang...@bell.net >>> >>> >>> io.log >>> >>> >>> CC arch/parisc/kernel/asm-offsets.s >>> In file included from ./arch/parisc/include/asm/io.h:262:0, >>> from

[RFC v4 0/4] Centralize and unify usage of preempt/irq tracepoints

Hello, This is the next revision of preempt/irq tracepoint centralization and unified usage across the kernel [1]. The preempt/irq tracepoints exist but not everything in the kernel is using it. This makes things not work simultaneously (for ex, only lockdep or irqsoff events can be used). This

[RFC v4 0/4] Centralize and unify usage of preempt/irq tracepoints

Hello, This is the next revision of preempt/irq tracepoint centralization and unified usage across the kernel [1]. The preempt/irq tracepoints exist but not everything in the kernel is using it. This makes things not work simultaneously (for ex, only lockdep or irqsoff events can be used). This

Re: [PATCH 1/7] powerpc: Add TIDR CPU feature for Power9

On 17/04/18 12:09, Alastair D'Silva wrote: diff --git a/arch/powerpc/include/asm/switch_to.h b/arch/powerpc/include/asm/switch_to.h index be8c9fa23983..5b03d8a82409 100644 --- a/arch/powerpc/include/asm/switch_to.h +++ b/arch/powerpc/include/asm/switch_to.h @@ -94,6 +94,5 @@ static inline void

Re: [PATCH 1/7] powerpc: Add TIDR CPU feature for Power9

On 17/04/18 12:09, Alastair D'Silva wrote: diff --git a/arch/powerpc/include/asm/switch_to.h b/arch/powerpc/include/asm/switch_to.h index be8c9fa23983..5b03d8a82409 100644 --- a/arch/powerpc/include/asm/switch_to.h +++ b/arch/powerpc/include/asm/switch_to.h @@ -94,6 +94,5 @@ static inline void

[RFC v4 3/4] irqflags: Avoid unnecessary calls to trace_ if you can

With TRACE_IRQFLAGS, we call trace_ API too many times. We don't need to if local_irq_restore or local_irq_save didn't actually do anything. This gives around a 4% improvement in performance when doing the following command: "time find / > /dev/null" Also its best to avoid these calls where

[RFC v4 3/4] irqflags: Avoid unnecessary calls to trace_ if you can

With TRACE_IRQFLAGS, we call trace_ API too many times. We don't need to if local_irq_restore or local_irq_save didn't actually do anything. This gives around a 4% improvement in performance when doing the following command: "time find / > /dev/null" Also its best to avoid these calls where

[PATCH v2 2/2] parisc: define stronger ordering for the default readX()

parisc architecture seems to be mapping readX() and readX_relaxed() APIs to __raw_readX() API. __raw_readX() API doesn't provide any kind of ordering guarantees. commit 032d59e1cde9 ("io: define stronger ordering for the default readX() implementation") changed asm-generic implementation to use a

[PATCH v2 2/2] parisc: define stronger ordering for the default readX()

parisc architecture seems to be mapping readX() and readX_relaxed() APIs to __raw_readX() API. __raw_readX() API doesn't provide any kind of ordering guarantees. commit 032d59e1cde9 ("io: define stronger ordering for the default readX() implementation") changed asm-generic implementation to use a

[PATCH v2 1/2] parisc: define stronger ordering for the default writeX()

parisc architecture seems to be mapping writeX() and writeX_relaxed() APIs to __raw_writeX() API. __raw_writeX() API doesn't provide any kind of ordering guarantees. commit 755bd04aaf4b ("io: define stronger ordering for the default writeX() implementation") changed asm-generic implementation to

[PATCH v2 1/2] parisc: define stronger ordering for the default writeX()

parisc architecture seems to be mapping writeX() and writeX_relaxed() APIs to __raw_writeX() API. __raw_writeX() API doesn't provide any kind of ordering guarantees. commit 755bd04aaf4b ("io: define stronger ordering for the default writeX() implementation") changed asm-generic implementation to

  1   2   3   4   5   6   7   8   9   10   >