[RFC PATCH 4/4] perf-probe: Support probing on offline cross-arch binary

Support probing on offline cross-architecture binary by adding getting the target machine arch from ELF and choose correct register string for the machine. Here is an example: - $ mkdir tracing $ sudo perf probe --outdir=./tracing --vmlinux=./vmlinux-arm \ do_sys_open '$vars'

Re: [PATCH v2 4/4] gpu: drm: exynos_hdmi: Use consolidated function on binding PHY DT property

On 08/24/2016 04:25 AM, Milo Kim wrote: > Handle legacy and raw 'phy' parsing in single function. > And it also removes goto condition. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: David Airlie > Cc: Inki Dae

[RFC PATCH 4/4] perf-probe: Support probing on offline cross-arch binary

Support probing on offline cross-architecture binary by adding getting the target machine arch from ELF and choose correct register string for the machine. Here is an example: - $ mkdir tracing $ sudo perf probe --outdir=./tracing --vmlinux=./vmlinux-arm \ do_sys_open '$vars'

Re: [PATCH v2 4/4] gpu: drm: exynos_hdmi: Use consolidated function on binding PHY DT property

On 08/24/2016 04:25 AM, Milo Kim wrote: > Handle legacy and raw 'phy' parsing in single function. > And it also removes goto condition. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: David Airlie > Cc: Inki Dae > Cc: Joonyoung Shim > Cc: Seung-Woo Kim > Cc: Kyungmin Park > Cc: Rob

[RFC PATCH 2/4] perf-probe: Add offline output directory option

Add offline output direcrtory option. This allows user to store probe event definition in offline output directory. Signed-off-by: Masami Hiramatsu --- tools/perf/builtin-probe.c|2 ++ tools/perf/util/probe-event.h |1 + tools/perf/util/probe-file.c | 19

[RFC PATCH 3/4] perf-probe: Ignore vmlinux buildid if offline kernel is given

Ignore the buildid of running kernel when both --outdir and --vmlinux is given and --outdir is not tracing_path, because that kernel should be off-line. Signed-off-by: Masami Hiramatsu --- tools/perf/builtin-probe.c |6 ++ tools/perf/util/symbol-elf.c |2 +- 2

[RFC PATCH 2/4] perf-probe: Add offline output directory option

Add offline output direcrtory option. This allows user to store probe event definition in offline output directory. Signed-off-by: Masami Hiramatsu --- tools/perf/builtin-probe.c|2 ++ tools/perf/util/probe-event.h |1 + tools/perf/util/probe-file.c | 19 --- 3

[RFC PATCH 3/4] perf-probe: Ignore vmlinux buildid if offline kernel is given

Ignore the buildid of running kernel when both --outdir and --vmlinux is given and --outdir is not tracing_path, because that kernel should be off-line. Signed-off-by: Masami Hiramatsu --- tools/perf/builtin-probe.c |6 ++ tools/perf/util/symbol-elf.c |2 +- 2 files changed, 7

[RFC PATCH 1/4] perf-probe: Remove unused tracing_dir variable

Remove unused tracing_dir variable from open_probe_events(). Signed-off-by: Masami Hiramatsu --- tools/perf/util/probe-file.c |5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/tools/perf/util/probe-file.c b/tools/perf/util/probe-file.c index

[RFC PATCH 1/4] perf-probe: Remove unused tracing_dir variable

Remove unused tracing_dir variable from open_probe_events(). Signed-off-by: Masami Hiramatsu --- tools/perf/util/probe-file.c |5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/tools/perf/util/probe-file.c b/tools/perf/util/probe-file.c index 697ef66..6f931e4 100644 ---

[RFC PATCH 0/4] perf probe: Introduce remote cross-arch probes

Hi, Here is an RFC series for remote cross-arch probe support on perf-probe. I've made a perf-probe for remote arch (currently arm on x86-64) for helping debugging and performance analysis. Currently perf-probe doesn't supoort cross/remote target. This means we have to cross-build the

[RFC PATCH 0/4] perf probe: Introduce remote cross-arch probes

Hi, Here is an RFC series for remote cross-arch probe support on perf-probe. I've made a perf-probe for remote arch (currently arm on x86-64) for helping debugging and performance analysis. Currently perf-probe doesn't supoort cross/remote target. This means we have to cross-build the

Re: [PATCH v6 2/4] Add support for SCT Write Same

