[RFC PATCH 2/4] cpufreq: schedutil: support scheduler cpufreq callbacks on remote CPUs

In preparation for the scheduler cpufreq callback happening on remote CPUs, add support for this in schedutil. Schedutil requires the callback occur on the CPU being updated in order to support fast frequency switches. Signed-off-by: Steve Muckle ---

[RFC PATCH 1/4] cpufreq: governor: support scheduler cpufreq callbacks on remote CPUs

In preparation for the scheduler cpufreq callback happening on remote CPUs, add support for this in the dbs governors. The dbs governors make assumptions about the callback occurring on the CPU being updated. Signed-off-by: Steve Muckle --- drivers/cpufreq/cpufreq_governor.c

[RFC PATCH 2/4] cpufreq: schedutil: support scheduler cpufreq callbacks on remote CPUs

In preparation for the scheduler cpufreq callback happening on remote CPUs, add support for this in schedutil. Schedutil requires the callback occur on the CPU being updated in order to support fast frequency switches. Signed-off-by: Steve Muckle --- kernel/sched/cpufreq_schedutil.c | 90

[RFC PATCH 1/4] cpufreq: governor: support scheduler cpufreq callbacks on remote CPUs

In preparation for the scheduler cpufreq callback happening on remote CPUs, add support for this in the dbs governors. The dbs governors make assumptions about the callback occurring on the CPU being updated. Signed-off-by: Steve Muckle --- drivers/cpufreq/cpufreq_governor.c | 21

[RFC PATCH 3/4] intel_pstate: support scheduler cpufreq callbacks on remote CPUs

In preparation for the scheduler cpufreq callback happening on remote CPUs, add support for this in intel_pstate, which requires the callback run on the local CPU to be able to change the CPU frequency. Signed-off-by: Steve Muckle --- drivers/cpufreq/intel_pstate.c | 88

[RFC PATCH 4/4] sched/fair: call cpufreq hook for remote wakeups

Without calling the cpufreq hook for a remote wakeup it is possible for such a wakeup to go unnoticed by cpufreq on the target CPU for up to a full tick. This can occur if the target CPU is running a CPU-bound task. Signed-off-by: Steve Muckle --- kernel/sched/fair.c | 8

[RFC PATCH 4/4] sched/fair: call cpufreq hook for remote wakeups

Without calling the cpufreq hook for a remote wakeup it is possible for such a wakeup to go unnoticed by cpufreq on the target CPU for up to a full tick. This can occur if the target CPU is running a CPU-bound task. Signed-off-by: Steve Muckle --- kernel/sched/fair.c | 8 +++-

[RFC PATCH 3/4] intel_pstate: support scheduler cpufreq callbacks on remote CPUs

In preparation for the scheduler cpufreq callback happening on remote CPUs, add support for this in intel_pstate, which requires the callback run on the local CPU to be able to change the CPU frequency. Signed-off-by: Steve Muckle --- drivers/cpufreq/intel_pstate.c | 88

[PATCH v2] drm/rockchip: get rid of rockchip_drm_crtc_mode_config

We need to take care of the vop status when use rockchip_drm_crtc_mode_config, if vop is disabled, the function would failed, that is terrible. Save output_type and output_mode into rockchip_crtc_state, it's nice to make them into atomic. Signed-off-by: Mark Yao ---

[PATCH v2] drm/rockchip: get rid of rockchip_drm_crtc_mode_config

We need to take care of the vop status when use rockchip_drm_crtc_mode_config, if vop is disabled, the function would failed, that is terrible. Save output_type and output_mode into rockchip_crtc_state, it's nice to make them into atomic. Signed-off-by: Mark Yao --- Changes in v2: Advised by

[PATCH] perf script: fix segfault when printing callchains using builtin-script

This fixes a bug caused by an unitialized callchain cursor. The crash frist appeared in: 6f736735e30f ("perf evsel: Require that callchains be resolved before calling fprintf_{sym,callchain}") The callchain cursor is a struct that contains pointers, that when uninitialized will cause

