Re: [PATCH] ARM: dts: db600c: add support to pcie refclk

On Tue 20 Mar 17:28 HKT 2018, Srinivas Kandagatla wrote: > From: Srinivas Kandagatla > > This patch adds support to external pcie refclk. > > Signed-off-by: Srinivas Kandagatla > --- > arch/arm/boot/dts/qcom-apq8064-db600c.dts |

Re: [PATCH] ARM: dts: db600c: add support to pcie refclk

On Tue 20 Mar 17:28 HKT 2018, Srinivas Kandagatla wrote: > From: Srinivas Kandagatla > > This patch adds support to external pcie refclk. > > Signed-off-by: Srinivas Kandagatla > --- > arch/arm/boot/dts/qcom-apq8064-db600c.dts | 27 +++ > 1 file changed, 27

Re: [PATCH v1 1/2] phy: Add QMP phy based UFS phy support for sdm845

Hi Can, On 3/21/2018 8:12 AM, c...@codeaurora.org wrote: > On 2018-03-20 19:30, Can Guo wrote: >> Add UFS PHY support to make SDM845 UFS work with common PHY framework. >> >> Signed-off-by: Can Guo >> --- >>  drivers/phy/qualcomm/phy-qcom-qmp.c | 120 >>

Re: [PATCH v1 1/2] phy: Add QMP phy based UFS phy support for sdm845

Hi Can, On 3/21/2018 8:12 AM, c...@codeaurora.org wrote: > On 2018-03-20 19:30, Can Guo wrote: >> Add UFS PHY support to make SDM845 UFS work with common PHY framework. >> >> Signed-off-by: Can Guo >> --- >>  drivers/phy/qualcomm/phy-qcom-qmp.c | 120 >> +++- >>  

linux-next: manual merge of the selinux tree with the security tree

Hi Paul, Today's linux-next merge of the selinux tree got a conflict in: security/selinux/hooks.c between commit: 6b4f3d01052a ("usb, signal, security: only pass the cred, not the secid, to kill_pid_info_as_cred and security_task_kill") from the security tree and commit: 6b6bc6205d98

linux-next: manual merge of the selinux tree with the security tree

Hi Paul, Today's linux-next merge of the selinux tree got a conflict in: security/selinux/hooks.c between commit: 6b4f3d01052a ("usb, signal, security: only pass the cred, not the secid, to kill_pid_info_as_cred and security_task_kill") from the security tree and commit: 6b6bc6205d98

RE: [PATCH v5 2/7] vfio/type1: Check reserve region conflict and update iova list

> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Wednesday, March 21, 2018 6:38 AM > > On Mon, 19 Mar 2018 07:51:58 + > "Tian, Kevin" wrote: > > > > From: Shameer Kolothum > > > Sent: Friday, March 16, 2018 12:35 AM > > > > > > This retrieves the

RE: [PATCH v5 2/7] vfio/type1: Check reserve region conflict and update iova list

> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Wednesday, March 21, 2018 6:38 AM > > On Mon, 19 Mar 2018 07:51:58 + > "Tian, Kevin" wrote: > > > > From: Shameer Kolothum > > > Sent: Friday, March 16, 2018 12:35 AM > > > > > > This retrieves the reserved regions

RE: [PATCH v5 0/7] vfio/type1: Add support for valid iova list management

> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Wednesday, March 21, 2018 6:55 AM > > On Mon, 19 Mar 2018 08:28:32 + > "Tian, Kevin" wrote: > > > > From: Shameer Kolothum > > > Sent: Friday, March 16, 2018 12:35 AM > > > > > > This series introduces

RE: [PATCH v5 0/7] vfio/type1: Add support for valid iova list management

> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Wednesday, March 21, 2018 6:55 AM > > On Mon, 19 Mar 2018 08:28:32 + > "Tian, Kevin" wrote: > > > > From: Shameer Kolothum > > > Sent: Friday, March 16, 2018 12:35 AM > > > > > > This series introduces an iova list

[PATCH V2 2/4] clk: add new APIs to operate on all available clocks

This patch introduces of_clk_bulk_get_all and clk_bulk_x_all APIs to users who just want to handle all available clocks from device tree without need to know the detailed clock information likes clock numbers and names. This is useful in writing some generic drivers to handle clock part. Cc:

[PATCH V2 3/4] clk: add managed version of clk_bulk_get_all

