linaro-kernel April 2014

linaro-kernel@lists.linaro.org

103 participants
204 discussions

Re: [RFC PATCH v3] ARM: uprobes need icache flush after xol write

by David Miller

From: Oleg Nesterov <oleg(a)redhat.com> Date: Wed, 16 Apr 2014 17:29:46 +0200 > On 04/16, David Miller wrote: >> >> From: Oleg Nesterov <oleg(a)redhat.com> >> Date: Wed, 16 Apr 2014 17:06:46 +0200 >> >> > Off-topic, I am just curious... can't someone explain why flush_pfn_alias() >> > or flush_icache_alias() can't race with itself ? I have no idea what they do, >> > but what if another thread calls the same function with the same CACHE_COLOUR() >> > right after set_pte_ext? >> >> PTE modifications are supposed to run with the page table lock held. > > OK, but __access_remote_vm() doesn't take ptl? > > And on arm copy_to_user_page()->flush_ptrace_access()->flush_pfn_alias() > does this. Well, for one thing, PTE's can't gain permissions except under mmap_sem which __access_remote_vm() does hold. But I see what you're saying, flush_pfn_alias() is doing something different. It's not making user mappings, but kernel ones in order to implement the cache flush. On sparc64 we handle this situation by hand-loading the mappings into the TLB, doing the operation using the mappings, then flushing it out of the TLB, all with interrupts disabled. Furthermore, in ARMs case, the code explicitly states that these mappings are not used on SMP. See the comment above the FLUSH_ALIAS_START definition in arch/arm/mm/mm.h

10 years

[PATCH v4 0/5] rework sched_domain topology description

by Vincent Guittot

This patchset was previously part of the larger tasks packing patchset [1]. I have splitted the latter in 3 different patchsets (at least) to make the thing easier. -configuration of sched_domain topology (this patchset) -update and consolidation of cpu_power -tasks packing algorithm Based on Peter Z's proposal [2][3], this patchset modifies the way to configure the sched_domain level in order to let architectures to add specific level like the current BOOK level or the proposed power gating level for ARM architecture. [1] https://lkml.org/lkml/2013/10/18/121 [2] https://lkml.org/lkml/2013/11/5/239 [3] https://lkml.org/lkml/2013/11/5/449 Change since v3: - remove last patch which was adding SD_SHARE_POWER_DOMAIN for powerpc's SMT level Change since v2: - remove patch 1 as it has been already applied to metag tree for v3.15 - updates some commit messages - add new flag description in TOPOLOGY_SD_FLAGS description Change since v1: - move sched_domains_curr_level back under #ifdef CONFIG_NUMA - use function pointer to set flag instead of a plain value. - add list of tunable flags in the commit message of patch 2 - add SD_SHARE_POWER_DOMAIN flag for powerpc's SMT level Vincent Guittot (5): sched: rework of sched_domain topology definition sched: s390: create a dedicated topology table sched: powerpc: create a dedicated topology table sched: add a new SD_SHARE_POWERDOMAIN for sched_domain sched: ARM: create a dedicated scheduler topology table arch/arm/kernel/topology.c | 26 +++++ arch/ia64/include/asm/topology.h | 24 ---- arch/powerpc/kernel/smp.c | 31 +++-- arch/s390/include/asm/topology.h | 13 +-- arch/s390/kernel/topology.c | 20 ++++ arch/tile/include/asm/topology.h | 33 ------ include/linux/sched.h | 49 +++++++- include/linux/topology.h | 128 +++----------------- kernel/sched/core.c | 244 ++++++++++++++++++++------------------- 9 files changed, 255 insertions(+), 313 deletions(-) -- 1.9.1

10 years

Urgency,thanks: Arm declared the current A53 bugs:one's recommended soution is given below. using DCCIMVAC instead ,don't use DCCMVAC or DCCMVAU

by Panshilin (Peter)