[PATCH] perf script: fix segfault when printing callchains using builtin-script

This fixes a bug caused by an unitialized callchain cursor. The crash frist appeared in: 6f736735e30f ("perf evsel: Require that callchains be resolved before calling fprintf_{sym,callchain}") The callchain cursor is a struct that contains pointers, that when uninitialized will cause

Re: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children

On Tue, 19 Apr 2016 23:05:28 -0300 Daniel Bristot de Oliveira wrote: > On 04/19/2016 11:34 AM, Steven Rostedt wrote: > > This code adds the event-fork option that, when set, will have tasks > > with their PIDs in set_event_pid add their children PIDs when they > > fork. It

Re: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children

On Tue, 19 Apr 2016 23:05:28 -0300 Daniel Bristot de Oliveira wrote: > On 04/19/2016 11:34 AM, Steven Rostedt wrote: > > This code adds the event-fork option that, when set, will have tasks > > with their PIDs in set_event_pid add their children PIDs when they > > fork. It will also remove their

Re: [PATCH 1/2] sched/fair: move cpufreq hook to update_cfs_rq_load_avg()

On Wed, Apr 13, 2016 at 09:50:19PM +0200, Rafael J. Wysocki wrote: > On Wed, Apr 13, 2016 at 8:06 PM, Steve Muckle wrote: > > On 04/13/2016 09:07 AM, Rafael J. Wysocki wrote: > >> If you want to do remote updates, I guess that will require an > >> irq_work to run

Re: [PATCH 1/2] sched/fair: move cpufreq hook to update_cfs_rq_load_avg()

On Wed, Apr 13, 2016 at 09:50:19PM +0200, Rafael J. Wysocki wrote: > On Wed, Apr 13, 2016 at 8:06 PM, Steve Muckle wrote: > > On 04/13/2016 09:07 AM, Rafael J. Wysocki wrote: > >> If you want to do remote updates, I guess that will require an > >> irq_work to run the update on the target

Re: [PATCH] drm/rockchip: get rid of rockchip_drm_crtc_mode_config

On 2016年04月19日 17:06, John Keeping wrote: On Tue, 19 Apr 2016 10:43:03 +0800, Mark yao wrote: On 2016年04月18日 17:25, John Keeping wrote: On Mon, 18 Apr 2016 11:03:31 +0800, Mark Yao wrote: We need to take care of the vop status when use rockchip_drm_crtc_mode_config, if vop is disabled,

Re: [PATCH] drm/rockchip: get rid of rockchip_drm_crtc_mode_config

On 2016年04月19日 17:06, John Keeping wrote: On Tue, 19 Apr 2016 10:43:03 +0800, Mark yao wrote: On 2016年04月18日 17:25, John Keeping wrote: On Mon, 18 Apr 2016 11:03:31 +0800, Mark Yao wrote: We need to take care of the vop status when use rockchip_drm_crtc_mode_config, if vop is disabled,

[PATCH v2 0/7] mmc: sdhci-pltfm: fix and tidy up sdhci_pltfm_init()

Changes in v2: - Remove resource size checking rather than fix it. - Add \n to the tail of the error message Masahiro Yamada (7): mmc: sdhci-pltfm: drop error message for too small MMIO resource size mmc: sdhci-pltfm: check return value of platform_get_irq() mmc: sdhci-pltfm: use

[PATCH v2 0/7] mmc: sdhci-pltfm: fix and tidy up sdhci_pltfm_init()

Changes in v2: - Remove resource size checking rather than fix it. - Add \n to the tail of the error message Masahiro Yamada (7): mmc: sdhci-pltfm: drop error message for too small MMIO resource size mmc: sdhci-pltfm: check return value of platform_get_irq() mmc: sdhci-pltfm: use

[PATCH v2 4/7] mmc: sdhci-pltfm: use devm_ioremap()

Use the managed variant of ioremap(). Signed-off-by: Masahiro Yamada --- Changes in v2: None drivers/mmc/host/sdhci-pltfm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mmc/host/sdhci-pltfm.c b/drivers/mmc/host/sdhci-pltfm.c