Never mind. I was a bit lightheaded. Anyway I don't think you should use ata_scsi_rbuf. It is a buffer created and used for ata_scsi_simulate, which interacts with the SCSI layer but not the ATA device (v.s. ata_scsi_translate). You should probably create buffer inside ata_format_dsm_trim_descr()

Re: [PATCH v6 2/4] Add support for SCT Write Same

Never mind. I was a bit lightheaded. Anyway I don't think you should use ata_scsi_rbuf. It is a buffer created and used for ata_scsi_simulate, which interacts with the SCSI layer but not the ATA device (v.s. ata_scsi_translate). You should probably create buffer inside ata_format_dsm_trim_descr()

Re: [PATCH v2 3/4] gpu: drm: exynos_hdmi: Use consolidated function on binding DDC DT property

On 08/24/2016 04:25 AM, Milo Kim wrote: > Handle legacy and raw 'ddc' parsing in single function. > And it also removes goto condition. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: David Airlie > Cc: Inki Dae

Re: [PATCH v2 3/4] gpu: drm: exynos_hdmi: Use consolidated function on binding DDC DT property

On 08/24/2016 04:25 AM, Milo Kim wrote: > Handle legacy and raw 'ddc' parsing in single function. > And it also removes goto condition. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: David Airlie > Cc: Inki Dae > Cc: Joonyoung Shim > Cc: Seung-Woo Kim > Cc: Kyungmin Park > Cc: Rob

Re: [PATCH v2 2/2] HWRNG: thunderx: Add Cavium HWRNG driver for ThunderX SoC.