________________________________ 发件人: Panshilin (Peter) 发送时间: 2014年4月25日 13:52 收件人: linaro-kernel(a)lists.linaro.org 主题: Arm declared the current A53 bugs:one's recommended soution is given below. using DCCIMVAC instead ,don't use DCCMVAC or DCCMVAU Hi all: Arm has declared the current A53 bugs:one's recommended soution is given below. has linaro kernel team known and is there patches in current LSK for aarch64? 824069: Cache line might not be marked as clean after a CleanShared snoop Status Affects: Cortex-A53 MPCore Fault Type: Programmer Category B Fault Status: Present in: r0p0, r0p1, r0p2 Open. Description If a Cortex-A53 processor is executing a store or PLDW instruction at the same time as a processor in another cluster is executing a cache maintenance operation to the same address, then this erratum might cause a clean cache line to be incorrectly marked as dirty. Configurations affected This erratum affects all configurations of the Cortex-A53 processor when it is connected to a coherent interconnect. Workaround Date of Issue: 11-Mar-2014 ARM Product Errata Notice Document Revision 9.0 ARM-EPM-048405 v9.0 Confidential. Page 24 of 40 © Copyright ARM 2014. All rights reserved. The majority of systems will not need a workaround for this erratum. For any systems that do need a workaround, any software that uses DCCMVAC or DCCMVAU instructions can replace them with DCCIMVAC instructions, or their AArch64 equivalents. Note that this workaround must be applied to all the masters in the system that might generate a snoop into the Cortex-A53 cluster. For example, on a big.LITTLE configuration with one Cortex-A53 processor and one Cortex-A57 processor, the workaround needs to be applied to all software running on the Cortex-A57 processor. On a Cortex-A57 processor it is possible to set bit 44 in the CPUACTLR_EL1 register to automatically convert all DCCMVAC and DCCMVAU instructions into DCCIMVAC instructions.

10 years

[PATCH] cpufreq: Set CPUFREQ_ASYNC_NOTIFICATION for drivers handling notification

by Viresh Kumar