[PATCH v2 7/7] mmc: sdhci-pltfm: call platform_get_irq() before sdhci_alloc_host()

Swap the call order of sdhci_alloc_host() and platform_get_irq(). It makes sdhci_alloc_host() the last function that can fail in the sdhci_pltfm_init(). So, we can drop the sdhci_free_host() call from the failure path. Signed-off-by: Masahiro Yamada --- Changes

[PATCH v2 2/7] mmc: sdhci-pltfm: check return value of platform_get_irq()

The function platform_get_irq() can fail; it returns a negative error code on failure. A negative IRQ number will make sdhci_add_host() fail to request IRQ anyway, but it makes sense to let it fail earlier here. Signed-off-by: Masahiro Yamada --- Changes in v2:

[PATCH v2 3/7] mmc: sdhci-pltfm: use devm_request_mem_region()

Use the managed variant of request_mem_region(). Signed-off-by: Masahiro Yamada --- Changes in v2: None drivers/mmc/host/sdhci-pltfm.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/drivers/mmc/host/sdhci-pltfm.c

[PATCH v2 4/7] mmc: sdhci-pltfm: use devm_ioremap()

Use the managed variant of ioremap(). Signed-off-by: Masahiro Yamada --- Changes in v2: None drivers/mmc/host/sdhci-pltfm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mmc/host/sdhci-pltfm.c b/drivers/mmc/host/sdhci-pltfm.c index 8527a7c..5213287 100644 ---

[PATCH v2 7/7] mmc: sdhci-pltfm: call platform_get_irq() before sdhci_alloc_host()

Swap the call order of sdhci_alloc_host() and platform_get_irq(). It makes sdhci_alloc_host() the last function that can fail in the sdhci_pltfm_init(). So, we can drop the sdhci_free_host() call from the failure path. Signed-off-by: Masahiro Yamada --- Changes in v2: None

[PATCH v2 2/7] mmc: sdhci-pltfm: check return value of platform_get_irq()

The function platform_get_irq() can fail; it returns a negative error code on failure. A negative IRQ number will make sdhci_add_host() fail to request IRQ anyway, but it makes sense to let it fail earlier here. Signed-off-by: Masahiro Yamada --- Changes in v2: - Add \n to the tail of the

[PATCH v2 3/7] mmc: sdhci-pltfm: use devm_request_mem_region()

Use the managed variant of request_mem_region(). Signed-off-by: Masahiro Yamada --- Changes in v2: None drivers/mmc/host/sdhci-pltfm.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/drivers/mmc/host/sdhci-pltfm.c b/drivers/mmc/host/sdhci-pltfm.c index

[PATCH v2 5/7] mmc: sdhci-pltfm: use devm_ioremap_resource()

The chain of devm_request_mem_region() and devm_ioremap() can be replaced with devm_ioremap_resource(). Also, we can drop the error messages because devm_ioremap_resource() displays similar messages on error. Signed-off-by: Masahiro Yamada --- Changes in v2: None

[PATCH v2 6/7] mmc: sdhci-pltfm: move devm_ioremap_resource() up

Call devm_ioremap_resource() right after platform_get_resource(). This saves the error check of platform_get_resource() because devm_ioremap_resource() checks if the given resource is NULL. Signed-off-by: Masahiro Yamada --- Changes in v2: None

[PATCH v2 5/7] mmc: sdhci-pltfm: use devm_ioremap_resource()

The chain of devm_request_mem_region() and devm_ioremap() can be replaced with devm_ioremap_resource(). Also, we can drop the error messages because devm_ioremap_resource() displays similar messages on error. Signed-off-by: Masahiro Yamada --- Changes in v2: None

[PATCH v2 6/7] mmc: sdhci-pltfm: move devm_ioremap_resource() up

Call devm_ioremap_resource() right after platform_get_resource(). This saves the error check of platform_get_resource() because devm_ioremap_resource() checks if the given resource is NULL. Signed-off-by: Masahiro Yamada --- Changes in v2: None drivers/mmc/host/sdhci-pltfm.c | 13