This patch introduces the managed version of clk_bulk_get_all. Cc: Michael Turquette Cc: Stephen Boyd Signed-off-by: Dong Aisheng --- v1->v2: * new patch --- drivers/clk/clk-devres.c | 24

[PATCH V2 2/4] clk: add new APIs to operate on all available clocks

This patch introduces of_clk_bulk_get_all and clk_bulk_x_all APIs to users who just want to handle all available clocks from device tree without need to know the detailed clock information likes clock numbers and names. This is useful in writing some generic drivers to handle clock part. Cc:

[PATCH V2 3/4] clk: add managed version of clk_bulk_get_all

This patch introduces the managed version of clk_bulk_get_all. Cc: Michael Turquette Cc: Stephen Boyd Signed-off-by: Dong Aisheng --- v1->v2: * new patch --- drivers/clk/clk-devres.c | 24 include/linux/clk.h | 23 +++ 2 files changed, 47

[PATCH V2 4/4] video: simplefb: switch to use clk_bulk API to simplify clock operations

Switching to use clk_bulk API to simplify clock operations. Cc: Hans de Goede Cc: Bartlomiej Zolnierkiewicz Cc: linux-fb...@vger.kernel.org Cc: Masahiro Yamada Cc: Stephen Boyd Signed-off-by:

[PATCH V2 4/4] video: simplefb: switch to use clk_bulk API to simplify clock operations

Switching to use clk_bulk API to simplify clock operations. Cc: Hans de Goede Cc: Bartlomiej Zolnierkiewicz Cc: linux-fb...@vger.kernel.org Cc: Masahiro Yamada Cc: Stephen Boyd Signed-off-by: Dong Aisheng --- v1->v2: * switch to clk_bulk_get_all from of_clk_bulk_get_all ---

[PATCH V2 1/4] clk: bulk: add of_clk_bulk_get()

'clock-names' property is optional in DT, so of_clk_bulk_get() is introduced here to handle this for DT users without 'clock-names' specified. Later clk_bulk_get_all() will be implemented on top of it and this API will be kept private until someone proves they need it because they don't have a

[PATCH V2 0/4] clk: new APIs to handle all available clocks

This patch series is a continue of discussion from here, https://patchwork.kernel.org/patch/9986293/ that some users may want to handle all available clocks from device tree without need to know the detailed clock information likes clock numbers and names. This is useful in writing some generic

[PATCH V2 1/4] clk: bulk: add of_clk_bulk_get()

'clock-names' property is optional in DT, so of_clk_bulk_get() is introduced here to handle this for DT users without 'clock-names' specified. Later clk_bulk_get_all() will be implemented on top of it and this API will be kept private until someone proves they need it because they don't have a

[PATCH V2 0/4] clk: new APIs to handle all available clocks

This patch series is a continue of discussion from here, https://patchwork.kernel.org/patch/9986293/ that some users may want to handle all available clocks from device tree without need to know the detailed clock information likes clock numbers and names. This is useful in writing some generic

Re: [PATCH v4 23/24] fpga: dfl: afu: add user afu sub feature support

On Tue, Mar 20, 2018 at 01:17:14PM -0500, Alan Tull wrote: > On Tue, Mar 20, 2018 at 2:10 AM, Wu Hao wrote: > > On Mon, Mar 19, 2018 at 03:10:28PM -0500, Alan Tull wrote: > >> On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote: > >> > >> Hi Hao, > >> > >> > From:

Re: [PATCH v4 23/24] fpga: dfl: afu: add user afu sub feature support

On Tue, Mar 20, 2018 at 01:17:14PM -0500, Alan Tull wrote: > On Tue, Mar 20, 2018 at 2:10 AM, Wu Hao wrote: > > On Mon, Mar 19, 2018 at 03:10:28PM -0500, Alan Tull wrote: > >> On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote: > >> > >> Hi Hao, > >> > >> > From: Xiao Guangrong > >> > > >> > User

Re: [PATCH -next] phy: phy-mtk-tphy: fix missing clk_disable_unprepare() on error in mtk_phy_init()

On Tue, 2018-03-20 at 13:19 +, Wei Yongjun wrote: > Fix the missing clk_disable_unprepare() before return > from mtk_phy_init() in the error handling case. > > Signed-off-by: Wei Yongjun > --- > drivers/phy/mediatek/phy-mtk-tphy.c | 11 +-- > 1 file changed,