CPUFREQ_ASYNC_NOTIFICATION was initially designed for drivers which don't want core to send notifications for them as they wouldn't finish frequency transitions in ->target_index(). But there were other kinds of drivers as well who don't have straight forward implementations of ->target_index() routines and wanted to handle notifications themselves. Patch: 7dbf694 (cpufreq: distinguish drivers that do asynchronous notifications) missed addressing these drivers and that caused these drivers to send double notifications. Initially cpufreq core sends a notification for these and then the drivers themselves. It might not cause a big problem for kernels (3.13/3.14) which doesn't have this patch in: 12478cf (cpufreq: Make sure frequency transitions are serialized), as this came in v3.15-rc1. Reason being, we are sending an extra notification for the same frequency, and so other kernel code that depends on it shouldn't behave badly. Above patch broke things as it forces serialization of notifications, so that we aren't configuring same hardware registers simultaneously. Reported-by: Meelis Roos <mroos(a)linux.ee> Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- Hi Rafael, This one is for rc3 surely :) Also, as I mentioned above it might not create any problems for 3.13 and 3.14. And so I havne't cc'd stable for those kernels. Please add them in case you feel its still better to get it fixed. drivers/cpufreq/longhaul.c | 1 + drivers/cpufreq/powernow-k6.c | 1 + drivers/cpufreq/powernow-k7.c | 1 + 3 files changed, 3 insertions(+) diff --git a/drivers/cpufreq/longhaul.c b/drivers/cpufreq/longhaul.c index d00e5d1..41f3d28 100644 --- a/drivers/cpufreq/longhaul.c +++ b/drivers/cpufreq/longhaul.c @@ -909,6 +909,7 @@ static int longhaul_cpu_init(struct cpufreq_policy *policy) } static struct cpufreq_driver longhaul_driver = { + .flags = CPUFREQ_ASYNC_NOTIFICATION, .verify = cpufreq_generic_frequency_table_verify, .target_index = longhaul_target, .get = longhaul_get, diff --git a/drivers/cpufreq/powernow-k6.c b/drivers/cpufreq/powernow-k6.c index 49f120e..080bbb9 100644 --- a/drivers/cpufreq/powernow-k6.c +++ b/drivers/cpufreq/powernow-k6.c @@ -242,6 +242,7 @@ static unsigned int powernow_k6_get(unsigned int cpu) } static struct cpufreq_driver powernow_k6_driver = { + .flags = CPUFREQ_ASYNC_NOTIFICATION, .verify = cpufreq_generic_frequency_table_verify, .target_index = powernow_k6_target, .init = powernow_k6_cpu_init, diff --git a/drivers/cpufreq/powernow-k7.c b/drivers/cpufreq/powernow-k7.c index f911645..fccfc25 100644 --- a/drivers/cpufreq/powernow-k7.c +++ b/drivers/cpufreq/powernow-k7.c @@ -677,6 +677,7 @@ static int powernow_cpu_exit(struct cpufreq_policy *policy) } static struct cpufreq_driver powernow_driver = { + .flags = CPUFREQ_ASYNC_NOTIFICATION, .verify = cpufreq_generic_frequency_table_verify, .target_index = powernow_target, .get = powernow_get, -- 1.7.12.rc2.18.g61b472e

10 years

a question about juice project: how did you deal with the iptables component in 32 android/64 kernel mode.

by Panshilin (Peter)

Hi all concerned: there will have some problems about the external software components like iptables when they are running in kernel 64 . because these components interactive by netlink and share structures between the usrer space and kernel space. How the juice team work to meet these problems? whether the juice team have noticed and verify these android external components. Best Regards Peter

10 years

Arm declared the current A53 bugs:one's recommended soution is given below. using DCCIMVAC instead ,don't use DCCMVAC or DCCMVAU

by Panshilin (Peter)

Hi all: Arm has declared the current A53 bugs:one's recommended soution is given below. has linaro kernel team known and is there patches in current LSK for aarch64? 824069: Cache line might not be marked as clean after a CleanShared snoop Status Affects: Cortex-A53 MPCore Fault Type: Programmer Category B Fault Status: Present in: r0p0, r0p1, r0p2 Open. Description If a Cortex-A53 processor is executing a store or PLDW instruction at the same time as a processor in another cluster is executing a cache maintenance operation to the same address, then this erratum might cause a clean cache line to be incorrectly marked as dirty. Configurations affected This erratum affects all configurations of the Cortex-A53 processor when it is connected to a coherent interconnect. Workaround Date of Issue: 11-Mar-2014 ARM Product Errata Notice Document Revision 9.0 ARM-EPM-048405 v9.0 Confidential. Page 24 of 40 © Copyright ARM 2014. All rights reserved. The majority of systems will not need a workaround for this erratum. For any systems that do need a workaround, any software that uses DCCMVAC or DCCMVAU instructions can replace them with DCCIMVAC instructions, or their AArch64 equivalents. Note that this workaround must be applied to all the masters in the system that might generate a snoop into the Cortex-A53 cluster. For example, on a big.LITTLE configuration with one Cortex-A53 processor and one Cortex-A57 processor, the workaround needs to be applied to all software running on the Cortex-A57 processor. On a Cortex-A57 processor it is possible to set bit 44 in the CPUACTLR_EL1 register to automatically convert all DCCMVAC and DCCMVAU instructions into DCCIMVAC instructions.

10 years

[RFC 0/4] Migrate timers away from cpuset on setting cpuset.quiesce

by Viresh Kumar

For networking platforms we need to provide one isolated CPU per user space data plane thread. These CPUs should not be interrupted by kernel at all unless userspace has requested for some syscalls. And so must live in isolated mode. Currently, there are background kernel activities that are running on almost every CPU, like: timers/hrtimers/watchdogs/etc, and these are required to be migrated to other CPUs. This patchset tries to migrate un-pinned timers away in the first attempt. And support for migrating others like hrtimers/workqueues/etc would be added later. This has only went through basic testing currently on ARM Samsung Exynos board which only has two CPUs. Separate cpusets were created for these two CPUs and then timers were migrated from one cpuset to other. This option was earlier suggested by Peter Z. here. https://lkml.org/lkml/2014/1/15/186 Please provide your inputs on how this can be improved.. Viresh Kumar (4): timer: track pinned timers with TIMER_PINNED flag timer: don't migrate pinned timers timer: create timer_quiesce_cpu() for cpusets.quiesce option cpuset: Add cpusets.quiesce option include/linux/timer.h | 10 +++--- kernel/cpuset.c | 56 +++++++++++++++++++++++++++++++ kernel/timer.c | 92 +++++++++++++++++++++++++++++++++++++++++---------- 3 files changed, 136 insertions(+), 22 deletions(-) -- 1.7.12.rc2.18.g61b472e

10 years

arm-soc boot: 48 pass, 0 fail (v3.15-rc2-74-g1fc52762)

by Kevin's boot bot

Tree/Branch: arm-soc Git describe: v3.15-rc2-74-g1fc52762 Full Report =========== arm-davinci_all_defconfig ------------------------- legacy,dm365evm 0 min 17.3 sec: PASS da850-evm 0 min 15.8 sec: PASS arm-tegra_defconfig ------------------- tegra30-beaver 0 min 17.2 sec: PASS arm-omap2plus_defconfig ----------------------- legacy,3730xm 0 min 51.7 sec: PASS am335x-boneblack 0 min 44.2 sec: PASS omap3-beagle-xm 1 min 0.9 sec: PASS legacy,3530beagle 0 min 40.5 sec: PASS (Warnings: 1) omap4-panda 1 min 11.3 sec: PASS omap3-overo-tobi 0 min 23.2 sec: PASS (Warnings: 1) am335x-bone 0 min 27.8 sec: PASS omap3-overo-storm-tobi 0 min 24.8 sec: PASS omap5-uevm 1 min 4.2 sec: PASS (Warnings: 1) omap3-n900 0 min 17.2 sec: PASS (Warnings: 1) legacy,n900 0 min 17.1 sec: PASS (Warnings: 1) omap4-panda-es 1 min 10.2 sec: PASS legacy,3730storm 0 min 23.2 sec: PASS legacy,3530overo 0 min 21.4 sec: PASS (Warnings: 1) arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual 0 min 18.6 sec: PASS imx6dl-wandboard,wand-solo 0 min 18.9 sec: PASS imx6q-wandboard 0 min 17.1 sec: PASS arm-multi_v7_defconfig ---------------------- qcom-apq8074-dragonboard 0 min 25.7 sec: PASS ste-snowball 1 min 18.1 sec: PASS tegra30-beaver 0 min 23.8 sec: PASS am335x-boneblack 0 min 38.5 sec: PASS omap3-beagle-xm 0 min 48.8 sec: PASS sun7i-a20-cubieboard2 0 min 18.2 sec: PASS armada-370-mirabox 0 min 27.2 sec: PASS omap4-panda 0 min 52.3 sec: PASS armada-xp-openblocks-ax3-4 0 min 26.2 sec: PASS sun4i-a10-cubieboard 0 min 19.3 sec: PASS bcm28155-ap 0 min 27.7 sec: PASS omap3-overo-tobi 0 min 22.3 sec: PASS (Warnings: 1) imx6dl-wandboard,wand-solo 0 min 18.1 sec: PASS am335x-bone 0 min 27.4 sec: PASS omap3-overo-storm-tobi 0 min 25.6 sec: PASS omap5-uevm 1 min 40.6 sec: PASS (Warnings: 1) omap3-n900 0 min 16.3 sec: PASS (Warnings: 1) imx6q-wandboard 0 min 16.9 sec: PASS omap4-panda-es 0 min 58.5 sec: PASS imx6dl-wandboard,wand-dual 0 min 18.1 sec: PASS arm-sunxi_defconfig ------------------- sun7i-a20-cubieboard2 0 min 22.9 sec: PASS sun4i-a10-cubieboard 0 min 13.1 sec: PASS arm-bcm_defconfig ----------------- bcm28155-ap 0 min 24.9 sec: PASS arm-exynos_defconfig -------------------- exynos5250-arndale 0 min 31.0 sec: PASS arm-u8500_defconfig ------------------- ste-snowball 0 min 33.7 sec: PASS arm-mvebu_v7_defconfig ---------------------- armada-xp-openblocks-ax3-4 0 min 22.2 sec: PASS armada-370-mirabox 0 min 20.4 sec: PASS arm-sama5_defconfig ------------------- sama5d35ek 0 min 17.7 sec: PASS

10 years

mainline boot: 48 pass, 0 fail (v3.15-rc2-107-g76429f1)

by Kevin's boot bot

Tree/Branch: mainline Git describe: v3.15-rc2-107-g76429f1 Full Report =========== arm-davinci_all_defconfig ------------------------- legacy,dm365evm 0 min 17.4 sec: PASS da850-evm 0 min 15.4 sec: PASS arm-tegra_defconfig ------------------- tegra30-beaver 0 min 17.2 sec: PASS arm-omap2plus_defconfig ----------------------- legacy,3730xm 0 min 52.3 sec: PASS am335x-boneblack 0 min 43.8 sec: PASS omap3-beagle-xm 1 min 3.9 sec: PASS legacy,3530beagle 0 min 33.9 sec: PASS (Warnings: 1) omap4-panda 1 min 7.1 sec: PASS omap3-overo-tobi 0 min 23.3 sec: PASS (Warnings: 1) am335x-bone 0 min 27.4 sec: PASS omap3-overo-storm-tobi 0 min 22.4 sec: PASS omap5-uevm 1 min 1.2 sec: PASS (Warnings: 1) omap3-n900 0 min 16.4 sec: PASS (Warnings: 1) legacy,n900 0 min 17.0 sec: PASS (Warnings: 1) omap4-panda-es 1 min 10.0 sec: PASS legacy,3730storm 0 min 23.0 sec: PASS legacy,3530overo 0 min 21.3 sec: PASS (Warnings: 1) arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual 0 min 19.0 sec: PASS imx6dl-wandboard,wand-solo 0 min 18.6 sec: PASS imx6q-wandboard 0 min 17.1 sec: PASS arm-multi_v7_defconfig ---------------------- qcom-apq8074-dragonboard 0 min 17.4 sec: PASS ste-snowball 1 min 21.5 sec: PASS tegra30-beaver 0 min 17.2 sec: PASS am335x-boneblack 0 min 38.9 sec: PASS omap3-beagle-xm 0 min 56.1 sec: PASS sun7i-a20-cubieboard2 0 min 12.3 sec: PASS armada-370-mirabox 0 min 22.3 sec: PASS omap4-panda 0 min 55.0 sec: PASS armada-xp-openblocks-ax3-4 0 min 25.3 sec: PASS sun4i-a10-cubieboard 0 min 18.9 sec: PASS bcm28155-ap 0 min 26.9 sec: PASS omap3-overo-tobi 0 min 22.3 sec: PASS (Warnings: 1) imx6dl-wandboard,wand-solo 0 min 17.9 sec: PASS am335x-bone 0 min 26.8 sec: PASS omap3-overo-storm-tobi 0 min 24.1 sec: PASS omap5-uevm 1 min 43.3 sec: PASS (Warnings: 1) omap3-n900 0 min 15.9 sec: PASS (Warnings: 1) imx6q-wandboard 0 min 16.8 sec: PASS omap4-panda-es 0 min 53.9 sec: PASS imx6dl-wandboard,wand-dual 0 min 18.3 sec: PASS arm-sunxi_defconfig ------------------- sun7i-a20-cubieboard2 0 min 22.7 sec: PASS sun4i-a10-cubieboard 0 min 16.1 sec: PASS arm-bcm_defconfig ----------------- bcm28155-ap 0 min 23.7 sec: PASS arm-exynos_defconfig -------------------- exynos5250-arndale 0 min 30.0 sec: PASS arm-u8500_defconfig ------------------- ste-snowball 0 min 31.1 sec: PASS arm-mvebu_v7_defconfig ---------------------- armada-xp-openblocks-ax3-4 0 min 22.3 sec: PASS armada-370-mirabox 0 min 20.5 sec: PASS arm-sama5_defconfig ------------------- sama5d35ek 0 min 17.3 sec: PASS

10 years

mainline boot: 48 pass, 0 fail (v3.15-rc2-78-gdb725c8)

by Kevin's boot bot

Tree/Branch: mainline Git describe: v3.15-rc2-78-gdb725c8 Full Report =========== arm-davinci_all_defconfig ------------------------- legacy,dm365evm 0 min 17.4 sec: PASS da850-evm 0 min 15.6 sec: PASS arm-tegra_defconfig ------------------- tegra30-beaver 0 min 17.2 sec: PASS arm-omap2plus_defconfig ----------------------- legacy,3730xm 0 min 50.5 sec: PASS am335x-boneblack 0 min 44.0 sec: PASS omap3-beagle-xm 0 min 59.0 sec: PASS legacy,3530beagle 0 min 39.2 sec: PASS (Warnings: 1) omap4-panda 1 min 5.8 sec: PASS omap3-overo-tobi 0 min 23.5 sec: PASS (Warnings: 1) am335x-bone 0 min 27.5 sec: PASS omap3-overo-storm-tobi 0 min 24.8 sec: PASS omap5-uevm 0 min 57.6 sec: PASS (Warnings: 1) omap3-n900 0 min 44.0 sec: PASS (Warnings: 1) legacy,n900 0 min 17.1 sec: PASS (Warnings: 1) omap4-panda-es 1 min 9.2 sec: PASS legacy,3730storm 0 min 20.0 sec: PASS legacy,3530overo 0 min 21.3 sec: PASS (Warnings: 1) arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual 0 min 18.7 sec: PASS imx6dl-wandboard,wand-solo 0 min 19.1 sec: PASS imx6q-wandboard 0 min 17.1 sec: PASS arm-multi_v7_defconfig ---------------------- qcom-apq8074-dragonboard 0 min 16.6 sec: PASS ste-snowball 1 min 17.3 sec: PASS tegra30-beaver 0 min 17.4 sec: PASS am335x-boneblack 0 min 38.1 sec: PASS omap3-beagle-xm 0 min 49.0 sec: PASS sun7i-a20-cubieboard2 0 min 12.4 sec: PASS armada-370-mirabox 0 min 22.4 sec: PASS omap4-panda 0 min 59.8 sec: PASS armada-xp-openblocks-ax3-4 0 min 26.5 sec: PASS sun4i-a10-cubieboard 0 min 14.5 sec: PASS bcm28155-ap 0 min 27.7 sec: PASS omap3-overo-tobi 0 min 22.3 sec: PASS (Warnings: 1) imx6dl-wandboard,wand-solo 0 min 18.1 sec: PASS am335x-bone 0 min 26.8 sec: PASS omap3-overo-storm-tobi 0 min 23.4 sec: PASS omap5-uevm 1 min 38.3 sec: PASS (Warnings: 1) omap3-n900 0 min 33.9 sec: PASS (Warnings: 1) imx6q-wandboard 0 min 16.9 sec: PASS omap4-panda-es 0 min 51.8 sec: PASS imx6dl-wandboard,wand-dual 0 min 18.4 sec: PASS arm-sunxi_defconfig ------------------- sun7i-a20-cubieboard2 0 min 22.8 sec: PASS sun4i-a10-cubieboard 0 min 17.7 sec: PASS arm-bcm_defconfig ----------------- bcm28155-ap 0 min 23.7 sec: PASS arm-exynos_defconfig -------------------- exynos5250-arndale 0 min 30.4 sec: PASS arm-u8500_defconfig ------------------- ste-snowball 0 min 32.0 sec: PASS arm-mvebu_v7_defconfig ---------------------- armada-xp-openblocks-ax3-4 0 min 22.2 sec: PASS armada-370-mirabox 0 min 20.4 sec: PASS arm-sama5_defconfig ------------------- sama5d35ek 0 min 17.2 sec: PASS

10 years

← Newer
1
2
3
4
5
6
7
8
9
...
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel April 2014