[PATCH v2 1/7] mmc: sdhci-pltfm: drop error message for too small MMIO resource size

The requirement resource_size >= 0x100 may not necessarily be reasonable; for example, sdhci-dove appears to sidestep some registers in sdhci_dove_readw(). Moreover, current code displays an error message for too small resource size, but still moves forward. Every DT should be responsible for

[PATCH v2 1/7] mmc: sdhci-pltfm: drop error message for too small MMIO resource size

The requirement resource_size >= 0x100 may not necessarily be reasonable; for example, sdhci-dove appears to sidestep some registers in sdhci_dove_readw(). Moreover, current code displays an error message for too small resource size, but still moves forward. Every DT should be responsible for

Re: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children

On 04/19/2016 11:34 AM, Steven Rostedt wrote: > This code adds the event-fork option that, when set, will have tasks > with their PIDs in set_event_pid add their children PIDs when they > fork. It will also remove their PID from the file on exit. That is a nice feature! I tested it and it works.

Re: [RFC][PATCH 0/4] tracing: Add event-fork to trace tasks children

On 04/19/2016 11:34 AM, Steven Rostedt wrote: > This code adds the event-fork option that, when set, will have tasks > with their PIDs in set_event_pid add their children PIDs when they > fork. It will also remove their PID from the file on exit. That is a nice feature! I tested it and it works.

Re: Umount failing due to a file leak on 3.18 Android

Adding Arve Hjønnevåg and Riley Andrews I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call trace: 39.958108:

Re: Umount failing due to a file leak on 3.18 Android

Adding Arve Hjønnevåg and Riley Andrews I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call trace: 39.958108:

Re: [RESEND PATCH v4] clk/axs10x: Add I2S PLL clock driver

On 04/19, Jose Abreu wrote: > > @Stephen: can you give some input so that I can submit a v6? > I don't prefer putting the second register in the same DT node, but that's really up to the DT reviewers to approve such a design. The current binding has been acked by Rob right? Assuming the new

Re: [RESEND PATCH v4] clk/axs10x: Add I2S PLL clock driver

On 04/19, Jose Abreu wrote: > > @Stephen: can you give some input so that I can submit a v6? > I don't prefer putting the second register in the same DT node, but that's really up to the DT reviewers to approve such a design. The current binding has been acked by Rob right? Assuming the new

[PATCH v2] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

The range is registered into a linked list which can be referenced throughout the lifetime of the driver. Ensure the range's memory is useful for the same lifetime by adding it to the driver's private data structure. The bug was introduced in the driver's initial commit, which was present in

[PATCH v2] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

The range is registered into a linked list which can be referenced throughout the lifetime of the driver. Ensure the range's memory is useful for the same lifetime by adding it to the driver's private data structure. The bug was introduced in the driver's initial commit, which was present in

[PATCH v5 14/14] arm64, acpi, numa: Default enable ACPI_NUMA with NUMA

From: Robert Richter Signed-off-by: Robert Richter Signed-off-by: David Daney --- drivers/acpi/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index

[PATCH v5 14/14] arm64, acpi, numa: Default enable ACPI_NUMA with NUMA

From: Robert Richter Signed-off-by: Robert Richter Signed-off-by: David Daney --- drivers/acpi/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 5ce9f66..bacf245 100644 --- a/drivers/acpi/Kconfig +++

Re: Does anyone care about a race free ptsname?

On Tue, Apr 19, 2016 at 04:39:07PM -0700, H. Peter Anvin wrote: > On 04/19/2016 04:23 PM, Linus Torvalds wrote: > > On Tue, Apr 19, 2016 at 11:44 AM, Eric W. Biederman > > wrote: > >> > >> I will take a look in a minute. Before I do that I want to mention > >> why I care

Re: Does anyone care about a race free ptsname?