Re: [PATCH -next] phy: phy-mtk-tphy: fix missing clk_disable_unprepare() on error in mtk_phy_init()

On Tue, 2018-03-20 at 13:19 +, Wei Yongjun wrote: > Fix the missing clk_disable_unprepare() before return > from mtk_phy_init() in the error handling case. > > Signed-off-by: Wei Yongjun > --- > drivers/phy/mediatek/phy-mtk-tphy.c | 11 +-- > 1 file changed, 9 insertions(+), 2

[PATCH v3] MIPS: ralink: fix booting on mt7621

Since commit 3af5a67c86a3 ("MIPS: Fix early CM probing") the MT7621 has not been able to boot. This patched caused mips_cm_probe() to be called before mt7621.c::proc_soc_init(). prom_soc_init() has a comment explaining that mips_cm_probe() "wipes out the bootloader config" and means that

[PATCH v3] MIPS: ralink: fix booting on mt7621

Since commit 3af5a67c86a3 ("MIPS: Fix early CM probing") the MT7621 has not been able to boot. This patched caused mips_cm_probe() to be called before mt7621.c::proc_soc_init(). prom_soc_init() has a comment explaining that mips_cm_probe() "wipes out the bootloader config" and means that

Re: [PATCH v2] MIPS: ralink: fix booting on mt7621

On Tue, Mar 20 2018, Matt Redfearn wrote: > Hi Neil, > > > On 20/03/18 08:22, NeilBrown wrote: >> >> Further testing showed that the original version of this >> patch wasn't 100% reliable. Very occasionally the read >> of SYSC_REG_CHIP_NAME0 returns garbage. Repeating the >> read seems to be

Re: [PATCH v2] MIPS: ralink: fix booting on mt7621

On Tue, Mar 20 2018, Matt Redfearn wrote: > Hi Neil, > > > On 20/03/18 08:22, NeilBrown wrote: >> >> Further testing showed that the original version of this >> patch wasn't 100% reliable. Very occasionally the read >> of SYSC_REG_CHIP_NAME0 returns garbage. Repeating the >> read seems to be

Re: [PATCH v4 16/24] fpga: dfl: add fpga manager platform driver for FME

On Tue, Mar 20, 2018 at 03:32:34PM -0500, Alan Tull wrote: > On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote: > > Hi Hao, > > Elsewhere we discussed moving #defines used only in this driver either > to this .c file or to a similarly named .h file. A couple minor > things below.

Re: [PATCH v4 16/24] fpga: dfl: add fpga manager platform driver for FME

On Tue, Mar 20, 2018 at 03:32:34PM -0500, Alan Tull wrote: > On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote: > > Hi Hao, > > Elsewhere we discussed moving #defines used only in this driver either > to this .c file or to a similarly named .h file. A couple minor > things below. Hi Alan, Yes, I

[PATCH v1] ARM: dts: imx6qdl-sabreauto: add ecspi dts for sabreauto board

DIN pin of SPI-NOR muxed with I2C3_SDA which connected to one gpio expand chip, thus have to disable all those module which compacted by those gpios if enable SPI-NOR support on Sabreauto board. Signed-off-by: Robin Gong --- arch/arm/boot/dts/Makefile | 2

[PATCH v1] ARM: dts: imx6qdl-sabreauto: add ecspi dts for sabreauto board

DIN pin of SPI-NOR muxed with I2C3_SDA which connected to one gpio expand chip, thus have to disable all those module which compacted by those gpios if enable SPI-NOR support on Sabreauto board. Signed-off-by: Robin Gong --- arch/arm/boot/dts/Makefile | 2 ++

Re: [PATCH v2 00/11] RISC-V: Resolve the issue of loadable module on 64-bit

2018-03-21 1:11 GMT+08:00 Palmer Dabbelt : > On Thu, 15 Mar 2018 01:50:40 PDT (-0700), z...@andestech.com wrote: >> >> These patches resolve the some issues of loadable module. >> - symbol out of ranges >> - unknown relocation types >> >> The reference of external variable

Re: [PATCH v2 00/11] RISC-V: Resolve the issue of loadable module on 64-bit

2018-03-21 1:11 GMT+08:00 Palmer Dabbelt : > On Thu, 15 Mar 2018 01:50:40 PDT (-0700), z...@andestech.com wrote: >> >> These patches resolve the some issues of loadable module. >> - symbol out of ranges >> - unknown relocation types >> >> The reference of external variable and function symbols

