Re: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Wed, Jun 15, 2016 at 09:32:35PM +0300, Netanel Belgazal wrote: > I removed HAVE_NETDEV_NAPI_LIST and fixed the ena print macro. > I'll wait a bit to see if there are additional comment before I'll send the > v2 patch. Also, please don't top post (reply inline) and send emails as plain text

Re: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Wed, Jun 15, 2016 at 09:32:35PM +0300, Netanel Belgazal wrote: > I removed HAVE_NETDEV_NAPI_LIST and fixed the ena print macro. > I'll wait a bit to see if there are additional comment before I'll send the > v2 patch. Also, please don't top post (reply inline) and send emails as plain text

Re: [PATCH v2 00/13] Runtime PM for Thunderbolt on Macs

[+cc Linus, Greg KH] On Tue, Jun 14, 2016 at 03:22:28PM -0500, Bjorn Helgaas wrote: > On Tue, Jun 14, 2016 at 09:14:27PM +0200, Andreas Noever wrote: > > On Tue, Jun 14, 2016 at 6:37 PM, Bjorn Helgaas wrote: > > > On Sat, May 21, 2016 at 11:48:42AM +0200, Andreas Noever

Re: [PATCH v2 00/13] Runtime PM for Thunderbolt on Macs

[+cc Linus, Greg KH] On Tue, Jun 14, 2016 at 03:22:28PM -0500, Bjorn Helgaas wrote: > On Tue, Jun 14, 2016 at 09:14:27PM +0200, Andreas Noever wrote: > > On Tue, Jun 14, 2016 at 6:37 PM, Bjorn Helgaas wrote: > > > On Sat, May 21, 2016 at 11:48:42AM +0200, Andreas Noever wrote: > > > > On Fri,

[PATCH] selftests/exec: Makefile is a run-time dependency, add it to the install list

The execveat test try to exec the Makefile file and expect an EACCES results. When running the test in the installed destination it would fail with ENOENT since the file is not there. Add Makefile to the TEST_FILES list so it's copied at install time. Signed-off-by: Yannick Brosseau

[PATCH] selftests/exec: Makefile is a run-time dependency, add it to the install list

The execveat test try to exec the Makefile file and expect an EACCES results. When running the test in the installed destination it would fail with ENOENT since the file is not there. Add Makefile to the TEST_FILES list so it's copied at install time. Signed-off-by: Yannick Brosseau ---

[PATCH v2 1/3] net: stmmac: allow to split suspend/resume from init/exit callbacks

Let the stmmac platform drivers provide dedicated suspend and resume callbacks rather than always re-using the init and exits callbacks. If the driver does not provide the suspend or resume callback, we fall back to the old behavior trying to use exit or init. This allows a specific platform to

[PATCH v2 3/3] ARM: dts: rockchip: add interrupt for Wake-on-Lan on RK3288

In order to use Wake-on-Lan on RK3288 integrated MAC, we need to wake-up the CPU on the PMT interrupt when the MAC and the PHY are in low power mode. Adding the interrupt declaration. Signed-off-by: Vincent Palatin --- arch/arm/boot/dts/rk3288.dtsi | 5 +++-- 1 file

[PATCH v2 1/3] net: stmmac: allow to split suspend/resume from init/exit callbacks

Let the stmmac platform drivers provide dedicated suspend and resume callbacks rather than always re-using the init and exits callbacks. If the driver does not provide the suspend or resume callback, we fall back to the old behavior trying to use exit or init. This allows a specific platform to

[PATCH v2 3/3] ARM: dts: rockchip: add interrupt for Wake-on-Lan on RK3288

In order to use Wake-on-Lan on RK3288 integrated MAC, we need to wake-up the CPU on the PMT interrupt when the MAC and the PHY are in low power mode. Adding the interrupt declaration. Signed-off-by: Vincent Palatin --- arch/arm/boot/dts/rk3288.dtsi | 5 +++-- 1 file changed, 3 insertions(+), 2

[PATCH v2 2/3] net: stmmac: dwmac-rk: keep the PHY up for WoL