On Tue, Apr 19, 2016 at 04:39:07PM -0700, H. Peter Anvin wrote: > On 04/19/2016 04:23 PM, Linus Torvalds wrote: > > On Tue, Apr 19, 2016 at 11:44 AM, Eric W. Biederman > > wrote: > >> > >> I will take a look in a minute. Before I do that I want to mention > >> why I care about /dev/pts/ptmx. >

[PATCH] ARM: dove: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Andrew Lunn Signed-off-by: Stephen Boyd --- arch/arm/mach-dove/common.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH] ARM: dove: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Andrew Lunn Signed-off-by: Stephen Boyd --- arch/arm/mach-dove/common.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/mach-dove/common.c

Re: [PATCH 14/16] vfs: Implement mount_super_once

On April 19, 2016 6:24:12 PM PDT, Linus Torvalds wrote: >On Tue, Apr 19, 2016 at 4:29 PM, Linus Torvalds > wrote: >> >> I _violently_ oppose the stupid DEVPTS_MULTIPLE_INSTANCES config >option. > >So just to show what I want to

Re: [PATCH 14/16] vfs: Implement mount_super_once

On April 19, 2016 6:24:12 PM PDT, Linus Torvalds wrote: >On Tue, Apr 19, 2016 at 4:29 PM, Linus Torvalds > wrote: >> >> I _violently_ oppose the stupid DEVPTS_MULTIPLE_INSTANCES config >option. > >So just to show what I want to actually happen, here's the hacky patch >on top of my (now merged)

[PATCH v5 06/14] arm64, numa: rework numa_add_memblk()

From: Hanjun Guo Rework numa_add_memblk() to update the parameter "u64 size" to "u64 end", this will make it consistent with x86 and simplifies the arm64 ACPI NUMA code to be added later. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter

[PATCH v5 06/14] arm64, numa: rework numa_add_memblk()

From: Hanjun Guo Rework numa_add_memblk() to update the parameter "u64 size" to "u64 end", this will make it consistent with x86 and simplifies the arm64 ACPI NUMA code to be added later. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney ---

[PATCH v5 09/14] acpi, numa: remove unneeded acpi_numa=1

From: Hanjun Guo acpi_numa is default to 0, it's set to -1 when disable acpi numa or when a bad SRAT is parsed, and it's only consumed in srat_disabled() (compare it with 0) to continue parse the SRAT or not, so we don't need to set acpi_numa to 1 when we get a valid SRAT

[PATCH v5 07/14] x86, acpi, numa: cleanup acpi_numa_processor_affinity_init()

From: Hanjun Guo Cleanup acpi_numa_processor_affinity_init() in preparation for its move to drivers/acpi/numa.c. It will be reused by arm64, this has no functional change. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter

[PATCH v5 01/14] acpi, numa: Use pr_fmt() instead of printk

From: Hanjun Guo Just do some cleanups to replace printk with pr_fmt(). Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney --- drivers/acpi/numa.c | 17

[PATCH v5 09/14] acpi, numa: remove unneeded acpi_numa=1

From: Hanjun Guo acpi_numa is default to 0, it's set to -1 when disable acpi numa or when a bad SRAT is parsed, and it's only consumed in srat_disabled() (compare it with 0) to continue parse the SRAT or not, so we don't need to set acpi_numa to 1 when we get a valid SRAT entry. Signed-off-by:

[PATCH v5 07/14] x86, acpi, numa: cleanup acpi_numa_processor_affinity_init()

From: Hanjun Guo Cleanup acpi_numa_processor_affinity_init() in preparation for its move to drivers/acpi/numa.c. It will be reused by arm64, this has no functional change. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney --- arch/x86/mm/srat.c | 21

[PATCH v5 01/14] acpi, numa: Use pr_fmt() instead of printk

From: Hanjun Guo Just do some cleanups to replace printk with pr_fmt(). Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney --- drivers/acpi/numa.c | 17 +++-- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/drivers/acpi/numa.c

[PATCH v5 04/14] acpi, numa: Move acpi_numa_arch_fixup() to ia64 only

From: Robert Richter Since acpi_numa_arch_fixup() is only used in arch ia64, move it there to make a generic interface easier. This avoids empty function stubs or some complex kconfig options for x86 and arm64. Signed-off-by: Robert Richter