[PATCH v2] clk: sunxi-ng: add missing hdmi-slow clock for H6 CCU

The Allwinner H6 CCU has a "HDMI Slow Clock", which is currently missing in the ccu-sun50i-h6 driver. Add this missing clock to the driver. Fixes: 542353ea ("clk: sunxi-ng: add support for the Allwinner H6 CCU") Signed-off-by: Icenowy Zheng --- Changes in v2: - Rearrange clock

[PATCH v2] clk: sunxi-ng: add missing hdmi-slow clock for H6 CCU

The Allwinner H6 CCU has a "HDMI Slow Clock", which is currently missing in the ccu-sun50i-h6 driver. Add this missing clock to the driver. Fixes: 542353ea ("clk: sunxi-ng: add support for the Allwinner H6 CCU") Signed-off-by: Icenowy Zheng --- Changes in v2: - Rearrange clock slice numbers.

Re: linux-next: build failure after merge of the sound-asoc tree

On Wed, Mar 21, 2018 at 01:30:40PM +1100, Stephen Rothwell wrote: > Caused by commit > 363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller > instance") > I have used the sound-asoc tree from next-20180320 for today. Dropped. signature.asc Description: PGP signature

Re: linux-next: build failure after merge of the sound-asoc tree

On Wed, Mar 21, 2018 at 01:30:40PM +1100, Stephen Rothwell wrote: > Caused by commit > 363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller > instance") > I have used the sound-asoc tree from next-20180320 for today. Dropped. signature.asc Description: PGP signature

Re: [PATCH 2/2] x86/unwind: Make CONFIG_UNWINDER_ORC=y the default in kconfig for 64-bit

On Mon, Mar 19, 2018 at 04:22:55PM -0700, Matthias Kaehlcke wrote: > arch/x86/mm/pti.o: warning: objtool: pti_init() falls through to next > function pti_user_pagetable_walk_pmd() > s/debugfs/file.o: warning: objtool: full_proxy_llseek() falls through to next > function full_proxy_read() >

Re: [PATCH 2/2] x86/unwind: Make CONFIG_UNWINDER_ORC=y the default in kconfig for 64-bit

On Mon, Mar 19, 2018 at 04:22:55PM -0700, Matthias Kaehlcke wrote: > arch/x86/mm/pti.o: warning: objtool: pti_init() falls through to next > function pti_user_pagetable_walk_pmd() > s/debugfs/file.o: warning: objtool: full_proxy_llseek() falls through to next > function full_proxy_read() >

Re: [PATCH v1 1/2] phy: Add QMP phy based UFS phy support for sdm845

On 2018-03-20 19:30, Can Guo wrote: Add UFS PHY support to make SDM845 UFS work with common PHY framework. Signed-off-by: Can Guo --- drivers/phy/qualcomm/phy-qcom-qmp.c | 120 +++- drivers/phy/qualcomm/phy-qcom-qmp.h | 8 +++ 2 files

Re: [PATCH 2/2] dt-bindings: regulator: add QCOM RPMh regulator bindings

On Fri, Mar 16, 2018 at 06:09:11PM -0700, David Collins wrote: > Introduce bindings for RPMh regulator devices found on some > Qualcomm Technlogies, Inc. SoCs. These devices allow a given Please use subject lines matching the style for the subsystem. This makes it easier for people to identify

Re: [PATCH v1 1/2] phy: Add QMP phy based UFS phy support for sdm845

On 2018-03-20 19:30, Can Guo wrote: Add UFS PHY support to make SDM845 UFS work with common PHY framework. Signed-off-by: Can Guo --- drivers/phy/qualcomm/phy-qcom-qmp.c | 120 +++- drivers/phy/qualcomm/phy-qcom-qmp.h | 8 +++ 2 files changed, 126

Re: [PATCH 2/2] dt-bindings: regulator: add QCOM RPMh regulator bindings

On Fri, Mar 16, 2018 at 06:09:11PM -0700, David Collins wrote: > Introduce bindings for RPMh regulator devices found on some > Qualcomm Technlogies, Inc. SoCs. These devices allow a given Please use subject lines matching the style for the subsystem. This makes it easier for people to identify

Re: [PATCH v1 0/2] Support for Qualcomm UFS QMP PHY on SDM845

On 2018-03-20 19:30, Can Guo wrote: This patch series adds support for UFS QMP PHY on SDM845 and updates the compitable string for it. Can Guo (2): phy: Add QMP phy based UFS phy support for sdm845 dt-bindings: phy-qcom-qmp: Update UFS phy compitable string for sdm845