When suspending the machine, do not shutdown the external PHY by cutting its regulator in the mac platform driver suspend code if Wake-on-Lan is enabled, else it cannot wake us up. In order to do this, split the suspend/resume callbacks from the init/exit callbacks, so we can condition the

[PATCH v2 2/3] net: stmmac: dwmac-rk: keep the PHY up for WoL

When suspending the machine, do not shutdown the external PHY by cutting its regulator in the mac platform driver suspend code if Wake-on-Lan is enabled, else it cannot wake us up. In order to do this, split the suspend/resume callbacks from the init/exit callbacks, so we can condition the

[PATCH v2 0/3] net: stmmac: dwmac-rk: fixes for Wake-on-Lan on RK3288

In order to support Wake-On-Lan when using the RK3288 integrated MAC (with an external RGMII PHY), we need to avoid shutting down the regulator of the external PHY when the MAC is suspended as it's currently done in the MAC platform code. As a first step, create independant callbacks for

Re: [PATCH 4/5] nvmet-rdma: add a NVMe over Fabrics RDMA target driver

Looking at rdma_destroy_id(), I think it is invalid to call it from the event handler: ... So I withdraw my comment about nvmet. I think the code is fine as-is. The 2nd reject results in a no-op since the connection request was rejected by nvmet. I was just catching up on this after a

[PATCH v2 0/3] net: stmmac: dwmac-rk: fixes for Wake-on-Lan on RK3288

In order to support Wake-On-Lan when using the RK3288 integrated MAC (with an external RGMII PHY), we need to avoid shutting down the regulator of the external PHY when the MAC is suspended as it's currently done in the MAC platform code. As a first step, create independant callbacks for

Re: [PATCH 4/5] nvmet-rdma: add a NVMe over Fabrics RDMA target driver

Looking at rdma_destroy_id(), I think it is invalid to call it from the event handler: ... So I withdraw my comment about nvmet. I think the code is fine as-is. The 2nd reject results in a no-op since the connection request was rejected by nvmet. I was just catching up on this after a

[PATCH 3/3] acpi spi: Initialize modalias from of_compatible

When using devicetree spi_device.modalias is set to the compatible string with the vendor prefix removed. For SPI devices described via ACPI the i2c_board_info.type string is initialized by acpi_device_hid. When using ACPI and DT ids this string ends up something like "PRP0001". Change

[PATCH 3/3] acpi spi: Initialize modalias from of_compatible

When using devicetree spi_device.modalias is set to the compatible string with the vendor prefix removed. For SPI devices described via ACPI the i2c_board_info.type string is initialized by acpi_device_hid. When using ACPI and DT ids this string ends up something like "PRP0001". Change

[PATCH 2/3] acpi i2c: Initialize info.type from of_compatible

When using devicetree i2c_board_info.type is set to the compatible string with the vendor prefix removed. For I2C devices described via ACPI the i2c_board_info.type string is set to the ACPI device name. When using ACPI and DT ids this string ends up something like "PRP0001:00". If the

[PATCH 1/3] acpi: Export acpi_of_modalias equiv of of_modalias_node

When using devicetree stuff like i2c_client.name or spi_device.modalias is initialized to the first DT compatible id with the vendor prefix stripped. Since some drivers rely on this try to replicate it when using ACPI with DT ids. Signed-off-by: Crestez Dan Leonard ---

[PATCH 0/3] Init device ids from ACPI of_compatible

When using devicetree stuff like i2c_client.name or spi_device.modalias is initialized to the first DT compatible id with the vendor prefix stripped. Since some drivers rely on this try to replicate it when using ACPI with DT ids. Drivers rely on these ids in order to differentiate between

[PATCH 2/3] acpi i2c: Initialize info.type from of_compatible

When using devicetree i2c_board_info.type is set to the compatible string with the vendor prefix removed. For I2C devices described via ACPI the i2c_board_info.type string is set to the ACPI device name. When using ACPI and DT ids this string ends up something like "PRP0001:00". If the