[PATCH v5 03/14] acpi, numa: remove duplicate NULL check

From: Hanjun Guo The argument "header" for acpi_table_print_srat_entry() is always checked before the function is called, it's duplicate to check it again, remove it. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter

[PATCH v5 08/14] acpi, numa: move bad_srat() and srat_disabled() to drivers/acpi/numa.c

From: Hanjun Guo bad_srat() and srat_disabled() are shared by x86 and follow-on arm64 patches. Move them to drivers/acpi/numa.c in preparation for arm64 support. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter

[PATCH v5 04/14] acpi, numa: Move acpi_numa_arch_fixup() to ia64 only

From: Robert Richter Since acpi_numa_arch_fixup() is only used in arch ia64, move it there to make a generic interface easier. This avoids empty function stubs or some complex kconfig options for x86 and arm64. Signed-off-by: Robert Richter Signed-off-by: David Daney ---

[PATCH v5 03/14] acpi, numa: remove duplicate NULL check

From: Hanjun Guo The argument "header" for acpi_table_print_srat_entry() is always checked before the function is called, it's duplicate to check it again, remove it. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney --- drivers/acpi/numa.c | 3 --- 1 file

[PATCH v5 08/14] acpi, numa: move bad_srat() and srat_disabled() to drivers/acpi/numa.c

From: Hanjun Guo bad_srat() and srat_disabled() are shared by x86 and follow-on arm64 patches. Move them to drivers/acpi/numa.c in preparation for arm64 support. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter [david.da...@cavium.com moved definitions to drivers/acpi/numa.c]

[PATCH v5 12/14] arm64, acpi, numa: NUMA support based on SRAT and SLIT