Re: [PATCH v1 0/2] Support for Qualcomm UFS QMP PHY on SDM845

On 2018-03-20 19:30, Can Guo wrote: This patch series adds support for UFS QMP PHY on SDM845 and updates the compitable string for it. Can Guo (2): phy: Add QMP phy based UFS phy support for sdm845 dt-bindings: phy-qcom-qmp: Update UFS phy compitable string for sdm845

Re: [PATCH v1 2/2] dt-bindings: phy-qcom-qmp: Update UFS phy binding for sdm845

On 2018-03-20 19:30, Can Guo wrote: Update the compatible string for UFS QMP PHY on SDM845. Signed-off-by: Can Guo --- Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

Re: [PATCH v1 2/2] dt-bindings: phy-qcom-qmp: Update UFS phy binding for sdm845

On 2018-03-20 19:30, Can Guo wrote: Update the compatible string for UFS QMP PHY on SDM845. Signed-off-by: Can Guo --- Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0

On 03/15/2018 12:47 PM, John Garry wrote: > On 15/03/2018 15:53, William Cohen wrote: >> On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: >>> On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > Hi Will Cohen,

Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0

On 03/15/2018 12:47 PM, John Garry wrote: > On 15/03/2018 15:53, William Cohen wrote: >> On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: >>> On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > Hi Will Cohen, > > On Wed,

[PATCH v1] ARM: dts: imx6qdl-sabreauto: add ecspi dts for sabreauto board

DIN pin of SPI-NOR muxed with I2C3_SDA which connected to one gpio expand chip, thus have to disable all those module which compacted by those gpios if enable SPI-NOR support on Sabreauto board. Signed-off-by: Robin Gong --- arch/arm/boot/dts/Makefile | 2

[PATCH v1] ARM: dts: imx6qdl-sabreauto: add ecspi dts for sabreauto board

DIN pin of SPI-NOR muxed with I2C3_SDA which connected to one gpio expand chip, thus have to disable all those module which compacted by those gpios if enable SPI-NOR support on Sabreauto board. Signed-off-by: Robin Gong --- arch/arm/boot/dts/Makefile | 2 ++

[for-next][PATCH 08/46] tracing: Give event triggers access to ring_buffer_event

From: Tom Zanussi The ring_buffer event can provide a timestamp that may be useful to various triggers - pass it into the handlers for that purpose. Link: http://lkml.kernel.org/r/6de592683b59fa70ffa5d43d0109896623fc1367.1516069914.git.tom.zanu...@linux.intel.com

[for-next][PATCH 08/46] tracing: Give event triggers access to ring_buffer_event

From: Tom Zanussi The ring_buffer event can provide a timestamp that may be useful to various triggers - pass it into the handlers for that purpose. Link: http://lkml.kernel.org/r/6de592683b59fa70ffa5d43d0109896623fc1367.1516069914.git.tom.zanu...@linux.intel.com Signed-off-by: Tom Zanussi

[for-next][PATCH 07/46] tracing: Add timestamp_mode trace file

From: Tom Zanussi Add a new option flag indicating whether or not the ring buffer is in 'absolute timestamp' mode. Currently this is only set/unset by hist triggers that make use of a common_timestamp. As such, there's no reason to make this writeable for users -

[for-next][PATCH 07/46] tracing: Add timestamp_mode trace file

From: Tom Zanussi Add a new option flag indicating whether or not the ring buffer is in 'absolute timestamp' mode. Currently this is only set/unset by hist triggers that make use of a common_timestamp. As such, there's no reason to make this writeable for users - its purpose is only to allow

linux-next: build failure after merge of the sound-asoc tree

se I2S_SP_INSTANCE: ^~~ I2S_BT_INSTANCE Caused by commit 363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller instance") I have used the sound-asoc tree from next-20180320 for today. -- Cheers, Stephen Rothwell pgpHM3jB3z8xI.pgp Description: OpenPGP digital signature

linux-next: build failure after merge of the sound-asoc tree

se I2S_SP_INSTANCE: ^~~ I2S_BT_INSTANCE Caused by commit 363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller instance") I have used the sound-asoc tree from next-20180320 for today. -- Cheers, Stephen Rothwell pgpHM3jB3z8xI.pgp Description: OpenPGP digital signature