[PATCH 1/3] acpi: Export acpi_of_modalias equiv of of_modalias_node

When using devicetree stuff like i2c_client.name or spi_device.modalias is initialized to the first DT compatible id with the vendor prefix stripped. Since some drivers rely on this try to replicate it when using ACPI with DT ids. Signed-off-by: Crestez Dan Leonard --- drivers/acpi/bus.c |

[PATCH 0/3] Init device ids from ACPI of_compatible

When using devicetree stuff like i2c_client.name or spi_device.modalias is initialized to the first DT compatible id with the vendor prefix stripped. Since some drivers rely on this try to replicate it when using ACPI with DT ids. Drivers rely on these ids in order to differentiate between

Re: [PATCHv2] arm64: Handle el1 synchronous instruction aborts cleanly

On 06/15/2016 04:00 AM, Mark Rutland wrote: Hi Laura, On Tue, Jun 14, 2016 at 11:00:35AM -0700, Laura Abbott wrote: Executing from a non-executable area gives an ugly message: lkdtm: Performing direct entry EXEC_RODATA lkdtm: attempting ok execution at 084c0e08 lkdtm: attempting bad

Re: [PATCHv2] arm64: Handle el1 synchronous instruction aborts cleanly

On 06/15/2016 04:00 AM, Mark Rutland wrote: Hi Laura, On Tue, Jun 14, 2016 at 11:00:35AM -0700, Laura Abbott wrote: Executing from a non-executable area gives an ugly message: lkdtm: Performing direct entry EXEC_RODATA lkdtm: attempting ok execution at 084c0e08 lkdtm: attempting bad

Re: [RFC PATCH-tip v2 1/6] locking/osq: Make lock/unlock proper acquire/release barrier

On Wed, 15 Jun 2016, Peter Zijlstra wrote: In any case, its fairly simple to cure, just add smp_acquire__after_ctrl_dep() at the end. If we bail because need_resched() we don't need the acquire I think. I was just considering this for your smp_cond_acquire/smp_cond_load_acquire rework, so

Re: [RFC PATCH-tip v2 1/6] locking/osq: Make lock/unlock proper acquire/release barrier

On Wed, 15 Jun 2016, Peter Zijlstra wrote: In any case, its fairly simple to cure, just add smp_acquire__after_ctrl_dep() at the end. If we bail because need_resched() we don't need the acquire I think. I was just considering this for your smp_cond_acquire/smp_cond_load_acquire rework, so

Re: scripts: add glimpse.sh for indexing the kernel

> http://webglimpse.net/ > Its vaguely mentioned there. That's as good as it gets... How do you think about to insert the date "2014-09-26" into your commit message? >> https://github.com/gvelez17/glimpse/ > Sadly the original release didn't compile, I reported the issue in hopes it > would >

Re: scripts: add glimpse.sh for indexing the kernel

> http://webglimpse.net/ > Its vaguely mentioned there. That's as good as it gets... How do you think about to insert the date "2014-09-26" into your commit message? >> https://github.com/gvelez17/glimpse/ > Sadly the original release didn't compile, I reported the issue in hopes it > would >

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 11:12:37AM -0700, Andy Lutomirski wrote: > I want to see actual_problem in the log. So the optimal thing to do for that is to return an error to the calling site which says "exception got handled" and then the *calling* site can dump_stack(). And the old code did that:

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 11:12:37AM -0700, Andy Lutomirski wrote: > I want to see actual_problem in the log. So the optimal thing to do for that is to return an error to the calling site which says "exception got handled" and then the *calling* site can dump_stack(). And the old code did that:

initialize a mutex into locked state?

Hello! To my surprise I found out that it's not possible to initialise a mutex into a locked state. I discussed it with Arjan and apparently there's no fundamental reason not to allow this. A typical use would be when you have a structure that you need to init and then add to some

initialize a mutex into locked state?

Hello! To my surprise I found out that it's not possible to initialise a mutex into a locked state. I discussed it with Arjan and apparently there's no fundamental reason not to allow this. A typical use would be when you have a structure that you need to init and then add to some