From: Hanjun Guo Introduce a new file to hold ACPI based NUMA information parsing from SRAT and SLIT. SRAT includes the CPU ACPI ID to Proximity Domain mappings and memory ranges to Proximity Domain mapping. SLIT has the information of inter node distances(relative

[PATCH v5 11/14] acpi, numa, srat: Improve SRAT error detection and add messages.

From: David Daney Loosely based on code from Robert Richter and Hanjun Guo. Improve out of range node detection as well as allow for Larger SRAT entities. Add printing of nice messages. Signed-off-by: David Daney --- drivers/acpi/numa.c | 15

[PATCH v5 10/14] acpi, numa: Move acpi_numa_memory_affinity_init() to drivers/acpi/numa.c

From: Hanjun Guo acpi_numa_memory_affinity_init() will be reused by arm64. Move it to drivers/acpi/numa.c to facilitate reuse. No code change. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David

[PATCH v5 13/14] acpi, numa: Enable ACPI based NUMA on ARM64

From: Hanjun Guo Add function needed for cpu to node mapping, and enable ACPI based NUMA for ARM64 in Kconfig Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney ---

[PATCH v5 11/14] acpi, numa, srat: Improve SRAT error detection and add messages.

From: David Daney Loosely based on code from Robert Richter and Hanjun Guo. Improve out of range node detection as well as allow for Larger SRAT entities. Add printing of nice messages. Signed-off-by: David Daney --- drivers/acpi/numa.c | 15 +++ 1 file changed, 11

[PATCH v5 10/14] acpi, numa: Move acpi_numa_memory_affinity_init() to drivers/acpi/numa.c

From: Hanjun Guo acpi_numa_memory_affinity_init() will be reused by arm64. Move it to drivers/acpi/numa.c to facilitate reuse. No code change. Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney --- arch/x86/mm/srat.c | 57

[PATCH v5 13/14] acpi, numa: Enable ACPI based NUMA on ARM64

From: Hanjun Guo Add function needed for cpu to node mapping, and enable ACPI based NUMA for ARM64 in Kconfig Signed-off-by: Hanjun Guo Signed-off-by: Robert Richter Signed-off-by: David Daney --- drivers/acpi/Kconfig | 2 +- drivers/acpi/numa.c | 35 +++

[PATCH v5 12/14] arm64, acpi, numa: NUMA support based on SRAT and SLIT

From: Hanjun Guo Introduce a new file to hold ACPI based NUMA information parsing from SRAT and SLIT. SRAT includes the CPU ACPI ID to Proximity Domain mappings and memory ranges to Proximity Domain mapping. SLIT has the information of inter node distances(relative number for access latency).

[PATCH v5 05/14] acpi, numa: move acpi_numa_slit_init() to drivers/acpi/numa.c

From: Hanjun Guo Identical implementations of acpi_numa_slit_init() are used by both x86 and follow-on arm64 support. Move it to drivers/acpi/numa.c, and guard with CONFIG_X86 || CONFIG_ARM64 because ia64 has its own architecture specific implementation. No code change.

RE: [PATCH kernel 1/2] mm: add the related functions to build the free page bitmap

> Cc: Rik van Riel; v...@zeniv.linux.org.uk; linux-kernel@vger.kernel.org; > quint...@redhat.com; amit.s...@redhat.com; pbonz...@redhat.com; > dgilb...@redhat.com; linux...@kvack.org; k...@vger.kernel.org; qemu- > de...@nongnu.org; ag...@suse.de; borntrae...@de.ibm.com > Subject: Re: [PATCH kernel

[PATCH v5 02/14] acpi, numa: Replace ACPI_DEBUG_PRINT() with pr_debug()

From: Hanjun Guo ACPI_DEBUG_PRINT is a bit fragile in acpi/numa.c, the first thing is that component ACPI_NUMA(0x8000) is not described in the Documentation/acpi/debug.txt, and even not defined in the struct acpi_dlayer acpi_debug_layers which we can not dynamically

RE: [PATCH kernel 1/2] mm: add the related functions to build the free page bitmap

> Cc: Rik van Riel; v...@zeniv.linux.org.uk; linux-kernel@vger.kernel.org; > quint...@redhat.com; amit.s...@redhat.com; pbonz...@redhat.com; > dgilb...@redhat.com; linux...@kvack.org; k...@vger.kernel.org; qemu- > de...@nongnu.org; ag...@suse.de; borntrae...@de.ibm.com > Subject: Re: [PATCH kernel

[PATCH v5 02/14] acpi, numa: Replace ACPI_DEBUG_PRINT() with pr_debug()

From: Hanjun Guo ACPI_DEBUG_PRINT is a bit fragile in acpi/numa.c, the first thing is that component ACPI_NUMA(0x8000) is not described in the Documentation/acpi/debug.txt, and even not defined in the struct acpi_dlayer acpi_debug_layers which we can not dynamically enable/disable it with

[PATCH v5 05/14] acpi, numa: move acpi_numa_slit_init() to drivers/acpi/numa.c

From: Hanjun Guo Identical implementations of acpi_numa_slit_init() are used by both x86 and follow-on arm64 support. Move it to drivers/acpi/numa.c, and guard with CONFIG_X86 || CONFIG_ARM64 because ia64 has its own architecture specific implementation. No code change. Signed-off-by: Hanjun

[PATCH v5 00/14] ACPI NUMA support for ARM64

From: David Daney Based on v16 of device-tree NUMA patch set for arm64 [1],this patch set introduce the ACPI based configuration to provide NUMA information. ACPI 5.1 already introduced NUMA support for ARM64, which can get the NUMA domain information from SRAT and SLIT

[PATCH v5 00/14] ACPI NUMA support for ARM64

From: David Daney Based on v16 of device-tree NUMA patch set for arm64 [1],this patch set introduce the ACPI based configuration to provide NUMA information. ACPI 5.1 already introduced NUMA support for ARM64, which can get the NUMA domain information from SRAT and SLIT table, so parse those

[PATCH] ARM: mv78xx0: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Andrew Lunn Cc: Jason Cooper --- arch/arm/mach-mv78xx0/common.c | 3 +-- 1 file changed, 1

[PATCH] ARM: mv78xx0: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Andrew Lunn Cc: Jason Cooper --- arch/arm/mach-mv78xx0/common.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/mach-mv78xx0/common.c

[PATCH] ARM: orion5x: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Andrew Lunn Signed-off-by: Stephen Boyd --- arch/arm/mach-orion5x/common.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH] ARM: orion5x: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Andrew Lunn Signed-off-by: Stephen Boyd --- arch/arm/mach-orion5x/common.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/mach-orion5x/common.c

[PATCH] ARM: pxa: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Signed-off-by: Stephen Boyd --- arch/arm/mach-pxa/eseries.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-pxa/eseries.c

[PATCH] ARM: pxa: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Signed-off-by: Stephen Boyd --- arch/arm/mach-pxa/eseries.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-pxa/eseries.c b/arch/arm/mach-pxa/eseries.c

[PATCH] vexpress/spc: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Signed-off-by: Stephen Boyd --- arch/arm/mach-vexpress/spc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-vexpress/spc.c

[PATCH] vexpress/spc: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Signed-off-by: Stephen Boyd --- arch/arm/mach-vexpress/spc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-vexpress/spc.c b/arch/arm/mach-vexpress/spc.c

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher wrote: > On 12.04.2016 13:09, Tejun Heo wrote: >>> >>> Probably you want to look into: >>> https://lkml.org/lkml/2016/3/10/21 >>> >>> The patch mentioned above solves the issue for me. >> >> Heh, I tracked it down to

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher wrote: > On 12.04.2016 13:09, Tejun Heo wrote: >>> >>> Probably you want to look into: >>> https://lkml.org/lkml/2016/3/10/21 >>> >>> The patch mentioned above solves the issue for me. >> >> Heh, I tracked it down to wb_over_bg_thresh() and

[PATCH] MIPS: alchemy: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Manuel Lauss Signed-off-by: Stephen Boyd --- arch/mips/alchemy/common/clock.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)

[PATCH] MIPS: alchemy: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Manuel Lauss Signed-off-by: Stephen Boyd --- arch/mips/alchemy/common/clock.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/mips/alchemy/common/clock.c

[PATCH] MIPS: ath79: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Antony Pavlov Signed-off-by: Stephen Boyd --- arch/mips/ath79/clock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] MIPS: ath79: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Antony Pavlov Signed-off-by: Stephen Boyd --- arch/mips/ath79/clock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/mips/ath79/clock.c