[for-next][PATCH 04/46] tracing: Remove code which merges duplicates

From: Vedang Patel We now have the logic to detect and remove duplicates in the tracing_map hash table. The code which merges duplicates in the histogram is redundant now. So, modify this code just to detect duplicates. The duplication detection code is still kept to

[for-next][PATCH 05/46] ring-buffer: Add interface for setting absolute time stamps

From: Tom Zanussi Define a new function, tracing_set_time_stamp_abs(), which can be used to enable or disable the use of absolute timestamps rather than time deltas for a trace array. Only the interface is added here; a subsequent patch will add the underlying

[for-next][PATCH 05/46] ring-buffer: Add interface for setting absolute time stamps

From: Tom Zanussi Define a new function, tracing_set_time_stamp_abs(), which can be used to enable or disable the use of absolute timestamps rather than time deltas for a trace array. Only the interface is added here; a subsequent patch will add the underlying implementation. Link:

[for-next][PATCH 04/46] tracing: Remove code which merges duplicates

From: Vedang Patel We now have the logic to detect and remove duplicates in the tracing_map hash table. The code which merges duplicates in the histogram is redundant now. So, modify this code just to detect duplicates. The duplication detection code is still kept to ensure that any rare race

[for-next][PATCH 03/46] tracing: Add support to detect and avoid duplicates

From: Vedang Patel A duplicate in the tracing_map hash table is when 2 different entries have the same key and, as a result, the key_hash. This is possible due to a race condition in the algorithm. This race condition is inherent to the algorithm and not a bug. This was

[for-next][PATCH 03/46] tracing: Add support to detect and avoid duplicates

From: Vedang Patel A duplicate in the tracing_map hash table is when 2 different entries have the same key and, as a result, the key_hash. This is possible due to a race condition in the algorithm. This race condition is inherent to the algorithm and not a bug. This was fine because, until now,

[for-next][PATCH 02/46] tracing: Add Documentation for log2 modifier

From: Tom Zanussi Add a line for the log2 modifier, to keep it aligned with tracing/README. Link: http://lkml.kernel.org/r/a419028bccab155749a4b8702d5b97af75f1578f.1516069914.git.tom.zanu...@linux.intel.com Signed-off-by: Tom Zanussi

[for-next][PATCH 02/46] tracing: Add Documentation for log2 modifier

From: Tom Zanussi Add a line for the log2 modifier, to keep it aligned with tracing/README. Link: http://lkml.kernel.org/r/a419028bccab155749a4b8702d5b97af75f1578f.1516069914.git.tom.zanu...@linux.intel.com Signed-off-by: Tom Zanussi Signed-off-by: Steven Rostedt (VMware) ---

[for-next][PATCH 06/46] ring-buffer: Redefine the unimplemented RINGBUF_TYPE_TIME_STAMP

From: Tom Zanussi RINGBUF_TYPE_TIME_STAMP is defined but not used, and from what I can gather was reserved for something like an absolute timestamp feature for the ring buffer, if not a complete replacement of the current time_delta scheme. This code redefines

[for-next][PATCH 06/46] ring-buffer: Redefine the unimplemented RINGBUF_TYPE_TIME_STAMP

From: Tom Zanussi RINGBUF_TYPE_TIME_STAMP is defined but not used, and from what I can gather was reserved for something like an absolute timestamp feature for the ring buffer, if not a complete replacement of the current time_delta scheme. This code redefines RINGBUF_TYPE_TIME_STAMP to

[for-next][PATCH 09/46] tracing: Add ring buffer event param to hist field functions

From: Tom Zanussi Some events such as timestamps require access to a ring_buffer_event struct; add a param so that hist field functions can access that. Link:

[for-next][PATCH 09/46] tracing: Add ring buffer event param to hist field functions

From: Tom Zanussi Some events such as timestamps require access to a ring_buffer_event struct; add a param so that hist field functions can access that. Link: http://lkml.kernel.org/r/2ff4af18e72b6002eb86b26b2a7f39cef7d1dfe4.1516069914.git.tom.zanu...@linux.intel.com Signed-off-by: Tom

[for-next][PATCH 10/46] tracing: Break out hist trigger assignment parsing

From: Tom Zanussi This will make it easier to add variables, and makes the parsing code cleaner regardless. Link: http://lkml.kernel.org/r/e574b3291bbe15e35a4dfc87e5395aa715701c98.1516069914.git.tom.zanu...@linux.intel.com Signed-off-by: Tom Zanussi