Re: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Wed, Jun 15, 2016 at 11:07:17AM -0700, Matt Wilson wrote: > > You also had a few typos in the email addresses on the Cc: line that > I've corrected (d...@avemeloft.net -> da...@davemeloft.net, Argh, and of course I typo'ed the correction. -> da...@davemloft.net. --msw

Re: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Wed, Jun 15, 2016 at 11:07:17AM -0700, Matt Wilson wrote: > > You also had a few typos in the email addresses on the Cc: line that > I've corrected (d...@avemeloft.net -> da...@davemeloft.net, Argh, and of course I typo'ed the correction. -> da...@davemloft.net. --msw

Re: stack validation warning on lttng-modules bytecode interpreter

On Wed, Jun 15, 2016 at 04:55:16PM +, Mathieu Desnoyers wrote: > Hi Josh, > > I notice that with gcc 6.1.1, kernel 4.6, with > CONFIG_STACK_VALIDATION=y, building lttng-modules master > at commit 6c09dd94 gives this warning: > > lttng-modules/lttng-filter-interpreter.o: warning: objtool: >

[PATCH 04/19] perf buildid: Rename and export build_id_cache__cachedir()

From: Masami Hiramatsu Rename and export build_id_cache__cachedir() for retrieving use of the path of cache directory for given build_id. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli Cc: Brendan Gregg

Re: stack validation warning on lttng-modules bytecode interpreter

On Wed, Jun 15, 2016 at 04:55:16PM +, Mathieu Desnoyers wrote: > Hi Josh, > > I notice that with gcc 6.1.1, kernel 4.6, with > CONFIG_STACK_VALIDATION=y, building lttng-modules master > at commit 6c09dd94 gives this warning: > > lttng-modules/lttng-filter-interpreter.o: warning: objtool: >

[PATCH 04/19] perf buildid: Rename and export build_id_cache__cachedir()

From: Masami Hiramatsu Rename and export build_id_cache__cachedir() for retrieving use of the path of cache directory for given build_id. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli Cc: Brendan Gregg Cc: Hemant Kumar Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 09/19] perf tools: Fix Data Object sort entry width index

From: Jiri Olsa Putting correct HISTC_MEM_DADDR_DSO index to Data Object sort entry. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 09/19] perf tools: Fix Data Object sort entry width index

From: Jiri Olsa Putting correct HISTC_MEM_DADDR_DSO index to Data Object sort entry. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1465928361-2442-3-git-send-email-jo...@kernel.org Signed-off-by: Arnaldo Carvalho de Melo ---

[PATCH 01/19] perf config: Handle NULL at perf_config_set__delete()

From: Taeung Song perf_config_set__delete() purge and free the config set that contains all config key-value pairs. But if the config set (i.e. 'set' variable at the function) is NULL, this is wrong so handle it. Signed-off-by: Taeung Song Cc:

[PATCH 12/19] perf stdio: Separate hierarchy headers output

From: Jiri Olsa Introducing hists__fprintf_hierarchy_headers function to separate hierarchy headers display code. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim

[PATCH 01/19] perf config: Handle NULL at perf_config_set__delete()

From: Taeung Song perf_config_set__delete() purge and free the config set that contains all config key-value pairs. But if the config set (i.e. 'set' variable at the function) is NULL, this is wrong so handle it. Signed-off-by: Taeung Song Cc: Alexander Shishkin Cc: Jiri Olsa Cc: Masami

[PATCH 12/19] perf stdio: Separate hierarchy headers output

From: Jiri Olsa Introducing hists__fprintf_hierarchy_headers function to separate hierarchy headers display code. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 15/19] perf stdio: Add use_callchain parameter to hists__fprintf

From: Jiri Olsa It will be convenient in following patches to display hists entries without callchains even if they are defined. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra

[PATCH 08/19] perf mem: Add --ldlat option