Hello > +/* Read data from the RNG unit */ > +static int cavium_rng_read(struct hwrng *rng, void *dat, size_t max, bool > wait) > +{ > + struct cavium_rng *p = container_of(rng, struct cavium_rng, ops); > + unsigned int size = max; > + > + while (size >= 8) { > + *((u64

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, Aug 23, 2016 at 8:58 PM, Dan Williams wrote: > On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams > wrote: >> On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu wrote: On Tue, Aug 23, 2016 at 4:47 PM, Kani,

Re: [PATCH v2 2/2] HWRNG: thunderx: Add Cavium HWRNG driver for ThunderX SoC.

Hello > +/* Read data from the RNG unit */ > +static int cavium_rng_read(struct hwrng *rng, void *dat, size_t max, bool > wait) > +{ > + struct cavium_rng *p = container_of(rng, struct cavium_rng, ops); > + unsigned int size = max; > + > + while (size >= 8) { > + *((u64

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, Aug 23, 2016 at 8:58 PM, Dan Williams wrote: > On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams > wrote: >> On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu wrote: On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu wrote: > On Tue, 2016-08-23 at 15:32 -0700, Dan Williams

Re: [PATCH v6 1/4] libata: Safely overwrite attached page in WRITE SAME xlat

On 24 August 2016 at 11:33, Martin K. Petersen wrote: >> "Tom" == Tom Yan writes: > > Tom> Nope, SCSI Write Same commands does not have payload (or in SCSI > Tom> terms, parameter list / data-out buffer). > > WRITE SAME has a a payload of 1

Re: [PATCH v6 1/4] libata: Safely overwrite attached page in WRITE SAME xlat

On 24 August 2016 at 11:33, Martin K. Petersen wrote: >> "Tom" == Tom Yan writes: > > Tom> Nope, SCSI Write Same commands does not have payload (or in SCSI > Tom> terms, parameter list / data-out buffer). > > WRITE SAME has a a payload of 1 logical block (unless NDOB is set but we > have had

Re: [PATCH] drm/gma500: remove unnecessary config_enabled() guard

On Wed, Aug 24, 2016 at 01:42:54AM +0900, Masahiro Yamada wrote: > Commit d112a8163f83 ("gma500/cdv: Add eDP support") replaced the > code inside this if-conditional with gma_backlight_set(), which > becomes a nop stub if CONFIG_BACKLIGHT_CLASS_DEVICE is disabled. > So, there is no need to guard

Re: [PATCH] drm/gma500: remove unnecessary config_enabled() guard

On Wed, Aug 24, 2016 at 01:42:54AM +0900, Masahiro Yamada wrote: > Commit d112a8163f83 ("gma500/cdv: Add eDP support") replaced the > code inside this if-conditional with gma_backlight_set(), which > becomes a nop stub if CONFIG_BACKLIGHT_CLASS_DEVICE is disabled. > So, there is no need to guard

Re: [PATCH v2 2/4] ARM: dts: exynos: Use 'hpd-gpios' instead of 'hpd-gpio'

On 08/24/2016 04:25 AM, Milo Kim wrote: > This patch enables getting a HPD GPIO descriptor quickly. > The exynos-hdmi driver uses "hpd" for HDMI hot plug detection. > > static int hdmi_resources_init(struct hdmi_context *hdata) > { > ... > hdata->hpd_gpio =

Re: [PATCH v2 2/4] ARM: dts: exynos: Use 'hpd-gpios' instead of 'hpd-gpio'

On 08/24/2016 04:25 AM, Milo Kim wrote: > This patch enables getting a HPD GPIO descriptor quickly. > The exynos-hdmi driver uses "hpd" for HDMI hot plug detection. > > static int hdmi_resources_init(struct hdmi_context *hdata) > { > ... > hdata->hpd_gpio =

Re: [PATCH v2 1/4] ARM: dts: exynos: Enable HDMI for Arndale Octa board

Hi Milo, On 08/24/2016 04:25 AM, Milo Kim wrote: > * Support HDMI display data channel > I2C #2 is assigned for the HDMI DDC. It enables the EDID access. > > * GPIO for HDMI hot plug detect > GPX3_7 is used. The HPD awareness is done when the GPIO is active high and > single ended. > > *

Re: [PATCH v2 1/4] ARM: dts: exynos: Enable HDMI for Arndale Octa board

Hi Milo, On 08/24/2016 04:25 AM, Milo Kim wrote: > * Support HDMI display data channel > I2C #2 is assigned for the HDMI DDC. It enables the EDID access. > > * GPIO for HDMI hot plug detect > GPX3_7 is used. The HPD awareness is done when the GPIO is active high and > single ended. > > *

Re: [PATCH v2 2/4] On Discard either do Reset WP or Write Same

On Mon, Aug 22, 2016 at 8:25 PM, Damien Le Moal wrote: > > Shaun, > > On 8/23/16 09:22, Shaun Tancheff wrote: >> On Mon, Aug 22, 2016 at 6:57 PM, Damien Le Moal >> wrote: >> Also you may note that in my patch to get Host Aware working >> with the

Re: [PATCH v2 2/4] On Discard either do Reset WP or Write Same

On Mon, Aug 22, 2016 at 8:25 PM, Damien Le Moal wrote: > > Shaun, > > On 8/23/16 09:22, Shaun Tancheff wrote: >> On Mon, Aug 22, 2016 at 6:57 PM, Damien Le Moal >> wrote: >> Also you may note that in my patch to get Host Aware working >> with the zone cache I do not include the runt zone in

Re: [PATCH v3] PM / sleep: enable suspend-to-idle even without registered suspend_ops

On 19 August 2016 at 08:41, Sudeep Holla wrote: > Suspend-to-idle (aka the "freeze" sleep state) is a system sleep state > in which all of the processors enter deepest possible idle state and > wait for interrupts right after suspending all the devices. > > There is no hard

Re: [PATCH v3] PM / sleep: enable suspend-to-idle even without registered suspend_ops

On 19 August 2016 at 08:41, Sudeep Holla wrote: > Suspend-to-idle (aka the "freeze" sleep state) is a system sleep state > in which all of the processors enter deepest possible idle state and > wait for interrupts right after suspending all the devices. > > There is no hard requirement for a

[v14 PATCH 4/5] Documentation: bindings: add dt documentation for cdn DP controller

This patch adds a binding that describes the cdn DP controller for rk3399. Signed-off-by: Chris Zhong Acked-by: Rob Herring Reviewed-by: Guenter Roeck --- Changes in v14: None Changes in v13: - add dptx and apb reset Changes in v12:

[v14 PATCH 1/5] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY

This patch adds a binding that describes the Rockchip USB Type-C PHY for rk3399 Signed-off-by: Chris Zhong Reviewed-by: Tomasz Figa Reviewed-by: Kever Yang Reviewed-by: Guenter Roeck Acked-by: Rob Herring

[v14 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and HBR2 data rates. This driver create 2 PHY devices separately for USB3 and DisplyPort, and

[v14 PATCH 4/5] Documentation: bindings: add dt documentation for cdn DP controller

This patch adds a binding that describes the cdn DP controller for rk3399. Signed-off-by: Chris Zhong Acked-by: Rob Herring Reviewed-by: Guenter Roeck --- Changes in v14: None Changes in v13: - add dptx and apb reset Changes in v12: None Changes in v11: - refer dp phy Changes in v10: - add

[v14 PATCH 1/5] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY

This patch adds a binding that describes the Rockchip USB Type-C PHY for rk3399 Signed-off-by: Chris Zhong Reviewed-by: Tomasz Figa Reviewed-by: Kever Yang Reviewed-by: Guenter Roeck Acked-by: Rob Herring --- Changes in v14: None Changes in v13: None Changes in v12: None Changes in v11: -

[v14 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and HBR2 data rates. This driver create 2 PHY devices separately for USB3 and DisplyPort, and

[v14 PATCH 3/5] arm64: dts: rockchip: add Type-C phy for RK3399

There are 2 Type-C phy on RK3399, they are almost same, except the address of register. They support USB3.0 Type-C and DisplayPort1.3 Alt Mode on USB Type-C. Register a phy, supply it to USB3 controller and DP controller. Signed-off-by: Chris Zhong Reviewed-by: Guenter Roeck

[v14 PATCH 0/5] Rockchip Type-C and DisplayPort driver

Hi all This series patch is for rockchip Type-C phy and DisplayPort controller driver. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and

[v14 PATCH 5/5] drm/rockchip: cdn-dp: add cdn DP support for rk3399

Add support for cdn DP controller which is embedded in the rk3399 SoCs. The DP is compliant with DisplayPort Specification, Version 1.3, This IP is compatible with the rockchip type-c PHY IP. There is a uCPU in DP controller, it need a firmware to work, please put the firmware file to

[v14 PATCH 3/5] arm64: dts: rockchip: add Type-C phy for RK3399

There are 2 Type-C phy on RK3399, they are almost same, except the address of register. They support USB3.0 Type-C and DisplayPort1.3 Alt Mode on USB Type-C. Register a phy, supply it to USB3 controller and DP controller. Signed-off-by: Chris Zhong Reviewed-by: Guenter Roeck --- Changes in

[v14 PATCH 0/5] Rockchip Type-C and DisplayPort driver

Hi all This series patch is for rockchip Type-C phy and DisplayPort controller driver. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and

[v14 PATCH 5/5] drm/rockchip: cdn-dp: add cdn DP support for rk3399

Add support for cdn DP controller which is embedded in the rk3399 SoCs. The DP is compliant with DisplayPort Specification, Version 1.3, This IP is compatible with the rockchip type-c PHY IP. There is a uCPU in DP controller, it need a firmware to work, please put the firmware file to

Re: [PATCH 2/8] staging/lustre/mdc: fix panic at mdc_free_open()

Actually, please do not apply this one, there was a testing error that made me not noticing there's a bug in this one that insta-crashes everything on access. I tested the rest nd the rest are good without this one too. Sorry about this. On Aug 23, 2016, at 5:11 PM, Oleg Drokin wrote: > From:

Re: [PATCH 2/8] staging/lustre/mdc: fix panic at mdc_free_open()

Actually, please do not apply this one, there was a testing error that made me not noticing there's a bug in this one that insta-crashes everything on access. I tested the rest nd the rest are good without this one too. Sorry about this. On Aug 23, 2016, at 5:11 PM, Oleg Drokin wrote: > From:

Re: [PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus

On 08/22/16 at 09:14am, "Zhou, Wenjian/周文剑" wrote: > On 08/19/2016 11:57 PM, Jonathan Corbet wrote: > >On Fri, 19 Aug 2016 08:33:21 +0800 > >"Zhou, Wenjian/周文剑" wrote: > > > >>I was also confused by maxcpus and nr_cpus before writing this patch. > >>I think it is a

Re: [PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus

On 08/22/16 at 09:14am, "Zhou, Wenjian/周文剑" wrote: > On 08/19/2016 11:57 PM, Jonathan Corbet wrote: > >On Fri, 19 Aug 2016 08:33:21 +0800 > >"Zhou, Wenjian/周文剑" wrote: > > > >>I was also confused by maxcpus and nr_cpus before writing this patch. > >>I think it is a good choice to describe it in

[PATCH v2] serial: vt8500_serial: Fix a parameter of find_first_zero_bit.

The 2nd parameter of 'find_first_zero_bit' is the number of bits to search. In this case, we are passing 'sizeof(vt8500_ports_in_use)'. 'vt8500_ports_in_use' is an 'unsigned long'. So the sizeof is likely to return 4 on a 32 bits kernel. A few lines below, we check if it is below

[PATCH v2] serial: vt8500_serial: Fix a parameter of find_first_zero_bit.

The 2nd parameter of 'find_first_zero_bit' is the number of bits to search. In this case, we are passing 'sizeof(vt8500_ports_in_use)'. 'vt8500_ports_in_use' is an 'unsigned long'. So the sizeof is likely to return 4 on a 32 bits kernel. A few lines below, we check if it is below

Re: [v13.1 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Hi Chanwoo On 08/23/2016 01:44 PM, Chanwoo Choi wrote: Hi Chris, The name of 'SuperSpeed' property is changed from EXTCON_PROP_USB_SUPERSPEED to EXTCON_PROP_USB_SS. The name change was discussed on mail thread[1]. Oh, since I was using the old name in my local kernel, I will change it in

Re: [v13.1 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Hi Chanwoo On 08/23/2016 01:44 PM, Chanwoo Choi wrote: Hi Chris, The name of 'SuperSpeed' property is changed from EXTCON_PROP_USB_SUPERSPEED to EXTCON_PROP_USB_SS. The name change was discussed on mail thread[1]. Oh, since I was using the old name in my local kernel, I will change it in

Re: [PATCH v2 1/2] cpufreq / sched: Pass flags to cpufreq_update_util()

On Mon, Aug 22, 2016 at 07:30:36PM +0200, Rafael J. Wysocki wrote: > On Saturday, August 20, 2016 05:40:49 PM Krzysztof Kozlowski wrote: > > On Sat, Aug 20, 2016 at 03:08:01AM +0200, Rafael J. Wysocki wrote: > > > On Friday, August 19, 2016 03:26:21 PM Krzysztof Kozlowski wrote: > > > > On Fri,

Re: [PATCH v2 1/2] cpufreq / sched: Pass flags to cpufreq_update_util()

On Mon, Aug 22, 2016 at 07:30:36PM +0200, Rafael J. Wysocki wrote: > On Saturday, August 20, 2016 05:40:49 PM Krzysztof Kozlowski wrote: > > On Sat, Aug 20, 2016 at 03:08:01AM +0200, Rafael J. Wysocki wrote: > > > On Friday, August 19, 2016 03:26:21 PM Krzysztof Kozlowski wrote: > > > > On Fri,

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, Aug 23, 2016 at 9:28 PM, Kani, Toshimitsu wrote: >> On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams >> wrote: >> > On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu >> wrote: >> >>> On Tue, Aug 23, 2016 at 4:47 PM, Kani,

Re: [Patch v8] driver/clk/clk-si5338: Add common clock framework driver for si5338

On 08/24, kbuild test robot wrote: > > 2827if (drv_type < 0) > 2828return drv_type; > 2829 > 2830drv_vdd = get_drv_vdd(drvdata, i); > 2831if (drv_vdd < 0) > 2832return drv_vdd; >

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, Aug 23, 2016 at 9:28 PM, Kani, Toshimitsu wrote: >> On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams >> wrote: >> > On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu >> wrote: >> >>> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu >> >> >>> wrote: > : >> >> >> >> crash> p {struct

Re: [Patch v8] driver/clk/clk-si5338: Add common clock framework driver for si5338

On 08/24, kbuild test robot wrote: > > 2827if (drv_type < 0) > 2828return drv_type; > 2829 > 2830drv_vdd = get_drv_vdd(drvdata, i); > 2831if (drv_vdd < 0) > 2832return drv_vdd; >

Re: [PATCH 1/2] clk: samsung: exynos5260: Move struct samsung_cmu_info to init section

On 08/23, Sylwester Nawrocki wrote: > On 08/23/2016 04:35 AM, Chanwoo Choi wrote: > I checked stripped object files and it seems with the patch there > is some saving of the kernel image size. Exactly 784 bytes, which > makes zImage smaller by 480 bytes. > > The patch increases .init.rodata

Re: [PATCH 1/2] clk: samsung: exynos5260: Move struct samsung_cmu_info to init section

On 08/23, Sylwester Nawrocki wrote: > On 08/23/2016 04:35 AM, Chanwoo Choi wrote: > I checked stripped object files and it seems with the patch there > is some saving of the kernel image size. Exactly 784 bytes, which > makes zImage smaller by 480 bytes. > > The patch increases .init.rodata

linux-next: Tree for Aug 24

Hi all, Changes since 20160823: The drm-intel tree lost its build failure but gained conflicts against the drm-intel-fixes tree. The kbuild tree still had its build warnings for PowerPC, for which I reverted a commit. The sound-asoc tree lost its build failure. Non-merge commits (relative

linux-next: Tree for Aug 24

Hi all, Changes since 20160823: The drm-intel tree lost its build failure but gained conflicts against the drm-intel-fixes tree. The kbuild tree still had its build warnings for PowerPC, for which I reverted a commit. The sound-asoc tree lost its build failure. Non-merge commits (relative

RE: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

> On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams > wrote: > > On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu > wrote: > >>> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu > > >>> wrote: : > >> > >> crash> p {struct

RE: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

> On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams > wrote: > > On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu > wrote: > >>> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu > > >>> wrote: : > >> > >> crash> p {struct vmem_altmap} 0x88046d045410 > >> $6 = { > >> base_pfn = 0x48, >

linux-next: taking a break

Hi all, I will not be producing a linux-next release this Friday or next week. So the next release after tomorrow will be next-20160905. -- Cheers, Stephen Rothwell

linux-next: taking a break

Hi all, I will not be producing a linux-next release this Friday or next week. So the next release after tomorrow will be next-20160905. -- Cheers, Stephen Rothwell

Re: [RFC PATCH-tip v4 10/10] locking/rwsem: Add a boot parameter to reader spinning threshold

On Thu, 18 Aug 2016, Waiman Long wrote: The default reader spining threshold is current set to 4096. However, the right reader spinning threshold may vary from one system to another and among the different architectures. This patch adds a new kernel boot parameter to modify the threshold value.

Re: [RFC PATCH-tip v4 10/10] locking/rwsem: Add a boot parameter to reader spinning threshold

On Thu, 18 Aug 2016, Waiman Long wrote: The default reader spining threshold is current set to 4096. However, the right reader spinning threshold may vary from one system to another and among the different architectures. This patch adds a new kernel boot parameter to modify the threshold value.

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams wrote: > On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu wrote: >>> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu >>> wrote: >>> > On Tue, 2016-08-23 at 15:32 -0700, Dan

Re: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

On Tue, Aug 23, 2016 at 7:53 PM, Dan Williams wrote: > On Tue, Aug 23, 2016 at 6:29 PM, Kani, Toshimitsu wrote: >>> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu >>> wrote: >>> > On Tue, 2016-08-23 at 15:32 -0700, Dan Williams wrote: >>> >> On Tue, Aug 23, 2016 at 11:43 AM, Toshi Kani >>>

Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent

Thanks! I'll get back to you with something better. On 23 August 2016 at 23:55, Vince Weaver wrote: > On Tue, 23 Aug 2016, Alexander Shishkin wrote: > >> Vince Weaver writes: >> >> > On Tue, 23 Aug 2016, Alexander Shishkin wrote: >> > >> >> Recently Vince has

Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent

Thanks! I'll get back to you with something better. On 23 August 2016 at 23:55, Vince Weaver wrote: > On Tue, 23 Aug 2016, Alexander Shishkin wrote: > >> Vince Weaver writes: >> >> > On Tue, 23 Aug 2016, Alexander Shishkin wrote: >> > >> >> Recently Vince has reported warnings and panics coming

Re: [PATCH 2/2] mm/usercopy: enable usercopy size checking for modern versions of gcc

On Tue, Aug 23, 2016 at 3:28 PM, Josh Poimboeuf wrote: > This is a revert of: > > 2fb0815c9ee6 ("gcc4: disable __compiletime_object_size for GCC 4.6+") > > The goal of that commit was to silence the "provably correct" gcc > warnings. But it went too far: it also disabled

Re: [PATCH 2/2] mm/usercopy: enable usercopy size checking for modern versions of gcc

On Tue, Aug 23, 2016 at 3:28 PM, Josh Poimboeuf wrote: > This is a revert of: > > 2fb0815c9ee6 ("gcc4: disable __compiletime_object_size for GCC 4.6+") > > The goal of that commit was to silence the "provably correct" gcc > warnings. But it went too far: it also disabled the runtime warnings.

[PATCH v13 1/4] dt-bindings: soc: Add documentation for the MediaTek GCE unit

This adds documentation for the MediaTek Global Command Engine (GCE) unit found in MT8173 SoCs. Signed-off-by: HS Liao Acked-by: Rob Herring --- .../devicetree/bindings/soc/mediatek/gce.txt | 44 ++ 1 file changed, 44

[PATCH v13 1/4] dt-bindings: soc: Add documentation for the MediaTek GCE unit

This adds documentation for the MediaTek Global Command Engine (GCE) unit found in MT8173 SoCs. Signed-off-by: HS Liao Acked-by: Rob Herring --- .../devicetree/bindings/soc/mediatek/gce.txt | 44 ++ 1 file changed, 44 insertions(+) create mode 100644

linux-next: build warning after merge of the thermal tree

Hi Zhang, After merging the thermal tree, today's linux-next build (powerpc allyesconfig) produced this warning: warning: (HISI_THERMAL) selects STUB_CLK_HI6220 which has unmet direct dependencies (COMMON_CLK && COMMON_CLK_HI6220 && MAILBOX) Introduced by commit 5f63581ce68e ("thermal:

linux-next: build warning after merge of the thermal tree

Hi Zhang, After merging the thermal tree, today's linux-next build (powerpc allyesconfig) produced this warning: warning: (HISI_THERMAL) selects STUB_CLK_HI6220 which has unmet direct dependencies (COMMON_CLK && COMMON_CLK_HI6220 && MAILBOX) Introduced by commit 5f63581ce68e ("thermal:

[PATCH v13 2/4] CMDQ: Mediatek CMDQ driver

This patch is first version of Mediatek Command Queue(CMDQ) driver. The CMDQ is used to help write registers with critical time limitation, such as updating display configuration during the vblank. It controls Global Command Engine (GCE) hardware to achieve this requirement. Currently, CMDQ only

[PATCH v13 2/4] CMDQ: Mediatek CMDQ driver

This patch is first version of Mediatek Command Queue(CMDQ) driver. The CMDQ is used to help write registers with critical time limitation, such as updating display configuration during the vblank. It controls Global Command Engine (GCE) hardware to achieve this requirement. Currently, CMDQ only

Re: [PATCH] infiniband/mlx5: Remove superfluous include of io-mapping.h

- Original Message - > From: "Chris Wilson" > To: linux-r...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org, "Chris Wilson" , > "Eli Cohen" , "Jack > Morgenstein" , "Or Gerlitz" >

Re: [PATCH v6 1/4] libata: Safely overwrite attached page in WRITE SAME xlat

> "Tom" == Tom Yan writes: Tom> Nope, SCSI Write Same commands does not have payload (or in SCSI Tom> terms, parameter list / data-out buffer). WRITE SAME has a a payload of 1 logical block (unless NDOB is set but we have had no good reason to support that yet). UNMAP

Re: [PATCH] infiniband/mlx5: Remove superfluous include of io-mapping.h

- Original Message - > From: "Chris Wilson" > To: linux-r...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org, "Chris Wilson" , > "Eli Cohen" , "Jack > Morgenstein" , "Or Gerlitz" > , "Matan Barak" , > "Leon Romanovsky" , "Doug Ledford" > , "Sean Hefty" , > "Hal Rosenstock" >

Re: [PATCH v6 1/4] libata: Safely overwrite attached page in WRITE SAME xlat

> "Tom" == Tom Yan writes: Tom> Nope, SCSI Write Same commands does not have payload (or in SCSI Tom> terms, parameter list / data-out buffer). WRITE SAME has a a payload of 1 logical block (unless NDOB is set but we have had no good reason to support that yet). UNMAP has a payload that

[PATCH v13 4/4] CMDQ: save more energy in idle

Use clk_disable_unprepare instead of clk_disable to save more energy when CMDQ is idle. Signed-off-by: HS Liao --- drivers/soc/mediatek/mtk-cmdq.c | 54 +++-- 1 file changed, 46 insertions(+), 8 deletions(-) diff --git

[PATCH v13 4/4] CMDQ: save more energy in idle

Use clk_disable_unprepare instead of clk_disable to save more energy when CMDQ is idle. Signed-off-by: HS Liao --- drivers/soc/mediatek/mtk-cmdq.c | 54 +++-- 1 file changed, 46 insertions(+), 8 deletions(-) diff --git a/drivers/soc/mediatek/mtk-cmdq.c

[PATCH v13 3/4] arm64: dts: mt8173: Add GCE node

This patch adds the device node of the GCE hardware for CMDQ module. Signed-off-by: HS Liao --- arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi

[PATCH v13 3/4] arm64: dts: mt8173: Add GCE node

This patch adds the device node of the GCE hardware for CMDQ module. Signed-off-by: HS Liao --- arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi index

[PATCH v13 0/4] Mediatek MT8173 CMDQ support

Hi, This is Mediatek MT8173 Command Queue(CMDQ) driver. The CMDQ is used to help write registers with critical time limitation, such as updating display configuration during the vblank. It controls Global Command Engine (GCE) hardware to achieve this requirement. These patches have a build

[PATCH v13 0/4] Mediatek MT8173 CMDQ support

Hi, This is Mediatek MT8173 Command Queue(CMDQ) driver. The CMDQ is used to help write registers with critical time limitation, such as updating display configuration during the vblank. It controls Global Command Engine (GCE) hardware to achieve this requirement. These patches have a build

Re: [lkp] [x86/irq] 82ba4faca1: [No primary change] [unixbench]

On 08/24/2016 11:04 AM, kernel test robot wrote: > > FYI, we noticed interrupts.CAL:Function_call_interrupts +771.1% improvement > due to commit: This is expected. CAL:Function_call_interrupts now contains TLB shootdowns while it doesn't previously. Thanks, Aaron > > commit

Re: [lkp] [x86/irq] 82ba4faca1: [No primary change] [unixbench]

On 08/24/2016 11:04 AM, kernel test robot wrote: > > FYI, we noticed interrupts.CAL:Function_call_interrupts +771.1% improvement > due to commit: This is expected. CAL:Function_call_interrupts now contains TLB shootdowns while it doesn't previously. Thanks, Aaron > > commit

Re: [PATCH v1 00/10] Optimize sched avgs computation and implement flat util hierarchy

Hi Vincent, On Tue, Aug 23, 2016 at 03:28:19PM +0200, Vincent Guittot wrote: > I still wonder if using a flat util hierarchy is the right solution to > solve this problem with utilization and task group. I have noticed > exact same issues with load that generates weird task placement > decision

Re: [PATCH v1 00/10] Optimize sched avgs computation and implement flat util hierarchy

Hi Vincent, On Tue, Aug 23, 2016 at 03:28:19PM +0200, Vincent Guittot wrote: > I still wonder if using a flat util hierarchy is the right solution to > solve this problem with utilization and task group. I have noticed > exact same issues with load that generates weird task placement > decision

RE: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu > wrote: > > On Tue, 2016-08-23 at 15:32 -0700, Dan Williams wrote: > >> On Tue, Aug 23, 2016 at 11:43 AM, Toshi Kani > >> wrote: > > : > >> I'm not sure about this fix. The point of honoring > >>

RE: [PATCH] memremap: Fix NULL pointer BUG in get_zone_device_page()

> On Tue, Aug 23, 2016 at 4:47 PM, Kani, Toshimitsu > wrote: > > On Tue, 2016-08-23 at 15:32 -0700, Dan Williams wrote: > >> On Tue, Aug 23, 2016 at 11:43 AM, Toshi Kani > >> wrote: > > : > >> I'm not sure about this fix. The point of honoring > >> vmem_altmap_offset() is because a portion of

[RFC][PATCH v2] timekeeping: Cap array access in timekeeping_debug to protect against invalid sleep times

It was reported that hibernation could fail on the 2nd attempt, where the system hangs at hibernate() -> syscore_resume() -> i8237A_resume() -> claim_dma_lock(), because the lock has already been taken. However there is actually no other process would like to grab this lock on that problematic

Re: [PATCH v1 00/10] Optimize sched avgs computation and implement flat util hierarchy

On Tue, Aug 23, 2016 at 04:13:41PM +0200, Peter Zijlstra wrote: > On Tue, Aug 23, 2016 at 03:28:19PM +0200, Vincent Guittot wrote: > > I still wonder if using a flat util hierarchy is the right solution to > > solve this problem with utilization and task group. I have noticed > > exact same issues

[RFC][PATCH v2] timekeeping: Cap array access in timekeeping_debug to protect against invalid sleep times

It was reported that hibernation could fail on the 2nd attempt, where the system hangs at hibernate() -> syscore_resume() -> i8237A_resume() -> claim_dma_lock(), because the lock has already been taken. However there is actually no other process would like to grab this lock on that problematic

Re: [PATCH v1 00/10] Optimize sched avgs computation and implement flat util hierarchy

On Tue, Aug 23, 2016 at 04:13:41PM +0200, Peter Zijlstra wrote: > On Tue, Aug 23, 2016 at 03:28:19PM +0200, Vincent Guittot wrote: > > I still wonder if using a flat util hierarchy is the right solution to > > solve this problem with utilization and task group. I have noticed > > exact same issues

  1   2   3   4   5   6   7   8   9   10   >