[PATCH] powerpc/512x: clk: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Gerhard Sittig Signed-off-by: Stephen Boyd --- arch/powerpc/platforms/512x/clock-commonclk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] powerpc/512x: clk: Remove CLK_IS_ROOT

This flag is a no-op now (see commit 47b0eeb3dc8a "clk: Deprecate CLK_IS_ROOT", 2016-02-02) so remove it. Cc: Gerhard Sittig Signed-off-by: Stephen Boyd --- arch/powerpc/platforms/512x/clock-commonclk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v11 5/9] arm64: Kprobes with single stepping support

Hi David, on 2016/3/9 13:32, David Long wrote: > +int __kprobes arch_prepare_kprobe(struct kprobe *p) > +{ > + unsigned long probe_addr = (unsigned long)p->addr; Here should verify the addr alignment: if (probe_addr & 0x3) return -EINVAL; Thanks, Li Bin > + > +

Re: [PATCH v11 5/9] arm64: Kprobes with single stepping support

Hi David, on 2016/3/9 13:32, David Long wrote: > +int __kprobes arch_prepare_kprobe(struct kprobe *p) > +{ > + unsigned long probe_addr = (unsigned long)p->addr; Here should verify the addr alignment: if (probe_addr & 0x3) return -EINVAL; Thanks, Li Bin > + > +

Re: Umount failing due to a file leak on 3.18 Android

On Tue 19 Apr 2016 06:26:27 PM PDT, Nikhilesh Reddy wrote: Hi I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call

Re: Umount failing due to a file leak on 3.18 Android

On Tue 19 Apr 2016 06:26:27 PM PDT, Nikhilesh Reddy wrote: Hi I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call

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