[for-next][PATCH 10/46] tracing: Break out hist trigger assignment parsing

From: Tom Zanussi This will make it easier to add variables, and makes the parsing code cleaner regardless. Link: http://lkml.kernel.org/r/e574b3291bbe15e35a4dfc87e5395aa715701c98.1516069914.git.tom.zanu...@linux.intel.com Signed-off-by: Tom Zanussi Signed-off-by: Rajvi Jingar

[for-next][PATCH 12/46] tracing: Add per-element variable support to tracing_map

From: Tom Zanussi In order to allow information to be passed between trace events, add support for per-element variables to tracing_map. This provides a means for histograms to associate a value or values with an entry when it's saved or updated, and retrieved by a

[for-next][PATCH 12/46] tracing: Add per-element variable support to tracing_map

From: Tom Zanussi In order to allow information to be passed between trace events, add support for per-element variables to tracing_map. This provides a means for histograms to associate a value or values with an entry when it's saved or updated, and retrieved by a subsequent event occurrences.

[for-next][PATCH 11/46] tracing: Add hist trigger timestamp support

From: Tom Zanussi Add support for a timestamp event field. This is actually a 'pseudo-' event field in that it behaves like it's part of the event record, but is really part of the corresponding ring buffer event. To make use of the timestamp field, users can

[for-next][PATCH 11/46] tracing: Add hist trigger timestamp support

From: Tom Zanussi Add support for a timestamp event field. This is actually a 'pseudo-' event field in that it behaves like it's part of the event record, but is really part of the corresponding ring buffer event. To make use of the timestamp field, users can specify "common_timestamp" as a

[for-next][PATCH 25/46] tracing: Add support for field variables

From: Tom Zanussi Users should be able to directly specify event fields in hist trigger 'actions' rather than being forced to explicitly create a variable for that purpose. Add support allowing fields to be used directly in actions, which essentially does just that

[for-next][PATCH 25/46] tracing: Add support for field variables

From: Tom Zanussi Users should be able to directly specify event fields in hist trigger 'actions' rather than being forced to explicitly create a variable for that purpose. Add support allowing fields to be used directly in actions, which essentially does just that - creates 'invisible'

[for-next][PATCH 24/46] tracing: Add support for synthetic events

From: Tom Zanussi Synthetic events are user-defined events generated from hist trigger variables saved from one or more other events. To define a synthetic event, the user writes a simple specification consisting of the name of the new event along with one or more

[for-next][PATCH 27/46] tracing: Add onmax hist trigger action support

From: Tom Zanussi Add an 'onmax(var).save(field,...)' hist trigger action which is invoked whenever an event exceeds the current maximum. The end result is that the trace event fields or variables specified as the onmax.save() params will be saved if 'var' exceeds

[for-next][PATCH 27/46] tracing: Add onmax hist trigger action support

From: Tom Zanussi Add an 'onmax(var).save(field,...)' hist trigger action which is invoked whenever an event exceeds the current maximum. The end result is that the trace event fields or variables specified as the onmax.save() params will be saved if 'var' exceeds the current maximum for that

[for-next][PATCH 24/46] tracing: Add support for synthetic events

From: Tom Zanussi Synthetic events are user-defined events generated from hist trigger variables saved from one or more other events. To define a synthetic event, the user writes a simple specification consisting of the name of the new event along with one or more variables and their type(s),

[for-next][PATCH 20/46] tracing: Pass tracing_map_elt to hist_field accessor functions

From: Tom Zanussi Some accessor functions, such as for variable references, require access to a corrsponding tracing_map_elt. Add a tracing_map_elt param to the function signature and update the accessor functions accordingly. Link:

[for-next][PATCH 20/46] tracing: Pass tracing_map_elt to hist_field accessor functions

From: Tom Zanussi Some accessor functions, such as for variable references, require access to a corrsponding tracing_map_elt. Add a tracing_map_elt param to the function signature and update the accessor functions accordingly. Link:

[for-next][PATCH 19/46] tracing: Generalize per-element hist trigger data

From: Tom Zanussi Up until now, hist triggers only needed per-element support for saving 'comm' data, which was saved directly as a private data pointer. In anticipation of the need to save other data besides 'comm', add a new hist_elt_data struct for the purpose,

[for-next][PATCH 19/46] tracing: Generalize per-element hist trigger data