From: Jiri Olsa Adding --ldlat option to specify desired latency for loads event. Specify 50 as loads event latency: $ perf mem record -e ldlat-loads -v --ldlat 50 true calling: record -W -d -e cpu/mem-loads,ldlat=50/P true Signed-off-by: Jiri Olsa Cc:

[PATCH 06/19] perf probe: Uncomment and export synthesize_perf_probe_point()

From: Masami Hiramatsu Uncomment and export synthesize_perf_probe_point() which had once introduced but has been disabled for a long time. This renews the code and re-enable it. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli

[PATCH 07/19] perf unwind: Fix compile error for static cross build

From: He Kuang Build failure for static cross-compiling on aarch64, with libunwind-x86 provided: $ file ./libunwind_for_x86_on_aarch64/lib/libunwind-x86.so.8.0.1 libunwind-x86.so.8.0.1: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked,

[PATCH 06/19] perf probe: Uncomment and export synthesize_perf_probe_point()

From: Masami Hiramatsu Uncomment and export synthesize_perf_probe_point() which had once introduced but has been disabled for a long time. This renews the code and re-enable it. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli Cc: Brendan Gregg Cc: Hemant Kumar Cc: Namhyung

[PATCH 07/19] perf unwind: Fix compile error for static cross build

From: He Kuang Build failure for static cross-compiling on aarch64, with libunwind-x86 provided: $ file ./libunwind_for_x86_on_aarch64/lib/libunwind-x86.so.8.0.1 libunwind-x86.so.8.0.1: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, not stripped $

[PATCH 15/19] perf stdio: Add use_callchain parameter to hists__fprintf

From: Jiri Olsa It will be convenient in following patches to display hists entries without callchains even if they are defined. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1465928361-2442-9-git-send-email-jo...@kernel.org

[PATCH 08/19] perf mem: Add --ldlat option

From: Jiri Olsa Adding --ldlat option to specify desired latency for loads event. Specify 50 as loads event latency: $ perf mem record -e ldlat-loads -v --ldlat 50 true calling: record -W -d -e cpu/mem-loads,ldlat=50/P true Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc:

[PATCH 16/19] perf hists: Replace perf_evsel arg perf_hpp_fmt's header callback

From: Jiri Olsa Replacing perf_evsel arg perf_hpp_fmt's header callback with hists object. None of the actual callbacks actually use evsel object, also this will be helpful in future for non evsel related hist browsers. Signed-off-by: Jiri Olsa Cc: David

[PATCH 05/19] perf probe: Add perf_probe_event__copy()

From: Masami Hiramatsu Add perf_probe_event__copy() to copy perf_probe_event data structure and sub data structures under given source perf_probe_event. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli Cc:

[PATCH 03/19] perf probe: Fix to add NULL check for strndup

From: Masami Hiramatsu Fix to add a NULL check for strndup when parsing probe trace command. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli Cc: Brendan Gregg Cc: Hemant Kumar

[PATCH 02/19] perf tools: Fix rm_rf() to handle non-regular files correctly

From: Masami Hiramatsu Fix rm_rf() to handle non-regular files correctly. This fix includes two changes; - Fix to use lstat(3) instead of stat(3) since if the target file is a symbolic link, rm_rf() should unlink the symbolic link itself, not the file which pointed

[PATCH 03/19] perf probe: Fix to add NULL check for strndup

From: Masami Hiramatsu Fix to add a NULL check for strndup when parsing probe trace command. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli Cc: Brendan Gregg Cc: Hemant Kumar Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 02/19] perf tools: Fix rm_rf() to handle non-regular files correctly

From: Masami Hiramatsu Fix rm_rf() to handle non-regular files correctly. This fix includes two changes; - Fix to use lstat(3) instead of stat(3) since if the target file is a symbolic link, rm_rf() should unlink the symbolic link itself, not the file which pointed by the symlink. - Fix

[PATCH 16/19] perf hists: Replace perf_evsel arg perf_hpp_fmt's header callback

From: Jiri Olsa Replacing perf_evsel arg perf_hpp_fmt's header callback with hists object. None of the actual callbacks actually use evsel object, also this will be helpful in future for non evsel related hist browsers. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter

[PATCH 05/19] perf probe: Add perf_probe_event__copy()

From: Masami Hiramatsu Add perf_probe_event__copy() to copy perf_probe_event data structure and sub data structures under given source perf_probe_event. Signed-off-by: Masami Hiramatsu Cc: Ananth N Mavinakayanahalli Cc: Brendan Gregg Cc: Hemant Kumar Cc: Namhyung Kim Cc: Peter Zijlstra

[PATCH 10/19] perf tui: Separate hierarchy and standard headers output

From: Jiri Olsa It will be useful for future changes that enhance headers with multiple lines and span columns, which don't affect hierarchy headers. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern

Re: BLKZEROOUT not zeroing md dev on VMDK

It is possibly some race. We saw a WRITE SAME related issue in past for which Petr sent out a patch but looks like the patch didn't make it. :( https://groups.google.com/forum/#!topic/linux.kernel/1WGDSlyY0y0 Thanks! Arvind From: Sitsofe Wheeler

Re: BLKZEROOUT not zeroing md dev on VMDK

It is possibly some race. We saw a WRITE SAME related issue in past for which Petr sent out a patch but looks like the patch didn't make it. :( https://groups.google.com/forum/#!topic/linux.kernel/1WGDSlyY0y0 Thanks! Arvind From: Sitsofe Wheeler Sent:

[PATCH 10/19] perf tui: Separate hierarchy and standard headers output

From: Jiri Olsa It will be useful for future changes that enhance headers with multiple lines and span columns, which don't affect hierarchy headers. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 17/19] perf hists: Replace perf_evsel arg perf_hpp_fmt's width callback

From: Jiri Olsa Replacing perf_evsel arg perf_hpp_fmt's width callback with hists object. This will be helpful in future for non evsel related hist browsers. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim

[PATCH 17/19] perf hists: Replace perf_evsel arg perf_hpp_fmt's width callback

From: Jiri Olsa Replacing perf_evsel arg perf_hpp_fmt's width callback with hists object. This will be helpful in future for non evsel related hist browsers. Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 19/19] 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 Cc:

[PATCH 13/19] perf stdio: Separate standard headers output

From: Jiri Olsa Introducing hists__fprintf_standard_headers function to separate standard headers display code. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim

[GIT PULL 00/19] perf/core improvements and fixes