From: Tom Zanussi Up until now, hist triggers only needed per-element support for saving 'comm' data, which was saved directly as a private data pointer. In anticipation of the need to save other data besides 'comm', add a new hist_elt_data struct for the purpose, and switch the current

[for-next][PATCH 16/46] tracing: Account for variables in named trigger compatibility

From: Tom Zanussi Named triggers must also have the same set of variables in order to be considered compatible - update the trigger match test to account for that. The reason for this requirement is that named triggers with variables are meant to allow one or more

[for-next][PATCH 23/46] tracing: Add hist trigger action hook

From: Tom Zanussi Add a hook for executing extra actions whenever a histogram entry is added or updated. The default 'action' when a hist entry is added to a histogram is to update the set of values associated with it. Some applications may want to perform

[for-next][PATCH 16/46] tracing: Account for variables in named trigger compatibility

From: Tom Zanussi Named triggers must also have the same set of variables in order to be considered compatible - update the trigger match test to account for that. The reason for this requirement is that named triggers with variables are meant to allow one or more events to set the same

[for-next][PATCH 23/46] tracing: Add hist trigger action hook

From: Tom Zanussi Add a hook for executing extra actions whenever a histogram entry is added or updated. The default 'action' when a hist entry is added to a histogram is to update the set of values associated with it. Some applications may want to perform additional actions at that point,

[for-next][PATCH 17/46] tracing: Move get_hist_field_flags()

From: Tom Zanussi Move get_hist_field_flags() to make it more easily accessible for new code (and keep the move separate from new functionality). Link: http://lkml.kernel.org/r/32470f0a7047ec7a6e84ba5ec89d6142cc6ede7d.1516069914.git.tom.zanu...@linux.intel.com

[for-next][PATCH 17/46] tracing: Move get_hist_field_flags()

From: Tom Zanussi Move get_hist_field_flags() to make it more easily accessible for new code (and keep the move separate from new functionality). Link: http://lkml.kernel.org/r/32470f0a7047ec7a6e84ba5ec89d6142cc6ede7d.1516069914.git.tom.zanu...@linux.intel.com Signed-off-by: Tom Zanussi

[for-next][PATCH 18/46] tracing: Add simple expression support to hist triggers

From: Tom Zanussi Add support for simple addition, subtraction, and unary expressions (-(expr) and expr, where expr = b-a, a+b, a+b+c) to hist triggers, in order to support a minimal set of useful inter-event calculations. These operations are needed for calculating

[for-next][PATCH 18/46] tracing: Add simple expression support to hist triggers

From: Tom Zanussi Add support for simple addition, subtraction, and unary expressions (-(expr) and expr, where expr = b-a, a+b, a+b+c) to hist triggers, in order to support a minimal set of useful inter-event calculations. These operations are needed for calculating latencies between events

[for-next][PATCH 21/46] tracing: Add hist_field type field

From: Tom Zanussi Future support for synthetic events requires hist_field 'type' information, so add a field for that. Also, make other hist_field attribute usage consistent (size, is_signed, etc). Link:

[for-next][PATCH 22/46] tracing: Add variable reference handling to hist triggers

From: Tom Zanussi Add the necessary infrastructure to allow the variables defined on one event to be referenced in another. This allows variables set by a previous event to be referenced and used in expressions combining the variable values saved by that previous

[for-next][PATCH 31/46] tracing: Add last error error facility for hist triggers

From: Tom Zanussi With the addition of variables and actions, it's become necessary to provide more detailed error information to users about syntax errors. Add a 'last error' facility accessible via the erroring event's 'hist' file. Reading the hist file after an

[for-next][PATCH 21/46] tracing: Add hist_field type field

From: Tom Zanussi Future support for synthetic events requires hist_field 'type' information, so add a field for that. Also, make other hist_field attribute usage consistent (size, is_signed, etc). Link:

[for-next][PATCH 22/46] tracing: Add variable reference handling to hist triggers

From: Tom Zanussi Add the necessary infrastructure to allow the variables defined on one event to be referenced in another. This allows variables set by a previous event to be referenced and used in expressions combining the variable values saved by that previous event and the event fields of

[for-next][PATCH 31/46] tracing: Add last error error facility for hist triggers

From: Tom Zanussi With the addition of variables and actions, it's become necessary to provide more detailed error information to users about syntax errors. Add a 'last error' facility accessible via the erroring event's 'hist' file. Reading the hist file after an error will display more

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