/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-20160615 for you to fetch changes up to 2fd457a34525ea3bc609e377b46af759af8a7934: perf probe: Add --cache option to cache the probe definitions (2016-06-15 14:34:42 -0300

[PATCH 19/19] 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 Cc: Ananth N Mavinakayanahalli Cc: Brendan Gregg Cc: Hemant Kumar Cc: Masami Hiramatsu

[PATCH 13/19] perf stdio: Separate standard headers output

From: Jiri Olsa Introducing hists__fprintf_standard_headers function to separate standard headers display code. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[GIT PULL 00/19] perf/core improvements and fixes

/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-20160615 for you to fetch changes up to 2fd457a34525ea3bc609e377b46af759af8a7934: perf probe: Add --cache option to cache the probe definitions (2016-06-15 14:34:42 -0300

[PATCH 14/19] perf stdio: Do not pass hists in hist_entry__fprintf

From: Jiri Olsa There's no need, we have the hists pointer in struct hist_entry. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra

[PATCH] of: fix memory leak related to safe_name()

From: Frank Rowand Fix a memory leak resulting from memory allocation in safe_name(). This patch fixes all call sites of safe_name(). Mathieu Malaterre reported the memory leak on boot: On my PowerMac device-tree would generate a duplicate name: [0.023043]

[PATCH 11/19] perf stdio: Separate headers output

From: Jiri Olsa Introducing hists__fprintf_headers function to separate the code that displays headers. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim

[PATCH 14/19] perf stdio: Do not pass hists in hist_entry__fprintf

From: Jiri Olsa There's no need, we have the hists pointer in struct hist_entry. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1465928361-2442-8-git-send-email-jo...@kernel.org Signed-off-by:

[PATCH] of: fix memory leak related to safe_name()

From: Frank Rowand Fix a memory leak resulting from memory allocation in safe_name(). This patch fixes all call sites of safe_name(). Mathieu Malaterre reported the memory leak on boot: On my PowerMac device-tree would generate a duplicate name: [0.023043] device-tree: Duplicate name in

[PATCH 11/19] perf stdio: Separate headers output

From: Jiri Olsa Introducing hists__fprintf_headers function to separate the code that displays headers. Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link:

[PATCH 18/19] perf probe: Introduce perf_cache interfaces

From: Masami Hiramatsu Introduce perf_cache object and interfaces to create, add entries, commit, and delete the object. perf_cache represents a file for the cached "perf probe" definitions on one binary file or vmlinux which has its own build id. The probe cache file is

[PATCH 18/19] perf probe: Introduce perf_cache interfaces

From: Masami Hiramatsu Introduce perf_cache object and interfaces to create, add entries, commit, and delete the object. perf_cache represents a file for the cached "perf probe" definitions on one binary file or vmlinux which has its own build id. The probe cache file is located under the

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 11:07 AM, Borislav Petkov wrote: > On Wed, Jun 15, 2016 at 10:55:34AM -0700, Andy Lutomirski wrote: >> Isn't it this one? > > Yes, it is. > >> I'm not. If %pF points at some silly helper, we still want the frames below >> it. > > Why silly helper? It

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 11:07 AM, Borislav Petkov wrote: > On Wed, Jun 15, 2016 at 10:55:34AM -0700, Andy Lutomirski wrote: >> Isn't it this one? > > Yes, it is. > >> I'm not. If %pF points at some silly helper, we still want the frames below >> it. > > Why silly helper? It points to the rIP

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 10:55:34AM -0700, Andy Lutomirski wrote: > Isn't it this one? Yes, it is. > I'm not. If %pF points at some silly helper, we still want the frames below > it. Why silly helper? It points to the rIP where the *MSR instruction is. Can't get more precise than that. And

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 10:55:34AM -0700, Andy Lutomirski wrote: > Isn't it this one? Yes, it is. > I'm not. If %pF points at some silly helper, we still want the frames below > it. Why silly helper? It points to the rIP where the *MSR instruction is. Can't get more precise than that. And

Re: [PATCH v3 2/4] Add the latent_entropy gcc plugin

On Tue, Jun 14, 2016 at 3:20 PM, Emese Revfy wrote: > This plugin mitigates the problem of the kernel having too little entropy > during > and after boot for generating crypto keys. > > It creates a local variable in every marked function. The value of this > variable is >

Re: [PATCH v3 2/4] Add the latent_entropy gcc plugin

On Tue, Jun 14, 2016 at 3:20 PM, Emese Revfy wrote: > This plugin mitigates the problem of the kernel having too little entropy > during > and after boot for generating crypto keys. > > It creates a local variable in every marked function. The value of this > variable is > modified by randomly

Re: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Mon, Jun 13, 2016 at 11:46:13AM +0300, Netanel Belgazal wrote: > This is a driver for the forthcoming ENA family of networking devices. > > Signed-off-by: Netanel Belgazal [...] > + > +struct ena_napi { > + struct napi_struct napi cacheline_aligned; > +

Re: [PATCH net-next] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Mon, Jun 13, 2016 at 11:46:13AM +0300, Netanel Belgazal wrote: > This is a driver for the forthcoming ENA family of networking devices. > > Signed-off-by: Netanel Belgazal [...] > + > +struct ena_napi { > + struct napi_struct napi cacheline_aligned; > + struct ena_ring *tx_ring;

Re: [Cocci] [PATCH v3 3/6] scripts: add glimpse.sh for indexing the kernel

On Wed, Jun 15, 2016 at 12:26:19PM +0200, SF Markus Elfring wrote: > > Glimpse is a tool you can use to index the kernel. > > The tool was recently open sourced under the ISC license > > and can be obtained at: > > Do you find any official announcement for this software evolution? I had reached

Re: [Cocci] [PATCH v3 3/6] scripts: add glimpse.sh for indexing the kernel

On Wed, Jun 15, 2016 at 12:26:19PM +0200, SF Markus Elfring wrote: > > Glimpse is a tool you can use to index the kernel. > > The tool was recently open sourced under the ISC license > > and can be obtained at: > > Do you find any official announcement for this software evolution? I had reached

Re: [PATCH resend] libata:fix kernel panic when hotplug

Hello, On Wed, Jun 15, 2016 at 05:15:32PM +0800, DingXiang wrote: > From: Miao Xie > > In normal condition,if we use sas protocol and hotplug a sata disk on a port, > the sas driver will send event "PORTE_BYTES_DMAED" and call function > "sas_porte_bytes_dmaed". > But if a

Re: [PATCH resend] libata:fix kernel panic when hotplug

Hello, On Wed, Jun 15, 2016 at 05:15:32PM +0800, DingXiang wrote: > From: Miao Xie > > In normal condition,if we use sas protocol and hotplug a sata disk on a port, > the sas driver will send event "PORTE_BYTES_DMAED" and call function > "sas_porte_bytes_dmaed". > But if a sata disk is run io

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 10:50 AM, Borislav Petkov wrote: > On Wed, Jun 15, 2016 at 10:23:39AM -0700, Andy Lutomirski wrote: >> Did the "Call Trace" not show up? > > It did, but it is bollocks too: > > [0.020003] [ cut here ] > [0.024009] WARNING:

Re: [x86] 5ac0c41bf3: WARNING: CPU: 0 PID: 0 at arch/x86/mm/extable.c:50 ex_handler_rdmsr_unsafe

On Wed, Jun 15, 2016 at 10:50 AM, Borislav Petkov wrote: > On Wed, Jun 15, 2016 at 10:23:39AM -0700, Andy Lutomirski wrote: >> Did the "Call Trace" not show up? > > It did, but it is bollocks too: > > [0.020003] [ cut here ] > [0.024009] WARNING: CPU: 0 PID: 0 at

Re: [RFC][PATCH 3/8] sched/deadline/rtmutex: Dont miss the dl_runtime/dl_period update

On Wed, Jun 15, 2016 at 12:30:07PM -0400, Steven Rostedt wrote: > > +++ b/kernel/locking/rtmutex.c > > @@ -488,7 +488,7 @@ static int rt_mutex_adjust_prio_chain(st > > * enabled we continue, but stop the requeueing in the chain > > * walk. > > */ > > - if (waiter->prio ==

Re: [RFC][PATCH 3/8] sched/deadline/rtmutex: Dont miss the dl_runtime/dl_period update

On Wed, Jun 15, 2016 at 12:30:07PM -0400, Steven Rostedt wrote: > > +++ b/kernel/locking/rtmutex.c > > @@ -488,7 +488,7 @@ static int rt_mutex_adjust_prio_chain(st > > * enabled we continue, but stop the requeueing in the chain > > * walk. > > */ > > - if (waiter->prio ==

Re: [PATCH 4/4] coccicheck: add indexing enhancement options

On Wed, Jun 15, 2016 at 05:44:01PM +0200, Julia Lawall wrote: > > > On Wed, 15 Jun 2016, Luis R. Rodriguez wrote: > > OK thanks. I remove --very-quiet now if --profile is used within SPFLAGS, > > I'll extend > > this to also avoid --very-quiet if --show-trying is used. SPFLAGS is where > > you

Re: [PATCH 4/4] coccicheck: add indexing enhancement options

On Wed, Jun 15, 2016 at 05:44:01PM +0200, Julia Lawall wrote: > > > On Wed, 15 Jun 2016, Luis R. Rodriguez wrote: > > OK thanks. I remove --very-quiet now if --profile is used within SPFLAGS, > > I'll extend > > this to also avoid --very-quiet if --show-trying is used. SPFLAGS is where > > you

<    4   5   6   7   8   9   10   11   12   13   >