- linaro-kernel - lists.linaro.org

[PATCH 1/2] net/ipv4: queue work on power efficient wq

by Viresh Kumar

Workqueue used in ipv4 layer have no real dependency of scheduling these on the cpu which scheduled them. On a idle system, it is observed that an idle cpu wakes up many times just to service this work. It would be better if we can schedule it on a cpu which the scheduler believes to be the most appropriate one. This patch replaces normal workqueues with power efficient versions. This doesn't change existing behavior of code unless CONFIG_WQ_POWER_EFFICIENT is enabled. Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- Initial support for power-efficient workqueues was added here: https://lkml.org/lkml/2013/4/24/215 net/ipv4/devinet.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c index 646023b..ac2dff3 100644 --- a/net/ipv4/devinet.c +++ b/net/ipv4/devinet.c @@ -474,7 +474,7 @@ static int __inet_insert_ifa(struct in_ifaddr *ifa, struct nlmsghdr *nlh, inet_hash_insert(dev_net(in_dev->dev), ifa); cancel_delayed_work(&check_lifetime_work); - schedule_delayed_work(&check_lifetime_work, 0); + queue_delayed_work(system_power_efficient_wq, &check_lifetime_work, 0); /* Send message first, then call notifier. Notifier will trigger FIB update, so that @@ -684,7 +684,8 @@ static void check_lifetime(struct work_struct *work) if (time_before(next_sched, now + ADDRCONF_TIMER_FUZZ_MAX)) next_sched = now + ADDRCONF_TIMER_FUZZ_MAX; - schedule_delayed_work(&check_lifetime_work, next_sched - now); + queue_delayed_work(system_power_efficient_wq, &check_lifetime_work, + next_sched - now); } static void set_ifa_lifetime(struct in_ifaddr *ifa, __u32 valid_lft, @@ -842,7 +843,8 @@ static int inet_rtm_newaddr(struct sk_buff *skb, struct nlmsghdr *nlh) ifa = ifa_existing; set_ifa_lifetime(ifa, valid_lft, prefered_lft); cancel_delayed_work(&check_lifetime_work); - schedule_delayed_work(&check_lifetime_work, 0); + queue_delayed_work(system_power_efficient_wq, + &check_lifetime_work, 0); rtmsg_ifa(RTM_NEWADDR, ifa, nlh, NETLINK_CB(skb).portid); blocking_notifier_call_chain(&inetaddr_chain, NETDEV_UP, ifa); } @@ -2322,7 +2324,7 @@ void __init devinet_init(void) register_gifconf(PF_INET, inet_gifconf); register_netdevice_notifier(&ip_netdev_notifier); - schedule_delayed_work(&check_lifetime_work, 0); + queue_delayed_work(system_power_efficient_wq, &check_lifetime_work, 0); rtnl_af_register(&inet_af_ops); -- 1.7.12.rc2.18.g61b472e

11 years, 4 months

2
3
0 0

mainline boot: 37 pass, 0 fail (v3.13-3780-gfe41c2c)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-3780-gfe41c2c Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 26.2 sec omap3-beagle-xm PASS: 1 min 1.1 sec am335x-bone PASS: 0 min 27.4 sec omap3-tobi,3530overo PASS: 0 min 22.6 sec omap4-panda PASS: 1 min 9.9 sec omap4-panda-es PASS: 1 min 10.1 sec omap3-tobi,3730storm PASS: 0 min 21.7 sec omap3-beagle PASS: 1 min 21.0 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 PASS: 0 min 13.8 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.2 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.4 sec imx6dl-wandboard,wand-solo PASS: 0 min 19.1 sec imx6q-wandboard PASS: 0 min 17.3 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.2 sec sun4i-a10-cubieboard PASS: 0 min 15.5 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.1 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 30.5 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 29.4 sec tegra30-beaver PASS: 0 min 17.0 sec am335x-boneblack PASS: 0 min 22.5 sec omap3-beagle-xm PASS: 0 min 59.3 sec sun7i-a20-cubieboard2 PASS: 0 min 23.6 sec armada-370-mirabox PASS: 0 min 20.6 sec omap4-panda PASS: 1 min 1.3 sec omap4-panda-es PASS: 1 min 1.9 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.5 sec sun4i-a10-cubieboard PASS: 0 min 13.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.3 sec omap3-tobi,3530overo PASS: 0 min 20.9 sec am335x-bone PASS: 0 min 24.4 sec imx6q-wandboard PASS: 0 min 17.6 sec omap3-tobi,3730storm PASS: 0 min 23.2 sec imx6dl-wandboard,wand-dual PASS: 0 min 18.5 sec omap3-beagle PASS: 0 min 53.5 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 30.6 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec

11 years, 4 months

1
0
0 0

queue boot: 34 pass, 1 fail (v3.12.8-25-g45e6db5)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: queue Git describe: v3.12.8-25-g45e6db5 Failed boot tests (console logs at the end) =========================================== omap3-beagle: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.0 sec omap3-beagle-xm PASS: 0 min 59.4 sec am335x-bone PASS: 0 min 27.0 sec omap3-tobi,3530overo PASS: 0 min 22.0 sec omap4-panda PASS: 1 min 14.6 sec omap4-panda-es PASS: 1 min 9.0 sec omap3-tobi,3730storm PASS: 0 min 24.2 sec omap3-beagle PASS: 0 min 35.8 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 PASS: 0 min 13.7 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.1 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.1 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.8 sec imx6q-wandboard PASS: 0 min 15.3 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.9 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.6 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 28.5 sec tegra30-beaver PASS: 0 min 14.2 sec am335x-boneblack PASS: 0 min 32.3 sec omap3-beagle-xm PASS: 0 min 56.1 sec sun7i-a20-cubieboard2 PASS: 0 min 13.8 sec armada-370-mirabox PASS: 0 min 20.6 sec omap4-panda PASS: 1 min 7.5 sec omap4-panda-es PASS: 1 min 8.5 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.5 sec sun4i-a10-cubieboard PASS: 0 min 21.6 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.0 sec omap3-tobi,3530overo PASS: 0 min 23.4 sec am335x-bone PASS: 0 min 33.9 sec imx6q-wandboard PASS: 0 min 16.4 sec omap3-tobi,3730storm PASS: 0 min 23.1 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.5 sec omap3-beagle FAIL: 1 min 42.8 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 36.7 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.3 sec Console logs for failures ========================= multi_v7_defconfig ------------------ omap3-beagle: FAIL: last 24 lines of boot log: ---------------------------------------------- tftp 0x80200000 192.168.1.2:tmp/3530beagle-99PAgi/zImage Using asx0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.164 Filename 'tmp/3530beagle-99PAgi/zImage'. Load address: 0x80200000 Loading: *###################################################EHCI timed out on TD - token=0x8008d80 T ############## ######################T ###############T T T Abort OMAP3 beagleboard.org # tftp 0x80200000 192.168.1.2:tmp/3530beagle-99PAgi/zImage tftp 0x80200000 192.168.1.2:tmp/3530beagle-99PAgi/zImage EHCI timed out on TD - token=0x80008d80 ERROR: Need valid 'usbnet_devaddr' to be set at ether.c:2362/usb_eth_init() OMAP3 beagleboard.org # tftp 0x80200000 192.168.1.2:tmp/3530beagle-99PAgi/zImage <INTERRUPT> OMAP3 beagleboard.org # tftp 0x80200000 192.168.1.2:tmp/3530beagle-99PAgi/zImage EHCI timed out on TD - token=0x80008d80 ERROR: Need valid 'usbnet_devaddr' to be set at ether.c:2362/usb_eth_init() OMAP3 beagleboard.org # ~$off # PYBOOT: Exception: ERROR: Timeout loading 192.168.1.2:tmp/3530beagle-99PAgi/zImage. Giving up. # PYBOOT: Time: 102.76 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

mainline boot: 37 pass, 0 fail (v3.13-3667-ge1ba845)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-3667-ge1ba845 Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 26.2 sec omap3-beagle-xm PASS: 0 min 56.9 sec am335x-bone PASS: 0 min 27.4 sec omap3-tobi,3530overo PASS: 0 min 22.5 sec omap4-panda PASS: 1 min 7.7 sec omap4-panda-es PASS: 1 min 3.7 sec omap3-tobi,3730storm PASS: 0 min 22.1 sec omap3-beagle PASS: 1 min 7.8 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 PASS: 0 min 19.0 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.1 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 19.3 sec imx6q-wandboard PASS: 0 min 17.4 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 11.9 sec sun4i-a10-cubieboard PASS: 0 min 12.6 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.1 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 30.0 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 32.6 sec tegra30-beaver PASS: 0 min 14.3 sec am335x-boneblack PASS: 0 min 22.6 sec omap3-beagle-xm PASS: 0 min 54.3 sec sun7i-a20-cubieboard2 PASS: 0 min 13.8 sec armada-370-mirabox PASS: 0 min 20.7 sec omap4-panda PASS: 1 min 1.6 sec omap4-panda-es PASS: 1 min 7.1 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.2 sec sun4i-a10-cubieboard PASS: 0 min 13.6 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.2 sec omap3-tobi,3530overo PASS: 0 min 21.1 sec am335x-bone PASS: 0 min 24.2 sec imx6q-wandboard PASS: 0 min 17.8 sec omap3-tobi,3730storm PASS: 0 min 23.5 sec imx6dl-wandboard,wand-dual PASS: 0 min 18.5 sec omap3-beagle PASS: 1 min 10.6 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 31.0 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec

11 years, 4 months

1
0
0 0

arm-soc boot: 36 pass, 1 fail (v3.13-rc5-1194-gdbd3277)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.13-rc5-1194-gdbd3277 Failed boot tests (console logs at the end) =========================================== omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.4 sec omap3-beagle-xm PASS: 0 min 57.5 sec am335x-bone PASS: 0 min 27.4 sec omap3-tobi,3530overo PASS: 0 min 22.6 sec omap4-panda PASS: 1 min 18.0 sec omap4-panda-es PASS: 1 min 11.3 sec omap3-tobi,3730storm PASS: 0 min 21.7 sec omap3-beagle PASS: 0 min 42.4 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 PASS: 0 min 14.2 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.6 sec imx6dl-wandboard,wand-solo PASS: 0 min 19.2 sec imx6q-wandboard PASS: 0 min 17.6 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 11.8 sec sun4i-a10-cubieboard PASS: 0 min 13.8 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.0 sec armada-370-mirabox PASS: 0 min 20.2 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 30.3 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 16.7 sec tegra30-beaver PASS: 0 min 16.9 sec am335x-boneblack PASS: 0 min 23.4 sec omap3-beagle-xm PASS: 0 min 51.7 sec sun7i-a20-cubieboard2 PASS: 0 min 14.2 sec armada-370-mirabox PASS: 0 min 21.3 sec omap4-panda PASS: 0 min 51.2 sec omap4-panda-es FAIL: 1 min 44.7 sec armada-xp-openblocks-ax3-4 PASS: 0 min 23.9 sec sun4i-a10-cubieboard PASS: 0 min 19.1 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.8 sec omap3-tobi,3530overo PASS: 0 min 21.3 sec am335x-bone PASS: 0 min 25.0 sec imx6q-wandboard PASS: 0 min 17.3 sec omap3-tobi,3730storm PASS: 0 min 24.3 sec imx6dl-wandboard,wand-dual PASS: 0 min 18.0 sec omap3-beagle PASS: 0 min 41.6 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 28.3 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec Console logs for failures ========================= multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ I2C: ready DRAM: 1 GiB MMC: OMAP SD/MMC: 0 Using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 3 2 1 0 mmc0 is current device SD/MMC found on device 0 reading boot.scr ** Unable to read file boot.scr ** reading uEnv.txt 435 bytes read in 4 ms (105.5 KiB/s) Importing environment from mmc0 ... Running uenvcmd ... (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 104.74 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

mainline boot: 37 pass, 0 fail (v3.13-3477-gdf32e43)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-3477-gdf32e43 Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.7 sec omap3-beagle-xm PASS: 1 min 0.2 sec am335x-bone PASS: 0 min 27.1 sec omap3-tobi,3530overo PASS: 0 min 22.6 sec omap4-panda PASS: 1 min 3.9 sec omap4-panda-es PASS: 1 min 12.7 sec omap3-tobi,3730storm PASS: 0 min 25.2 sec omap3-beagle PASS: 0 min 34.8 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 PASS: 0 min 13.9 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 20.7 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 19.9 sec imx6dl-wandboard,wand-solo PASS: 0 min 20.3 sec imx6q-wandboard PASS: 0 min 17.4 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 11.8 sec sun4i-a10-cubieboard PASS: 0 min 12.9 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.8 sec armada-370-mirabox PASS: 0 min 19.9 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.0 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 32.3 sec tegra30-beaver PASS: 0 min 14.2 sec am335x-boneblack PASS: 0 min 22.5 sec omap3-beagle-xm PASS: 0 min 56.4 sec sun7i-a20-cubieboard2 PASS: 0 min 23.8 sec armada-370-mirabox PASS: 0 min 20.6 sec omap4-panda PASS: 1 min 3.9 sec omap4-panda-es PASS: 1 min 7.2 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.4 sec sun4i-a10-cubieboard PASS: 0 min 13.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.1 sec omap3-tobi,3530overo PASS: 0 min 21.2 sec am335x-bone PASS: 0 min 24.1 sec imx6q-wandboard PASS: 0 min 16.7 sec omap3-tobi,3730storm PASS: 0 min 24.9 sec imx6dl-wandboard,wand-dual PASS: 0 min 18.6 sec omap3-beagle PASS: 0 min 34.2 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 27.8 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec

11 years, 4 months

1
0
0 0

[PATCH] regmap: irq: Remove domain on exit

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> irqdomain now supports removal of domains on exit so we can properly clean up on deletion of a regmap irqchip. Signed-off-by: Mark Brown <broonie(a)linaro.org> --- drivers/base/regmap/regmap-irq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/base/regmap/regmap-irq.c b/drivers/base/regmap/regmap-irq.c index 82692068d3cb..52ce0c17c68b 100644 --- a/drivers/base/regmap/regmap-irq.c +++ b/drivers/base/regmap/regmap-irq.c @@ -533,7 +533,7 @@ void regmap_del_irq_chip(int irq, struct regmap_irq_chip_data *d) return; free_irq(irq, d); - /* We should unmap the domain but... */ + irq_domain_remove(d->domain); kfree(d->wake_buf); kfree(d->mask_buf_def); kfree(d->mask_buf); -- 1.8.5.3

11 years, 4 months

1
0
0 0

[PATCH] watchdog: Add sp805_wdt depends on ARM64

by naresh.bhat＠linaro.org

From: Naresh Bhat <naresh.bhat(a)linaro.org> Add sp805_wdt depends on ARM64. Signed-off-by: Naresh Bhat <naresh.bhat(a)linaro.org> --- drivers/watchdog/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig index 5be6e91..2385124 100644 --- a/drivers/watchdog/Kconfig +++ b/drivers/watchdog/Kconfig @@ -109,7 +109,7 @@ config WM8350_WATCHDOG config ARM_SP805_WATCHDOG tristate "ARM SP805 Watchdog" - depends on ARM && ARM_AMBA + depends on (ARM || ARM64) && ARM_AMBA select WATCHDOG_CORE help ARM Primecell SP805 Watchdog timer. This will reboot your system when -- 1.7.9.5

11 years, 4 months

3
2
0 0

[PATCH] sched: fix sched_entity avg statistics update

by Vincent Guittot

With the current implementation, the load average statistics of a sched entity change according to other activity on the CPU even if this activity is done between the running window of the sched entity and have no influence on the running duration of the task. When a task wakes up on the same CPU, we currently update last_runnable_update with the return of __synchronize_entity_decay without updating the runnable_avg_sum and runnable_avg_period accordingly. In fact, we have to sync the load_contrib of the se with the rq's blocked_load_contrib before removing it from the latter (with __synchronize_entity_decay) but we must keep last_runnable_update unchanged for updating runnable_avg_sum/period during the next update_entity_load_avg. Signed-off-by: Vincent Guittot <vincent.guittot(a)linaro.org> --- kernel/sched/fair.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index e64b079..5b0ef90 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -2370,8 +2370,7 @@ static inline void enqueue_entity_load_avg(struct cfs_rq *cfs_rq, * would have made count negative); we must be careful to avoid * double-accounting blocked time after synchronizing decays. */ - se->avg.last_runnable_update += __synchronize_entity_decay(se) - << 20; + __synchronize_entity_decay(se); } /* migrated tasks did not contribute to our blocked load */ -- 1.7.9.5

11 years, 4 months

5
10
0 0

[LSK PATCH 0/8] big.LITTLE MP fixes

by Jon Medhurst

This is a series of fixes for big.LITTLE MP. Patches 1, 2, 3, 6 & 8 are defect fixes. Patches 4 & 5 are to including packing in the TC2 build. Patch 7 is an old patch which accidentally got ommited from LSK. Contents ---------------------------------------------------------------- [PATCH 1/8] sched: reset blocked load decay_count during [PATCH 2/8] sched: update runqueue clock before migrations away [PATCH 3/8] sched: hmp: Make idle balance behaviour normal when [PATCH 4/8] sched: hmp: Change TC2 packing config to disabled [PATCH 5/8] config: Make packing present on TC2 [PATCH 6/8] sched: hmp: Fix potential task_struct memory leak [PATCH 7/8] HMP: Restrict irq_default_affinity to hmp_slow_cpu_mask [PATCH 8/8] HMP: Fix rt task allowed cpu mask restriction code on kernel/irq/irqdesc.c | 8 +++++++ kernel/sched/core.c | 5 ++++- kernel/sched/fair.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++--------- linaro/configs/big-LITTLE-MP.conf | 1 + 4 files changed, 69 insertions(+), 11 deletions(-)

11 years, 4 months

5
23
0 0

Re: [PATCH v6 0/3] AArch64: KGDB support

by Vijay Kilari

On Wed, Jan 22, 2014 at 12:06 AM, Will Deacon <will.deacon(a)arm.com> wrote: > On Tue, Jan 21, 2014 at 02:10:14PM +0000, Vijay Kilari wrote: >> Hi Will, > > Hello Vijay, > >> On Mon, Jan 20, 2014 at 3:53 PM, Will Deacon <will.deacon(a)arm.com> wrote: >> > Well, the warnings are one thing but the 100 miles of backtrace output that >> > appear on every boot (and I think end in an oops) are probably more >> > important to fix. Please enable CONFIG_KGDB_TESTS and >> > CONFIG_KGDB_TESTS_ON_BOOT and take a look. >> > >> >> I could manage to run KGDB boot tests if I run from sysfs after complete boot >> >> echo V1F1000 > /sys/module/kgdbts/parameters/kgdbts >> >> Here the value of PSTATE is 80000145, which means PSTATE.D is unmasked >> hence it works fine. >> >> If I run during boot by enabling CONFIG_KGDB_TESTS_ON_BOOT, >> the step debug test fail because value of PSTATE is 80000345. >> If I force PSTATE.D to 0, it works fine >> >> In debug_monitors.c file, only PSTATE.SS & MDSCR.KDE/MDE is managed >> but not PSTATE.D >> >> Can you please let me know if where PSTATE.D is managed in arm64? > > That's a good point: I think we wait until our first exception before they > are unmasked. Perhaps we should: > > (1) Move local_dbg_{save,restore} from debug-monitors.h into irqflags.h > (2) Add local_dbg_enable/local_dbg_disable macros > (3) Add a call to local_dbg_enable in the clear_os_lock function after the > isb(). > > Does that work for you? Yes, only after first exception occurs the PSTATE.D is unmasked. I have patched (temp) as below and now KGDB boot tests pass diff --git a/arch/arm64/include/asm/debug-monitors.h b/arch/arm64/include/asm/debug-monitors.h index aff3a76..ea2bc46 100644 --- a/arch/arm64/include/asm/debug-monitors.h +++ b/arch/arm64/include/asm/debug-monitors.h @@ -64,6 +111,24 @@ struct task_struct; #define DBG_ARCH_ID_RESERVED 0 /* In case of ptrace ABI updates. */ +#define local_dbg_enable() \ + do { \ + asm volatile( \ + "msr daifclr, #9 // arch_local_irq_disable" \ + : \ + : \ + : "memory"); \ + } while (0) + +#define local_dbg_disable() \ + do { \ + asm volatile( \ + "msr daifset, #9 // arch_local_irq_disable" \ + : \ + : \ + : "memory"); \ + } while (0) + struct step_hook { struct list_head node; int (*fn)(struct pt_regs *regs, unsigned int insn, unsigned long addr); diff --git a/arch/arm64/kernel/debug-monitors.c b/arch/arm64/kernel/debug-monitors.c index f8b90c0..d0e55f7 100644 --- a/arch/arm64/kernel/debug-monitors.c +++ b/arch/arm64/kernel/debug-monitors.c @@ -139,6 +142,7 @@ static void clear_os_lock(void *unused) { asm volatile("msr oslar_el1, %0" : : "r" (0)); isb(); + local_dbg_enable(); } boot test: [32927.161317] msgmni has been set to 1870 [32927.212747] alg: No test for stdrng (krng) [32927.213953] Key type asymmetric registered [32927.214899] Asymmetric key parser 'x509' registered [32927.220029] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [32927.225824] io scheduler noop registered [32927.226764] io scheduler deadline registered [32927.230714] io scheduler cfq registered (default) [32927.237895] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [32927.266066] kgdb: Registered I/O driver kgdbts. [32927.266419] kgdb: Waiting for connection from remote gdb... [32927.268598] kgdbts:RUN plant and detach test [32927.270683] kgdbts:RUN sw breakpoint test [32927.287659] kgdbts:RUN bad memory access test [32927.290322] kgdbts:RUN singlestep test 1000 iterations [32927.330342] kgdbts:RUN singlestep [0/1000] [32931.286356] kgdbts:RUN singlestep [100/1000] [32935.242536] kgdbts:RUN singlestep [200/1000] [32939.205392] kgdbts:RUN singlestep [300/1000] [32943.169522] kgdbts:RUN singlestep [400/1000] [32947.231868] kgdbts:RUN singlestep [500/1000] [32951.188008] kgdbts:RUN singlestep [600/1000] [32955.332243] kgdbts:RUN singlestep [700/1000] [32959.467109] kgdbts:RUN singlestep [800/1000] [32963.430888] kgdbts:RUN singlestep [900/1000] [32967.346992] kgdbts:RUN do_fork for 100 breakpoints kgdb test using sysfs: ~ # echo V1F1000 > /sys/module/kgdbts/parameters/kgdbts [33231.554237] kgdb: Registered I/O driver kgdbts. [33231.554677] kgdbts:RUN plant and detach test [33231.557072] kgdbts:RUN sw breakpoint test [33231.576980] kgdbts:RUN bad memory access test [33231.580022] kgdbts:RUN singlestep test 1000 iterations [33231.627056] kgdbts:RUN singlestep [0/1000] [33235.954027] kgdbts:RUN singlestep [100/1000] [33240.429086] kgdbts:RUN singlestep [200/1000] [33244.687118] kgdbts:RUN singlestep [300/1000] [33248.945191] kgdbts:RUN singlestep [400/1000] [33253.203751] kgdbts:RUN singlestep [500/1000] [33257.462019] kgdbts:RUN singlestep [600/1000] [33261.817809] kgdbts:RUN singlestep [700/1000] [33266.081268] kgdbts:RUN singlestep [800/1000] [33270.339813] kgdbts:RUN singlestep [900/1000] [33274.712404] kgdbts:RUN do_fork for 1000 breakpoints ~ # This works for me. Should I patch it or will you send a patch for this? PS: cc to mailing list missed > > Will

11 years, 4 months

2
2
0 0

[PATCH REPOST 0/5] armv7 BE kvm support

by Victor Kamensky

[repost: adding kvmarm mailing list as per Christoffer's request] Hi Guys, Here is series that enables KVM support for V7 big endian kernels. Mostly it deals with BE KVM host support. Marc Zyngier showed before with his patches how BE guest could run on top LE host. With these patches BE guest runs on top of BE host. If Marc's kvmtool is used with few additional changes I tested that BE host could run LE guest. Also I verified that there were no regressions in BE guest on top of LE host case. Note that posted series covers only kernel side changes. The changes were tested inside of bigger setup with additional changes in qemu and kvmtool. I will post those changes separately in proper aliases but for completeness sake Appendix A gives pointers to git repositories and branches with all needed changes. Please note first patch is not related to BE KVM per se. I've run into an issue of conflicting 'push' identifier use while trying to include assembler.h into KVM .S files. Details of an issue I observed covered in Appendix B. The first patch is my take on solving it. Victor Kamensky (5): ARM: kvm: replace push and pop with stdmb and ldmia instrs to enable assembler.h inclusion ARM: fix KVM assembler files to work in BE case ARM: kvm one_reg coproc set and get BE fixes ARM: kvm vgic mmio should return data in BE format in BE case ARM: kvm MMIO support BE host running LE code arch/arm/include/asm/assembler.h | 7 +++ arch/arm/include/asm/kvm_asm.h | 4 +- arch/arm/include/asm/kvm_emulate.h | 22 +++++++-- arch/arm/kvm/coproc.c | 94 ++++++++++++++++++++++++++++---------- arch/arm/kvm/init.S | 7 ++- arch/arm/kvm/interrupts.S | 50 +++++++++++--------- arch/arm/kvm/interrupts_head.S | 61 +++++++++++++++---------- virt/kvm/arm/vgic.c | 4 +- 8 files changed, 168 insertions(+), 81 deletions(-) -- 1.8.1.4 Thanks, Victor Appendix A: Testing and Full Setup Description ---------------------------------------------- I) No mixed mode setup - i.e BE guest on BE host; and LE guest on LE host tested to make sure no regressions. KVM host and guest kernels: TC2 on top of Linus 3.13-rc4 (this patch series): git: git://git.linaro.org/people/victor.kamensky/linux-linaro-tracking-be.git branch: armv7be-kvm-3.13-rc4 TC2 and Arndale on top of Linaro BE tree: git: git://git.linaro.org/people/victor.kamensky/linux-linaro-tracking-be.git branch: llct-be-20131216-kvm - TC1 kernels used as guests qemu: git: git://git.linaro.org/people/victor.kamensky/qemu-be.git branch: armv7be-v1 description: changes to run qemu on armeb target; and other changes to work with be image on top of be host kvmtool: git: git://git.linaro.org/people/victor.kamensky/linux-linaro-tracking-be.git branch: kvmtool-armv7be-v1 desciption: minimal changes to build kvmtool for armeb target; and tiny change with virtio magic II) Mixed mode setup all possible combinations within V7 (LE guest on BE host; BE guest on LE host as Marc's setup tested to make sure no regressions) only with kvmtool. This work is based on Marc Zyngier's work that made BE guest to run on top of LE host. For this setup special version of kvmtool should be used and in addition I had to apply patch to guest kernel that would switch reading virtio configs reads to be LE only, that is made on top of previous Rusty Russell's changes. Effectively I just had to do very minor addition to make LE guest to work on BE host, most of heavy lifting was done before by Marc. KVM host kernels: as in previous setup Guest TC1 kernels with LE virtio config patch: git: git://git.linaro.org/people/victor.kamensky/linux-linaro-tracking-be.git branch: virtio-leconfig-3.13-rc4 kvmtool: git: git://git.linaro.org/people/victor.kamensky/linux-linaro-tracking-be.git branch: kvmtool-mixed-v1 description: based on git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git branch kvm-arm64/kvmtool-be-on-le; adds missing include fix; above armeb target build patches; and one fix related to BE mode qemu: git: git://git.linaro.org/people/victor.kamensky/qemu-be.git branch: armv7be-leconfig-v1 description: change virtio-blk that so qemu could work with guest image where virtio leconfig is made; note it does not work in mixed mode; to do so qemu would need bunch of similar changes that Marc did in kvmtool Appendix B: kvm asm file and asm/assembler.h file issue ------------------------------------------------------- diff --git a/arch/arm/kvm/interrupts.S b/arch/arm/kvm/interrupts.S index ddc1553..5d3b511 100644 --- a/arch/arm/kvm/interrupts.S +++ b/arch/arm/kvm/interrupts.S @@ -25,6 +25,7 @@ #include <asm/kvm_asm.h> #include <asm/kvm_arm.h> #include <asm/vfpmacros.h> +#include <asm/assembler.h> #include "interrupts_head.S" .text produce the following compilation errors: /run/media/kamensky/wd/linaro/linux-linaro-core-tracking/092913/linux-linaro-tracking-be/arch/arm/kvm/interrupts.S: Assembler messages: /run/media/kamensky/wd/linaro/linux-linaro-core-tracking/092913/linux-linaro-tracking-be/arch/arm/kvm/interrupts.S:51: Error: ARM register expected -- `lsr {r2,r3}' /run/media/kamensky/wd/linaro/linux-linaro-core-tracking/092913/linux-linaro-tracking-be/arch/arm/kvm/interrupts.S:100: Error: ARM register expected -- `lsr {r2}' /run/media/kamensky/wd/linaro/linux-linaro-core-tracking/092913/linux-linaro-tracking-be/arch/arm/kvm/interrupts.S:100: Error: ARM register expected -- `lsr {r4-r12}'

11 years, 4 months

6
25
0 0

[PATCH] ARM64: perf: support dwarf unwinding in compat mode

by Jean Pihet

Add support for unwinding using the dwarf information in compat mode. Using the correct user stack pointer allows perf to record the frames correctly in the native and compat modes. Note that although the dwarf frame unwinding works ok using libunwind in native mode (on ARMv7 & ARMv8), some changes are required to the libunwind code for the compat mode. Those changes are posted separately on the libunwind mailing list. Tested on ARMv8 platform with v8 and compat v7 binaries, the latter are statically built. Signed-off-by: Jean Pihet <jean.pihet(a)linaro.org> --- arch/arm64/include/asm/ptrace.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/include/asm/ptrace.h b/arch/arm64/include/asm/ptrace.h index fbb0020..86d5b54 100644 --- a/arch/arm64/include/asm/ptrace.h +++ b/arch/arm64/include/asm/ptrace.h @@ -133,7 +133,7 @@ struct pt_regs { (!((regs)->pstate & PSR_F_BIT)) #define user_stack_pointer(regs) \ - ((regs)->sp) + (!compat_user_mode(regs)) ? ((regs)->sp) : ((regs)->compat_sp) /* * Are the current registers suitable for user mode? (used to maintain -- 1.7.11.7

11 years, 4 months

2
8
0 0

Re: [alsa-devel] [PATCH] ASoC: da9055: Partially fix device

by Opensource [Adam Thomson]

On Wed, 8 Jan 2014 20:38:55 +0000, Mark Brown wrote: > It has never been possible to even load the da9055 driver since both the > MFD and CODEC drivers register the I2C device "da9055". Fix this by using > the usual pattern for MFDs with multiple I2C addresses and having the CODEC > driver reference an I2C dummy registered by the MFD. > Since I don't know which I2C address to use for the CODEC a FIXME has been > left in the MFD, this doesn't make anything any worse since the device has > never been able to load in the first place. What you're saying here is incorrect, as previously discussed at length in this thread: http://mailman.alsa-project.org/pipermail/alsa-devel/2013-September/066027.… The two drivers did work together fine until someone in 3.12 changed the PMIC I2C Id back to just 'da9055' and broke it again. Also, I wanted to add a simple patch to tidy up the I2C Id names and avoid this but you would not agree. The codec part can be standalone and by doing what you've done here means that customers would need to now add additional, unnecessary code to be able to use just the codec driver. This is not right to me.

11 years, 4 months

2
11
0 0

[PATCH 1/4] sched: Remove 'cpu' parameter for idle_balance()

by Daniel Lezcano

The cpu parameter passed to idle_balance is not needed as it could be retrieved from the struct rq. Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- kernel/sched/core.c | 2 +- kernel/sched/fair.c | 3 ++- kernel/sched/sched.h | 2 +- 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 36c951b..cf51601 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -2680,7 +2680,7 @@ need_resched: pre_schedule(rq, prev); if (unlikely(!rq->nr_running)) - idle_balance(cpu, rq); + idle_balance(rq); put_prev_task(rq, prev); next = pick_next_task(rq); diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index b24b6cf..d601df3 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -6359,12 +6359,13 @@ out: * idle_balance is called by schedule() if this_cpu is about to become * idle. Attempts to pull tasks from other CPUs. */ -void idle_balance(int this_cpu, struct rq *this_rq) +void idle_balance(struct rq *this_rq) { struct sched_domain *sd; int pulled_task = 0; unsigned long next_balance = jiffies + HZ; u64 curr_cost = 0; + int this_cpu = this_rq->cpu; this_rq->idle_stamp = rq_clock(this_rq); diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h index c2119fd..b0be4c6 100644 --- a/kernel/sched/sched.h +++ b/kernel/sched/sched.h @@ -1176,7 +1176,7 @@ extern const struct sched_class idle_sched_class; extern void update_group_power(struct sched_domain *sd, int cpu); extern void trigger_load_balance(struct rq *rq); -extern void idle_balance(int this_cpu, struct rq *this_rq); +extern void idle_balance(struct rq *this_rq); extern void idle_enter_fair(struct rq *this_rq); extern void idle_exit_fair(struct rq *this_rq); -- 1.7.9.5

11 years, 4 months

2
20
0 0

[discussion] simpler load balance in scheduler

by Alex Shi

Paul & Vincent & Morten, The following rough idea get during this KS. I want to have internal review before send to LKML. Would you like to give some comments? ========================== 1, Current scheduler load balance is bottom-up mode, each CPU need initiate the balance by self. Like in a integrate computer system, it has smt/core/cpu/numa, 4 level scheduler domains. If there is just 2 tasks in whole system that both running on cpu0. Current load balance need to pull task to another smt in smt domain, then pull task to another core, then pull task to another cpu, finally pull task to another numa. Totally it is need 4 times task moving to get system balance. Generally, the task moving complexity is O(nm log n), n := nr_cpus, m := nr_tasks PeterZ has a excellent summary and explanation for this in kernel/sched/fair.c:4605 Another weakness of current LB is that every cpu need to get the other cpus' load info repeatedly and try to figure out busiest sched group/queue on every sched domain level. but may not conduct a task moving, one of reasons is that cpu can only pull task, not pushing. 2, Consider huge cost of task moving: CS, tlb/cache refill, and the useless remote cpu load info getting. If we can have better solution for load balance, like reduce the balance times to. O(m) m := nr_tasks It will be a great win on performance. like above example, we can move task from cpu0 direct to another numa. that only need 1 task moving, save 3 CS and tlb/cache refill. To get this point, a rough idea is changing the load balance behaviour to top-down mode. Say let each of cpu report self load status on per-cpu memory. And a baby-sitter in system to collect these cpus load info, then decide how to move task centralize, finally send IPI to each hungry cpu to let them pull load quota from appointed cpus. Like in above example, the baby-sitter will fetch each cpus' load info, then send a pull task IPI to let a cpu in another numa pull one task from cpu0. So in the task pulling, we still just involved 2 cpus, can reuse move_tasks functions. BTW, the baby-sitter can care all kind of balance, regular balance, idle balance, wake up balance. 3, One of concern of top-down mode is that baby-sitter need remote access cpu load info on top domain level every times. But the fact is current load balance also need to get remote cpu load info for top level domain balance. and more worse, such remote accessing maybe useless. -- since there is just one thread reading the info, no competitor writer, Paul, do you think it is worthy concern? BTW, to reduce unnecessary remote info fetching, we can use current idle_cpus_mask in nohz, we just skip the idle cpu in this cpumask simply. 4, From power saving POV, top-down give the whole system cpu topology info directly. So beside the CS reducing, it can reduce the idle cpu interfere by a transition task. and let idle cpu sleep better. -- Thanks Alex

11 years, 4 months

3
14
0 0

[PATCH] ASoC: omap: Make RX51 depend on GPIOLIB due to jack usage

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> Since the GPIO jacks are only supported if gpiolib is built and fail to compile otherwise add a build depedency. This is unlikely to have any practical impact outside of coverage testing. Reported-by: Russell King <linux(a)arm.linux.org.uk> Signed-off-by: Mark Brown <broonie(a)linaro.org> --- sound/soc/omap/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/sound/soc/omap/Kconfig b/sound/soc/omap/Kconfig index 4a07f7179690..22ad9c5654b5 100644 --- a/sound/soc/omap/Kconfig +++ b/sound/soc/omap/Kconfig @@ -30,6 +30,7 @@ config SND_OMAP_SOC_RX51 select SND_OMAP_SOC_MCBSP select SND_SOC_TLV320AIC3X select SND_SOC_TPA6130A2 + depends on GPIOLIB help Say Y if you want to add support for SoC audio on Nokia RX-51 hardware. This is also known as Nokia N900 product. -- 1.8.5.2

11 years, 4 months

2
1
0 0

[PATCH] ARM: asm: __und_usr_thumb need byteswap instructions in BE case

by Victor Kamensky

__und_usr_thumb function deals with thumb2 opcodes. In case of BE image, it needs to byteswap half word thumb2 encoded instructions before further processing them. Without this fix BE image user-land thread executing first VFP instruction encoded in thumb2 fails with SIGILL, because kernel does not recognize instruction and does not enable VFP. Reported-by: Corey Melton <comelton(a)cisco.com> Signed-off-by: Victor Kamensky <victor.kamensky(a)linaro.org> --- arch/arm/kernel/entry-armv.S | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/kernel/entry-armv.S b/arch/arm/kernel/entry-armv.S index b3fb8c9..1879e8d 100644 --- a/arch/arm/kernel/entry-armv.S +++ b/arch/arm/kernel/entry-armv.S @@ -451,9 +451,11 @@ __und_usr_thumb: .arch armv6t2 #endif 2: ldrht r5, [r4] +ARM_BE8(rev16 r5, r5) @ little endian instruction cmp r5, #0xe800 @ 32bit instruction if xx != 0 blo __und_usr_fault_16 @ 16bit undefined instruction 3: ldrht r0, [r2] +ARM_BE8(rev16 r0, r0) @ little endian instruction add r2, r2, #2 @ r2 is PC + 2, make it PC + 4 str r2, [sp, #S_PC] @ it's a 2x16bit instr, update orr r0, r0, r5, lsl #16 -- 1.8.1.4

11 years, 4 months

3
3
0 0

[PATCH 0/3] ACPI: Some patches to prepare for running ACPI on !x86 and !ia64

by Hanjun Guo

Some of the ACPI code is arch-dependent and make the code can't be compiled on !x86 and !ia64, the first two patches just do some rework on the idle_boot_override and _PDC related stuff to make the ACPI code more arch-independent. The third patch just introduce map_gic_id() for ACPI processor core followed by the ACPI 5.0 spec. These three patches are just ACPI related so I send them out as a separate patch set. I have compiled the kernel successful after appling this patch set on x86, ia64 and powerpc(with cross compile tool). Changes since last RFC version: a) Remove the RFC tag; b) Move idle_boot_override out of the arch directory suggested by Alan; c) Make these 3 patches as a separate patch set since there are not not related to the ARM/ARM64 platform. Hanjun Guo (3): ACPI / idle: Move idle_boot_override out of the arch directory ACPI / processor_core: Rework _PDC related stuff to make it more arch-independent ACPI: Introduce map_gic_id() to get apic id from MADT or _MAT method arch/ia64/include/asm/acpi.h | 5 +--- arch/ia64/include/asm/processor.h | 3 --- arch/ia64/kernel/acpi.c | 17 +++++++++++++ arch/powerpc/include/asm/processor.h | 1 - arch/x86/include/asm/acpi.h | 19 +-------------- arch/x86/include/asm/processor.h | 3 --- arch/x86/kernel/acpi/cstate.c | 31 ++++++++++++++++++++++++ arch/x86/kernel/process.c | 1 + drivers/acpi/processor_core.c | 47 +++++++++++++++++++++--------------- include/linux/cpu.h | 8 ++++++ 10 files changed, 87 insertions(+), 48 deletions(-) -- 1.8.2.2

11 years, 4 months

3
10
0 0

[RFC part2 PATCH 0/9] Using ACPI MADT table to initialise SMP and GIC

by Hanjun Guo

This patch set is based on part1 "Make ACPI core running on ARM64" patch set. After we can get the ACPI tables from UEFI, we can use these tables to initialise the system now. GIC (means GIC cpu interface) structure and GIC distributor structure in MADT table contains the information of GIC cpu interface base address and GIC distributor base address, which can be used to initialise GIC. Further more, parked address in GIC structure can be used as cpu release address for spin table SMP initialisation. This patch set use these information to init SMP and GIC. Please refer to chapter 5.2.12.14/15 of ACPI 5.0 spec for GIC and GIC distributor structure information. Amit Daniel Kachhap (1): irqdomain: Add a new API irq_create_acpi_mapping() Hanjun Guo (8): ARM64 / ACPI: Implement core functions for parsing MADT table ARM64 / ACPI: Prefill cpu possible/present maps and map logical cpu id to APIC id ARM64 / ACPI: Introduce map_gic_id() to get apic id from MADT or _MAT method ARM64 / ACPI: Use Parked Address in GIC structure for spin table SMP initialisation ACPI: Define ACPI_IRQ_MODEL_GIC needed for arm Irqchip / gic: Set as default domain so we can access from ACPI ACPI / ARM64: Update acpi_register_gsi to register with the core IRQ subsystem ACPI / GIC: Initialize GIC using the information in MADT arch/arm64/include/asm/acpi.h | 16 +- arch/arm64/kernel/irq.c | 5 + arch/arm64/kernel/setup.c | 2 + arch/arm64/kernel/smp.c | 2 + arch/arm64/kernel/smp_spin_table.c | 16 +- drivers/acpi/bus.c | 3 + drivers/acpi/plat/arm-core.c | 397 +++++++++++++++++++++++++++++++++++- drivers/acpi/processor_core.c | 26 +++ drivers/acpi/tables.c | 21 ++ drivers/irqchip/irq-gic.c | 7 + include/linux/acpi.h | 9 + kernel/irq/irqdomain.c | 27 +++ 12 files changed, 521 insertions(+), 10 deletions(-) -- 1.7.9.5

11 years, 4 months

3
16
0 0

queue boot: 12 pass, 5 fail (v3.10.27-1-gcc30b1d)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: queue Git describe: v3.10.27-1-gcc30b1d Failed boot tests (console logs at the end) =========================================== am335x-bone: FAIL: omap2plus_defconfig armada-xp-openblocks-ax3-4: FAIL: multi_v7_defconfig armada-370-mirabox: FAIL: multi_v7_defconfig sun4i-a10-cubieboard: FAIL: multi_v7_defconfig sama5d35ek: FAIL: sama5_defconfig Full Report =========== omap2plus_defconfig ------------------- omap3-beagle-xm PASS: 0 min 55.5 sec am335x-bone FAIL: 0 min 31.4 sec omap3-tobi,3530overo PASS: 0 min 33.7 sec omap4-panda PASS: 1 min 3.8 sec omap4-panda-es PASS: 1 min 7.2 sec omap3-tobi,3730storm PASS: 0 min 35.9 sec omap3-beagle PASS: 0 min 51.5 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.8 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.6 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.3 sec armada-370-mirabox PASS: 0 min 19.6 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.4 sec multi_v7_defconfig ------------------ armada-xp-openblocks-ax3-4 FAIL: 0 min 20.0 sec armada-370-mirabox FAIL: 0 min 17.9 sec sun4i-a10-cubieboard FAIL: 1 min 8.5 sec sama5_defconfig --------------- sama5d35ek FAIL: 0 min 31.4 sec Console logs for failures ========================= omap2plus_defconfig ------------------- am335x-bone: FAIL: last 24 lines of boot log: --------------------------------------------- cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use cu: /home/khilman/dev/am335xbone: Line in use Unknown command '~`f~~~~ff~`f~~~~ff~`f~~~~ff~xp~~xp~' - try 'help' U-Boot# ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 31.36 seconds. # PYBOOT: Result: FAIL multi_v7_defconfig ------------------ armada-xp-openblocks-ax3-4: FAIL: last 24 lines of boot log: ------------------------------------------------------------ [<c0013bec>] (unwind_backtrace+0x0/0xf4) from [<c00114b0>] (show_stack+0x10/0x14) [<c00114b0>] (show_stack+0x10/0x14) from [<c0275d20>] (panic+0xa0/0x1e8) [<c0275d20>] (panic+0xa0/0x1e8) from [<c0329110>] (mount_block_root+0x294/0x298) [<c0329110>] (mount_block_root+0x294/0x298) from [<c03292c4>] (prepare_namespace+0x14c/0x184) [<c03292c4>] (prepare_namespace+0x14c/0x184) from [<c0328d60>] (kernel_init_freeable+0x1c8/0x1d8) [<c0328d60>] (kernel_init_freeable+0x1c8/0x1d8) from [<c0271a90>] (kernel_init+0x8/0x158) [<c0271a90>] (kernel_init+0x8/0x158) from [<c000df18>] (ret_from_fork+0x14/0x3c) CPU0: stopping CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.27-00001-gcc30b1d #1 [<c0013bec>] (unwind_backtrace+0x0/0xf4) from [<c00114b0>] (show_stack+0x10/0x14) [<c00114b0>] (show_stack+0x10/0x14) from [<c001236c>] (handle_IPI+0x108/0x130) [<c001236c>] (handle_IPI+0x108/0x130) from [<c000851c>] (armada_370_xp_handle_irq+0x90/0xa8) [<c000851c>] (armada_370_xp_handle_irq+0x90/0xa8) from [<c000dac0>] (__irq_svc+0x40/0x50) Exception stack(0xc0359f70 to 0xc0359fb8) 9f60: c1d5b6d8 00000000 000000be 000000be 9f80: c03604a8 c0358000 c036045c c0383b6c c027dec0 c0358000 c0383b6c c0358000 9fa0: 0000001f c0359fb8 c000f070 c004f970 60000113 ffffffff [<c000dac0>] (__irq_svc+0x40/0x50) from [<c004f970>] (cpu_startup_entry+0xfc/0x140) [<c004f970>] (cpu_startup_entry+0xfc/0x140) from [<c0328a3c>] (start_kernel+0x2c4/0x2d0) [<c0328a3c>] (start_kernel+0x2c4/0x2d0) from [<00008074>] (0x8074) ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: Kernel panic # PYBOOT: Time: 19.96 seconds. # PYBOOT: Result: FAIL armada-370-mirabox: FAIL: last 24 lines of boot log: ---------------------------------------------------- mousedev: PS/2 mouse device common for all mice sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper usbcore: registered new interface driver usbhid usbhid: USB HID core driver VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 Registering SWP/SWPB emulation handler /home/build/work/batch/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) List of all partitions: No filesystem could mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.27-00001-gcc30b1d #1 [<c0013bec>] (unwind_backtrace+0x0/0xf4) from [<c00114b0>] (show_stack+0x10/0x14) [<c00114b0>] (show_stack+0x10/0x14) from [<c0275d20>] (panic+0xa0/0x1e8) [<c0275d20>] (panic+0xa0/0x1e8) from [<c0329110>] (mount_block_root+0x294/0x298) [<c0329110>] (mount_block_root+0x294/0x298) from [<c03292c4>] (prepare_namespace+0x14c/0x184) [<c03292c4>] (prepare_namespace+0x14c/0x184) from [<c0328d60>] (kernel_init_freeable+0x1c8/0x1d8) [<c0328d60>] (kernel_init_freeable+0x1c8/0x1d8) from [<c0271a90>] (kernel_init+0x8/0x158) [<c0271a90>] (kernel_init+0x8/0x158) from [<c000df18>] (ret_from_fork+0x14/0x3c) ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: Kernel panic # PYBOOT: Time: 17.89 seconds. # PYBOOT: Result: FAIL sun4i-a10-cubieboard: FAIL: last 24 lines of boot log: ------------------------------------------------------ ipmi_si: Trying default-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0 ipmi_si: Could not set up I/O space Trying to free nonexistent resource <00000000000000e4-00000000000000e4> Trying to free nonexistent resource <00000000000000e5-00000000000000e5> Trying to free nonexistent resource <00000000000000e6-00000000000000e6> ipmi_si: Unable to find any System Interface(s) Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 17) is a U6_16550A console [ttyS0] enabled usbcore: registered new interface driver usb-storage mousedev: PS/2 mouse device common for all mice sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper usbcore: registered new interface driver usbhid usbhid: USB HID core driver VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 Registering SWP/SWPB emulation handler /home/build/work/batch/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Waiting for root device /dev/mmcblk0p2... ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 68.48 seconds. # PYBOOT: Result: FAIL sama5_defconfig --------------- sama5d35ek: FAIL: last 24 lines of boot log: -------------------------------------------- cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use cu: /home/khilman/dev/sama5: Line in use ~$off # PYBOOT: Exception: ERROR: Could not break into autoboot. # PYBOOT: Time: 31.45 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

2
1
0 0

[PATCH] audit: Modify a set of system calls in audit class definitions

by AKASHI Takahiro

Each asm-generic/audit_xx.h defines a set of system calls for respective audit permssion class (read, write, change attribute or exec). This patch changes two entries: 1) fchown in audit_change_attr.h Make fchown included by its own because in asm-generic/unistd.h, for example, fchown always exists while chown is optional. This change is necessary at least for arm64. 2) truncate64 in audit_write.h Add missing truncate64/ftruncate64 as well as truncate/ftruncate Signed-off-by: AKASHI Takahiro <takahiro.akashi(a)linaro.org> --- include/asm-generic/audit_change_attr.h | 4 +++- include/asm-generic/audit_write.h | 6 ++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/include/asm-generic/audit_change_attr.h b/include/asm-generic/audit_change_attr.h index 89b73e5..a186553 100644 --- a/include/asm-generic/audit_change_attr.h +++ b/include/asm-generic/audit_change_attr.h @@ -4,9 +4,11 @@ __NR_chmod, __NR_fchmod, #ifdef __NR_chown __NR_chown, -__NR_fchown, __NR_lchown, #endif +#ifdef __NR_fchown +__NR_fchown, +#endif __NR_setxattr, __NR_lsetxattr, __NR_fsetxattr, diff --git a/include/asm-generic/audit_write.h b/include/asm-generic/audit_write.h index e7020c5..274575d 100644 --- a/include/asm-generic/audit_write.h +++ b/include/asm-generic/audit_write.h @@ -10,6 +10,12 @@ __NR_truncate, #ifdef __NR_truncate64 __NR_truncate64, #endif +#ifdef __NR_ftruncate +__NR_ftruncate, +#endif +#ifdef __NR_ftruncate64 +__NR_ftruncate64, +#endif #ifdef __NR_bind __NR_bind, /* bind can affect fs object only in one way... */ #endif -- 1.7.9.5

11 years, 4 months

3
2
0 0

[PATCH v3] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enable this ACPI mode

by al.stone＠linaro.org

From: Al Stone <al.stone(a)linaro.org> ACPI hardware reduced mode exists to allow newer platforms to use a simpler form of ACPI that does not require supporting legacy versions of the specification and their associated hardware. This mode was introduced in the ACPI 5.0 specification. To enable the hardware reduced mode of ACPI, we need to set the flag ACPI_REDUCED_HARDWARE to TRUE in the ACPICA source. In order to do that, we introduce a kernel configuration item to enable or disable ACPI_REDUCED_HARDWARE. We can then change the kernel configuration instead of having to modify the kernel source. Introducing this configuration item is based on suggestions from Lv Zheng saying that this does not belong in ACPICA, but rather to the Linux kernel itself. Hence, we introduce this configuration item so that we can make ACPI_REDUCED_HARDWARE configurable. For the details of the discussion, please refer to: http://www.spinics.net/lists/linux-acpi/msg46369.html Changes for v3: -- Minimize the changelog. Changes for v2: -- Changed test for EXPERT to avoid reported Kconfig warning Signed-off-by: Hanjun Guo <hanjun.guo(a)linaro.org> Signed-off-by: Al Stone <al.stone(a)linaro.org> --- drivers/acpi/Kconfig | 13 +++++++++++++ include/acpi/platform/aclinux.h | 6 ++++++ 2 files changed, 19 insertions(+) diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 4770de5..9fd6a7a 100644 --- a/drivers/acpi/Kconfig +++ b/drivers/acpi/Kconfig @@ -343,6 +343,19 @@ config ACPI_BGRT data from the firmware boot splash. It will appear under /sys/firmware/acpi/bgrt/ . +config ACPI_REDUCED_HARDWARE_ONLY + bool "Hardware-reduced ACPI support only" if EXPERT + def_bool n + depends on ACPI + help + This config item changes the way the ACPI code is built. When this + option is selected, the kernel will use a specialized version of + ACPICA that ONLY supports the ACPI "reduced hardware" mode. The + resulting kernel will be smaller but it will also be restricted to + running in ACPI reduced hardware mode ONLY. + + If you are unsure what to do, do not enable this option. + source "drivers/acpi/apei/Kconfig" config ACPI_EXTLOG diff --git a/include/acpi/platform/aclinux.h b/include/acpi/platform/aclinux.h index 28f4f4d..7d71f08 100644 --- a/include/acpi/platform/aclinux.h +++ b/include/acpi/platform/aclinux.h @@ -52,6 +52,12 @@ #ifdef __KERNEL__ +/* Compile for reduced hardware mode only with this kernel config */ + +#ifdef CONFIG_ACPI_REDUCED_HARDWARE_ONLY +#define ACPI_REDUCED_HARDWARE 1 +#endif + #include <linux/string.h> #include <linux/kernel.h> #include <linux/ctype.h> -- 1.8.4.2

11 years, 4 months

1
0
0 0

mainline boot: 33 pass, 0 fail (v3.13-rc8-49-g8b6d79f)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-rc8-49-g8b6d79f Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.9 sec omap3-beagle-xm PASS: 0 min 58.7 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 5.0 sec omap4-panda-es PASS: 1 min 7.6 sec omap3-tobi,3730storm PASS: 0 min 20.6 sec omap3-tobi,3530overo PASS: 0 min 21.7 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 PASS: 0 min 13.0 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.0 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.4 sec imx6q-wandboard PASS: 0 min 16.6 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.9 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.0 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 29.2 sec tegra30-beaver PASS: 0 min 16.7 sec am335x-boneblack PASS: 0 min 21.8 sec omap3-beagle-xm PASS: 0 min 58.0 sec sun7i-a20-cubieboard2 PASS: 0 min 13.1 sec armada-370-mirabox PASS: 0 min 20.6 sec omap4-panda PASS: 1 min 2.7 sec omap4-panda-es PASS: 1 min 1.0 sec armada-xp-openblocks-ax3-4 PASS: 0 min 23.0 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec am335x-bone PASS: 0 min 23.5 sec imx6q-wandboard PASS: 0 min 15.8 sec omap3-tobi,3730storm PASS: 0 min 22.8 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.9 sec omap3-tobi,3530overo PASS: 0 min 20.3 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 31.3 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.5 sec

11 years, 4 months

1
0
0 0

arm-soc boot: 32 pass, 1 fail (v3.13-rc5-1178-gf342684)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.13-rc5-1178-gf342684 Failed boot tests (console logs at the end) =========================================== omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.9 sec omap3-beagle-xm PASS: 0 min 59.6 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 4.5 sec omap4-panda-es PASS: 1 min 10.0 sec omap3-tobi,3730storm PASS: 0 min 20.6 sec omap3-tobi,3530overo PASS: 0 min 21.8 sec multi_lpae_defconfig -------------------- sun7i-a20-cubieboard2 PASS: 0 min 14.4 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 18.2 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.5 sec imx6q-wandboard PASS: 0 min 15.7 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.2 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.0 sec armada-370-mirabox PASS: 0 min 20.3 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 28.2 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 17.4 sec tegra30-beaver PASS: 0 min 19.9 sec am335x-boneblack PASS: 0 min 22.7 sec omap3-beagle-xm PASS: 0 min 50.9 sec sun7i-a20-cubieboard2 PASS: 0 min 13.5 sec armada-370-mirabox PASS: 0 min 21.4 sec omap4-panda PASS: 0 min 52.7 sec omap4-panda-es FAIL: 1 min 45.5 sec armada-xp-openblocks-ax3-4 PASS: 0 min 23.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.2 sec am335x-bone PASS: 0 min 24.3 sec imx6q-wandboard PASS: 0 min 16.6 sec omap3-tobi,3730storm PASS: 0 min 23.0 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.6 sec omap3-tobi,3530overo PASS: 0 min 23.6 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 28.5 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.3 sec Console logs for failures ========================= multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 1.612487] Power Management for TI OMAP4. [ 1.616790] OMAP4 PM: u-boot >= v2012.07 is required for full PM support [ 1.623901] Registering SWP/SWPB emulation handler [ 1.630035] vwl1271: 1800 mV [ 1.636962] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 1.646118] twl 0-0048: PIH (irq 39) nested IRQs [ 1.652465] twl_rtc rtc.11: Enabling TWL-RTC [ 1.659332] twl_rtc rtc.11: rtc core: registered rtc.11 as rtc0 [ 1.666168] VAUX1_6030: 1000 <--> 3000 mV at 2800 mV [ 1.672149] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV [ 1.678131] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV [ 1.684143] VMMC: 1200 <--> 3000 mV at 3000 mV [ 1.689666] VPP: 1800 <--> 2500 mV at 1900 mV [ 1.695007] VUSIM: 1200 <--> 2900 mV at 1800 mV [ 1.700378] VDAC: 1800 mV [ 1.703552] VANA: 2100 mV [ 1.707031] VCXIO: 1800 mV [ 1.707061] VUSB: 3300 mV [ 1.713806] V1V8: 1800 mV [ 1.717254] V2V1: 2100 mV ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 105.47 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

next boot: 27 pass, 2 fail (next-20140117)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: next Git describe: next-20140117 Failed boot tests (console logs at the end) =========================================== exynos5250-arndale: FAIL: exynos_defconfig omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.2 sec omap3-beagle-xm PASS: 0 min 56.0 sec am335x-bone PASS: 0 min 26.8 sec omap4-panda PASS: 1 min 3.9 sec omap4-panda-es PASS: 1 min 6.6 sec omap3-tobi,3730storm PASS: 0 min 21.0 sec omap3-tobi,3530overo PASS: 0 min 22.2 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.2 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.0 sec imx6q-wandboard PASS: 0 min 15.7 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.3 sec exynos_defconfig ---------------- exynos5250-arndale FAIL: 1 min 30.0 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 16.9 sec tegra30-beaver PASS: 0 min 23.5 sec am335x-boneblack PASS: 0 min 22.8 sec omap3-beagle-xm PASS: 0 min 49.4 sec sun7i-a20-cubieboard2 PASS: 0 min 13.7 sec armada-370-mirabox PASS: 0 min 21.4 sec omap4-panda PASS: 0 min 54.8 sec omap4-panda-es FAIL: 1 min 44.7 sec armada-xp-openblocks-ax3-4 PASS: 0 min 24.0 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.2 sec am335x-bone PASS: 0 min 25.4 sec imx6q-wandboard PASS: 0 min 16.8 sec omap3-tobi,3730storm PASS: 0 min 23.3 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.5 sec omap3-tobi,3530overo PASS: 0 min 20.7 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 33.1 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.6 sec Console logs for failures ========================= exynos_defconfig ---------------- exynos5250-arndale: FAIL: last 24 lines of boot log: ---------------------------------------------------- [ 1.860071] VDD_33ON_2.8V: disabling [ 1.871051] exynos-dp 145b0000.dp-controller: unable to find phy [ 1.876948] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 1.877251] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1) [ 1.877336] mmc0: new high speed DDR MMC card at address 0001 [ 1.900558] isa bounce pool size: 16 pages [ 1.904414] mmcblk0: mmc0:0001 M4G1FA 3.72 GiB [ 1.909014] mmcblk0boot0: mmc0:0001 M4G1FA partition 1 1.00 MiB [ 1.914918] mmcblk0boot1: mmc0:0001 M4G1FA partition 2 1.00 MiB [ 1.920815] mmcblk0rpmb: mmc0:0001 M4G1FA partition 3 128 KiB [ 1.927522] mmcblk0: p1 p2 p3 p4 [ 1.931943] mmcblk0boot1: unknown partition table [ 1.936185] mmcblk0boot0: unknown partition table [ 2.101026] exynos-dp 145b0000.dp-controller: unable to find phy [ 2.105596] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 2.114333] input: gpio_keys.4 as /devices/gpio_keys.4/input/input0 [ 2.120005] exynos-dp 145b0000.dp-controller: unable to find phy [ 2.125624] s3c-rtc 101e0000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 2.125673] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 2.142965] Waiting for root device /dev/mmcblk1p3... ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 89.99 seconds. # PYBOOT: Result: FAIL multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 1.651611] OMAP4 PM: u-boot >= v2012.07 is required for full PM support [ 1.658721] Registering SWP/SWPB emulation handler [ 1.664733] vwl1271: 1800 mV [ 1.671264] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 1.681060] twl 0-0048: PIH (irq 39) nested IRQs [ 1.687286] twl_rtc rtc.11: Enabling TWL-RTC [ 1.694091] twl_rtc rtc.11: rtc core: registered rtc.11 as rtc0 [ 1.700988] VAUX1_6030: 1000 <--> 3000 mV at 2800 mV [ 1.707000] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV [ 1.712982] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV [ 1.718963] VMMC: 1200 <--> 3000 mV at 3000 mV [ 1.724426] VPP: 1800 <--> 2500 mV at 1900 mV [ 1.729736] VUSIM: 1200 <--> 2900 mV at 1800 mV [ 1.734771] VDAC: 1800 mV [ 1.734771] VANA: 2100 mV [ 1.741851] VCXIO: 1800 mV [ 1.741851] VUSB: 3300 mV [ 1.748596] V1V8: 1800 mV [ 1.752105] V2V1: 2100 mV [ 1.759094] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 104.66 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

next boot: 32 pass, 2 fail (next-20140116)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: next Git describe: next-20140116 Failed boot tests (console logs at the end) =========================================== exynos5250-arndale: FAIL: exynos_defconfig omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.2 sec omap3-beagle-xm PASS: 0 min 58.2 sec am335x-bone PASS: 0 min 26.8 sec omap4-panda PASS: 1 min 5.8 sec omap4-panda-es PASS: 1 min 4.9 sec omap3-tobi,3730storm PASS: 0 min 23.8 sec omap3-tobi,3530overo PASS: 0 min 25.3 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.1 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.0 sec imx6q-wandboard PASS: 0 min 15.7 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.3 sec bcm_defconfig ------------- bcm28155-ap PASS: 1 min 14.6 sec exynos_defconfig ---------------- exynos5250-arndale FAIL: 1 min 25.2 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 20.1 sec tegra30-beaver PASS: 0 min 21.1 sec am335x-boneblack PASS: 0 min 22.8 sec omap3-beagle-xm PASS: 0 min 50.4 sec sun7i-a20-cubieboard2 PASS: 0 min 13.7 sec armada-370-mirabox PASS: 0 min 21.5 sec omap4-panda PASS: 0 min 51.0 sec omap4-panda-es FAIL: 1 min 45.1 sec armada-xp-openblocks-ax3-4 PASS: 0 min 23.7 sec bcm28155-ap PASS: 1 min 9.1 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.2 sec am335x-bone PASS: 0 min 25.4 sec imx6q-wandboard PASS: 0 min 16.7 sec omap3-tobi,3730storm PASS: 0 min 23.1 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.6 sec omap3-tobi,3530overo PASS: 0 min 20.8 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 33.0 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.6 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.9 sec armada-370-mirabox PASS: 0 min 20.2 sec Console logs for failures ========================= exynos_defconfig ---------------- exynos5250-arndale: FAIL: last 24 lines of boot log: ---------------------------------------------------- [ 1.870085] VDD_33ON_2.8V: disabling [ 1.881063] exynos-dp 145b0000.dp-controller: unable to find phy [ 1.886960] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 1.887265] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1) [ 1.887351] mmc0: new high speed DDR MMC card at address 0001 [ 1.910581] isa bounce pool size: 16 pages [ 1.914429] mmcblk0: mmc0:0001 M4G1FA 3.72 GiB [ 1.919026] mmcblk0boot0: mmc0:0001 M4G1FA partition 1 1.00 MiB [ 1.924932] mmcblk0boot1: mmc0:0001 M4G1FA partition 2 1.00 MiB [ 1.930827] mmcblk0rpmb: mmc0:0001 M4G1FA partition 3 128 KiB [ 1.937537] mmcblk0: p1 p2 p3 p4 [ 1.942002] mmcblk0boot1: unknown partition table [ 1.946261] mmcblk0boot0: unknown partition table [ 2.111039] exynos-dp 145b0000.dp-controller: unable to find phy [ 2.115608] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 2.124339] input: gpio_keys.4 as /devices/gpio_keys.4/input/input0 [ 2.130055] exynos-dp 145b0000.dp-controller: unable to find phy [ 2.135687] s3c-rtc 101e0000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 2.144169] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 2.153030] Waiting for root device /dev/mmcblk1p3... ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 85.16 seconds. # PYBOOT: Result: FAIL multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ scanning usb for ethernet devices... 1 Ethernet Device(s) found Waiting for Ethernet connection... done. BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.1.163 Using sms0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.163 Filename 'omap2/zImage'. Load address: 0x82000000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ##################### 2.2 MiB/s done Bytes transferred = 4112320 (3ebfc0 hex) Wrong Image Format for bootm command ERROR: can't get kernel image! ** File not found /boot/omap2/zImage ** Panda # ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 105.08 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

[PATCH] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode

by al.stone＠linaro.org

From: Al Stone <al.stone(a)linaro.org> Hardware reduced mode, despite the name, exists primarily to allow newer platforms to use a much simpler form of ACPI that does not require supporting the legacy of previous versions of the specification. This mode was first introduced in the ACPI 5.0 specification, but because it is so much simpler and reduces the size of the object code needed to support ACPI, it is likely to be used more often in the near future. To enable the hardware reduced mode of ACPI on some platforms (such as ARM), we need to modify the kernel code and set ACPI_REDUCED_HARDWARE to TRUE in the ACPICA source. For ARM/ARM64, hardware reduced ACPI should be the only mode used; legacy mode would require modifications to SoCs in order to provide several x86-specific hardware features (e.g., an NMI and SMI support). We set ACPI_REDUCED_HARDWARE to TRUE in the ACPICA source by introducing a kernel config item to enable/disable ACPI_REDUCED_HARDWARE. We can then change the kernel config instead of having to modify the kernel source directly to enable the reduced hardware mode of ACPI. Lv Zheng suggested that this configuration item does not belong in ACPICA, the upstream source for much of the ACPI internals, but rather to the Linux kernel itself. Hence, we introduce this flag so that we can make ACPI_REDUCED_HARDWARE configurable. For the details of the discussion, please refer to: http://www.spinics.net/lists/linux-acpi/msg46369.html Even though support for X86 in hardware reduced mode is possible, it is NOT enabled. Extensive effort has gone into the Linux kernel so that there is a single kernel image than can run on all x86 hardware; the kernel changes run-time behavior to adapt to the hardware being used. This is not currently possible with the existing ACPICA infrastructure but only presents a problem on achitectures supporting both hardware-reduced and legacy modes of ACPI -- i.e., on x86 only. The problem with the current ACPICA code base is that if one builds legacy ACPI (a proper superset of hardware-reduced), the kernel can run in hardware- reduced with the proper ACPI tables, but there is still ACPICA code that could be executed even though it is not allowed by the specification. If one builds a hardware-reduced only ACPI, the kernel cannot run with ACPI tables that are for legacy mode. To ensure compliance with ACPI, one must therefore build two separate kernels. Once this problem has been properly fixed, we can then enable x86 hardware-reduced mode and use a single kernel. This patch used to be part of a set to implement stricter conformance with hardware reduced ACPI. The code changes from that set are being re-thought in order to handle some non-compliant hardware, but this patch did not depend on those changes. In the meantime, this patch is needed in order to enable ACPI core functionality for ARMv8 servers and hence is being submitted separately in order to aid that effort. Signed-off-by: Hanjun Guo <hanjun.guo(a)linaro.org> Signed-off-by: Al Stone <al.stone(a)linaro.org> --- drivers/acpi/Kconfig | 13 +++++++++++++ include/acpi/platform/aclinux.h | 6 ++++++ 2 files changed, 19 insertions(+) diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 4770de5..961ea9e 100644 --- a/drivers/acpi/Kconfig +++ b/drivers/acpi/Kconfig @@ -343,6 +343,19 @@ config ACPI_BGRT data from the firmware boot splash. It will appear under /sys/firmware/acpi/bgrt/ . +config ACPI_REDUCED_HARDWARE_ONLY + bool "Hardware-reduced ACPI support only" + def_bool n + depends on ACPI && EXPERT + help + This config item changes the way the ACPI code is built. When this + option is selected, the kernel will use a specialized version of + ACPICA that ONLY supports the ACPI "reduced hardware" mode. The + resulting kernel will be smaller but it will also be restricted to + running in ACPI reduced hardware mode ONLY. + + If you are unsure what to do, do not enable this option. + source "drivers/acpi/apei/Kconfig" config ACPI_EXTLOG diff --git a/include/acpi/platform/aclinux.h b/include/acpi/platform/aclinux.h index 28f4f4d..7d71f08 100644 --- a/include/acpi/platform/aclinux.h +++ b/include/acpi/platform/aclinux.h @@ -52,6 +52,12 @@ #ifdef __KERNEL__ +/* Compile for reduced hardware mode only with this kernel config */ + +#ifdef CONFIG_ACPI_REDUCED_HARDWARE_ONLY +#define ACPI_REDUCED_HARDWARE 1 +#endif + #include <linux/string.h> #include <linux/kernel.h> #include <linux/ctype.h> -- 1.8.4.2

11 years, 4 months

3
5
0 0

[PATCH] ACPI / processor: Return specific error value when mapping lapic id

by Hanjun Guo

we usually return 0 for success in int returned function, and negative value when failed, but in processor_core.c, some function return 1 for success and 0 for failure which leads confusion sometimes, replace with specific error values to fix that. Signed-off-by: Hanjun Guo <hanjun.guo(a)linaro.org> --- drivers/acpi/processor_core.c | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c index b3171f3..24c87ef 100644 --- a/drivers/acpi/processor_core.c +++ b/drivers/acpi/processor_core.c @@ -45,13 +45,13 @@ static int map_lapic_id(struct acpi_subtable_header *entry, (struct acpi_madt_local_apic *)entry; if (!(lapic->lapic_flags & ACPI_MADT_ENABLED)) - return 0; + return -ENODEV; if (lapic->processor_id != acpi_id) - return 0; + return -EINVAL; *apic_id = lapic->id; - return 1; + return 0; } static int map_x2apic_id(struct acpi_subtable_header *entry, @@ -61,14 +61,14 @@ static int map_x2apic_id(struct acpi_subtable_header *entry, (struct acpi_madt_local_x2apic *)entry; if (!(apic->lapic_flags & ACPI_MADT_ENABLED)) - return 0; + return -ENODEV; if (device_declaration && (apic->uid == acpi_id)) { *apic_id = apic->local_apic_id; - return 1; + return 0; } - return 0; + return -EINVAL; } static int map_lsapic_id(struct acpi_subtable_header *entry, @@ -78,16 +78,16 @@ static int map_lsapic_id(struct acpi_subtable_header *entry, (struct acpi_madt_local_sapic *)entry; if (!(lsapic->lapic_flags & ACPI_MADT_ENABLED)) - return 0; + return -ENODEV; if (device_declaration) { if ((entry->length < 16) || (lsapic->uid != acpi_id)) - return 0; + return -EINVAL; } else if (lsapic->processor_id != acpi_id) - return 0; + return -EINVAL; *apic_id = (lsapic->id << 8) | lsapic->eid; - return 1; + return 0; } static int map_madt_entry(int type, u32 acpi_id) @@ -117,13 +117,13 @@ static int map_madt_entry(int type, u32 acpi_id) struct acpi_subtable_header *header = (struct acpi_subtable_header *)entry; if (header->type == ACPI_MADT_TYPE_LOCAL_APIC) { - if (map_lapic_id(header, acpi_id, &apic_id)) + if (!map_lapic_id(header, acpi_id, &apic_id)) break; } else if (header->type == ACPI_MADT_TYPE_LOCAL_X2APIC) { - if (map_x2apic_id(header, type, acpi_id, &apic_id)) + if (!map_x2apic_id(header, type, acpi_id, &apic_id)) break; } else if (header->type == ACPI_MADT_TYPE_LOCAL_SAPIC) { - if (map_lsapic_id(header, type, acpi_id, &apic_id)) + if (!map_lsapic_id(header, type, acpi_id, &apic_id)) break; } entry += header->length; -- 1.7.9.5

11 years, 4 months

1
0
0 0

[RFC PATCH] sched: find the latest idle cpu

by Alex Shi

Currently we just try to find least load cpu. If some cpus idled, we just pick the first cpu in cpu mask. In fact we can get the interrupted idle cpu or the latest idled cpu, then we may get the benefit from both latency and power. The selected cpu maybe not the best, since other cpu may be interrupted during our selecting. But be captious costs too much. Signed-off-by: Alex Shi <alex.shi(a)linaro.org> --- kernel/sched/fair.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index c7395d9..fb52d26 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -4167,6 +4167,26 @@ find_idlest_cpu(struct sched_group *group, struct task_struct *p, int this_cpu) min_load = load; idlest = i; } +#ifdef CONFIG_NO_HZ_COMMON + /* + * Coarsely to get the latest idle cpu for shorter latency and + * possible power benefit. + */ + if (!min_load) { + struct tick_sched *ts = &per_cpu(tick_cpu_sched, i); + + s64 latest_wake = 0; + /* idle cpu doing irq */ + if (ts->inidle && !ts->idle_active) + idlest = i; + /* the cpu resched */ + else if (!ts->inidle) + idlest = i; + /* find latest idle cpu */ + else if (ktime_to_us(ts->idle_entrytime) > latest_wake) + idlest = i; + } +#endif } return idlest; -- 1.8.1.2

11 years, 4 months

5
14
0 0

[PATCH v2] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode

by al.stone＠linaro.org

From: Al Stone <al.stone(a)linaro.org> Hardware reduced mode, despite the name, exists primarily to allow newer platforms to use a much simpler form of ACPI that does not require supporting the legacy of previous versions of the specification. This mode was first introduced in the ACPI 5.0 specification, but because it is so much simpler and reduces the size of the object code needed to support ACPI, it is likely to be used more often in the near future. To enable the hardware reduced mode of ACPI on some platforms (such as ARM), we need to modify the kernel code and set ACPI_REDUCED_HARDWARE to TRUE in the ACPICA source. For ARM/ARM64, hardware reduced ACPI should be the only mode used; legacy mode would require modifications to SoCs in order to provide several x86-specific hardware features (e.g., an NMI and SMI support). We set ACPI_REDUCED_HARDWARE to TRUE in the ACPICA source by introducing a kernel config item to enable/disable ACPI_REDUCED_HARDWARE. We can then change the kernel config instead of having to modify the kernel source directly to enable the reduced hardware mode of ACPI. Lv Zheng suggested that this configuration item does not belong in ACPICA, the upstream source for much of the ACPI internals, but rather to the Linux kernel itself. Hence, we introduce this flag so that we can make ACPI_REDUCED_HARDWARE configurable. For the details of the discussion, please refer to: http://www.spinics.net/lists/linux-acpi/msg46369.html Even though support for X86 in hardware reduced mode is possible, it is NOT enabled. Extensive effort has gone into the Linux kernel so that there is a single kernel image than can run on all x86 hardware; the kernel changes run-time behavior to adapt to the hardware being used. This is not currently possible with the existing ACPICA infrastructure but only presents a problem on achitectures supporting both hardware-reduced and legacy modes of ACPI -- i.e., on x86 only. The problem with the current ACPICA code base is that if one builds legacy ACPI (a proper superset of hardware-reduced), the kernel can run in hardware- reduced with the proper ACPI tables, but there is still ACPICA code that could be executed even though it is not allowed by the specification. If one builds a hardware-reduced only ACPI, the kernel cannot run with ACPI tables that are for legacy mode. To ensure compliance with ACPI, one must therefore build two separate kernels. Once this problem has been properly fixed, we can then enable x86 hardware-reduced mode and use a single kernel. Changes for v2: -- Changed test for EXPERT to avoid reported Kconfig warning Signed-off-by: Hanjun Guo <hanjun.guo(a)linaro.org> Signed-off-by: Al Stone <al.stone(a)linaro.org> --- drivers/acpi/Kconfig | 13 +++++++++++++ include/acpi/platform/aclinux.h | 6 ++++++ 2 files changed, 19 insertions(+) diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 4770de5..9fd6a7a 100644 --- a/drivers/acpi/Kconfig +++ b/drivers/acpi/Kconfig @@ -343,6 +343,19 @@ config ACPI_BGRT data from the firmware boot splash. It will appear under /sys/firmware/acpi/bgrt/ . +config ACPI_REDUCED_HARDWARE_ONLY + bool "Hardware-reduced ACPI support only" if EXPERT + def_bool n + depends on ACPI + help + This config item changes the way the ACPI code is built. When this + option is selected, the kernel will use a specialized version of + ACPICA that ONLY supports the ACPI "reduced hardware" mode. The + resulting kernel will be smaller but it will also be restricted to + running in ACPI reduced hardware mode ONLY. + + If you are unsure what to do, do not enable this option. + source "drivers/acpi/apei/Kconfig" config ACPI_EXTLOG diff --git a/include/acpi/platform/aclinux.h b/include/acpi/platform/aclinux.h index 28f4f4d..7d71f08 100644 --- a/include/acpi/platform/aclinux.h +++ b/include/acpi/platform/aclinux.h @@ -52,6 +52,12 @@ #ifdef __KERNEL__ +/* Compile for reduced hardware mode only with this kernel config */ + +#ifdef CONFIG_ACPI_REDUCED_HARDWARE_ONLY +#define ACPI_REDUCED_HARDWARE 1 +#endif + #include <linux/string.h> #include <linux/kernel.h> #include <linux/ctype.h> -- 1.8.4.2

11 years, 4 months

2
1
0 0

[PATCH v4 0/3] perf: add AARCH64 arch support

by Jean Pihet

Add AARCH64 specific support. This includes the following: - AARCH64 perf registers definition and hooks, - compat mode registers use, i.e. profiling a 32-bit binary on a 64-bit system, - unwinding using the dwarf information from the .debug_frame section of the ELF binary; only in 64-bit mode, - unwinding using the frame pointer information; in 64-bit and compat modes. ToDo: - add support for unwinding using the dwarf information in compat mode. This requires some changes to the libunwind code. Tested on ARMv7 and ARMv8 platforms. The compat mode has been tested on ARMv8 using statically built 32-bit binaries. Jean Pihet (3): ARM64: perf: add support for perf registers API ARM64: perf: wire up perf_regs and unwind support ARM64: perf: add support for frame pointer unwinding in compat mode arch/arm64/Kconfig | 2 + arch/arm64/include/asm/ptrace.h | 1 + arch/arm64/include/uapi/asm/Kbuild | 1 + arch/arm64/include/uapi/asm/perf_regs.h | 40 ++++++++++++++ arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/perf_event.c | 75 +++++++++++++++++++++++--- arch/arm64/kernel/perf_regs.c | 44 ++++++++++++++++ tools/perf/arch/arm64/Makefile | 7 +++ tools/perf/arch/arm64/include/perf_regs.h | 88 +++++++++++++++++++++++++++++++ tools/perf/arch/arm64/util/dwarf-regs.c | 80 ++++++++++++++++++++++++++++ tools/perf/arch/arm64/util/unwind.c | 82 ++++++++++++++++++++++++++++ tools/perf/config/Makefile | 8 ++- 12 files changed, 420 insertions(+), 9 deletions(-) create mode 100644 arch/arm64/include/uapi/asm/perf_regs.h create mode 100644 arch/arm64/kernel/perf_regs.c create mode 100644 tools/perf/arch/arm64/Makefile create mode 100644 tools/perf/arch/arm64/include/perf_regs.h create mode 100644 tools/perf/arch/arm64/util/dwarf-regs.c create mode 100644 tools/perf/arch/arm64/util/unwind.c -- 1.7.11.7

11 years, 4 months

2
9
0 0

[PATCH 1/2] spi: Provide core support for DMA mapping transfers

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> The process of DMA mapping buffers for SPI transfers does not vary between devices so in order to save duplication of code in drivers this can be factored out into the core, allowing it to be integrated with the work that is being done on factoring out the common elements from the data path including more sharing of dmaengine code. In order to use this masters need to provide a can_dma() operation and while the hardware is prepared they should ensure that DMA channels are provided in tx_dma and rx_dma. The core will then ensure that the buffers are mapped for DMA prior to calling transfer_one_message(). Currently the cleanup on error is not complete, this needs to be improved. Signed-off-by: Mark Brown <broonie(a)linaro.org> --- drivers/spi/spi.c | 79 +++++++++++++++++++++++++++++++++++++++++++++++++ include/linux/spi/spi.h | 18 +++++++++++ 2 files changed, 97 insertions(+) diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c index a86569e1f178..314d326bce9f 100644 --- a/drivers/spi/spi.c +++ b/drivers/spi/spi.c @@ -24,6 +24,8 @@ #include <linux/device.h> #include <linux/init.h> #include <linux/cache.h> +#include <linux/dma-mapping.h> +#include <linux/dmaengine.h> #include <linux/mutex.h> #include <linux/of_device.h> #include <linux/of_irq.h> @@ -570,6 +572,74 @@ static void spi_set_cs(struct spi_device *spi, bool enable) spi->master->set_cs(spi, !enable); } +static int spi_dma_map_msg(struct spi_master *master, struct spi_message *msg) +{ + struct device *dev = master->dev.parent; + struct device *tx_dev, *rx_dev; + struct spi_transfer *xfer; + + if (msg->is_dma_mapped || !master->can_dma) + return 0; + + tx_dev = &master->dma_tx->dev->device; + rx_dev = &master->dma_rx->dev->device; + + list_for_each_entry(xfer, &msg->transfers, transfer_list) { + if (!master->can_dma(master, msg->spi, xfer)) + continue; + + if (xfer->tx_buf != NULL) { + xfer->tx_dma = dma_map_single(tx_dev, + (void *)xfer->tx_buf, + xfer->len, + DMA_TO_DEVICE); + if (dma_mapping_error(dev, xfer->tx_dma)) { + dev_err(dev, "dma_map_single Tx failed\n"); + return -ENOMEM; + } + } + + if (xfer->rx_buf != NULL) { + xfer->rx_dma = dma_map_single(rx_dev, + xfer->rx_buf, xfer->len, + DMA_FROM_DEVICE); + if (dma_mapping_error(dev, xfer->rx_dma)) { + dev_err(dev, "dma_map_single Rx failed\n"); + dma_unmap_single(tx_dev, xfer->tx_dma, + xfer->len, DMA_TO_DEVICE); + return -ENOMEM; + } + } + } + + return 0; +} + +static int spi_dma_unmap_msg(struct spi_master *master, + struct spi_message *msg) +{ + struct spi_transfer *xfer; + struct device *tx_dev, *rx_dev; + + if (!master->cur_msg_mapped || msg->is_dma_mapped || !master->can_dma) + return 0; + + tx_dev = &master->dma_tx->dev->device; + rx_dev = &master->dma_rx->dev->device; + + list_for_each_entry(xfer, &msg->transfers, transfer_list) { + if (!master->can_dma(master, msg->spi, xfer)) + continue; + + dma_unmap_single(rx_dev, xfer->rx_dma, xfer->len, + DMA_FROM_DEVICE); + dma_unmap_single(tx_dev, xfer->tx_dma, xfer->len, + DMA_TO_DEVICE); + } + + return 0; +} + /* * spi_transfer_one_message - Default implementation of transfer_one_message() * @@ -740,6 +810,13 @@ static void spi_pump_messages(struct kthread_work *work) master->cur_msg_prepared = true; } + ret = spi_dma_map_msg(master, master->cur_msg); + if (ret) { + master->cur_msg->status = ret; + spi_finalize_current_message(master); + return; + } + ret = master->transfer_one_message(master, master->cur_msg); if (ret) { dev_err(&master->dev, @@ -829,6 +906,8 @@ void spi_finalize_current_message(struct spi_master *master) queue_kthread_work(&master->kworker, &master->pump_messages); spin_unlock_irqrestore(&master->queue_lock, flags); + spi_dma_unmap_msg(master, mesg); + if (master->cur_msg_prepared && master->unprepare_message) { ret = master->unprepare_message(master, mesg); if (ret) { diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h index 21a7251d85ee..14380043491b 100644 --- a/include/linux/spi/spi.h +++ b/include/linux/spi/spi.h @@ -25,6 +25,8 @@ #include <linux/kthread.h> #include <linux/completion.h> +struct dma_chan; + /* * INTERFACES between SPI master-side drivers and SPI infrastructure. * (There's no SPI slave support for Linux yet...) @@ -385,6 +387,17 @@ struct spi_master { void (*cleanup)(struct spi_device *spi); /* + * Used to enable core support for DMA handling, if can_dma() + * exists and returns true then the transfer will be mapped + * prior to transfer_one() being called. The driver should + * not modify or store xfer and dma_tx and dma_rx must be set + * while the device is prepared. + */ + bool (*can_dma)(struct spi_master *master, + struct spi_device *spi, + struct spi_transfer *xfer); + + /* * These hooks are for drivers that want to use the generic * master transfer queueing mechanism. If these are used, the * transfer() function above must NOT be specified by the driver. @@ -402,6 +415,7 @@ struct spi_master { bool rt; bool auto_runtime_pm; bool cur_msg_prepared; + bool cur_msg_mapped; struct completion xfer_completion; int (*prepare_transfer_hardware)(struct spi_master *master); @@ -423,6 +437,10 @@ struct spi_master { /* gpio chip select */ int *cs_gpios; + + /* DMA channels for use with core dmaengine helpers */ + struct dma_chan *dma_tx; + struct dma_chan *dma_rx; }; static inline void *spi_master_get_devdata(struct spi_master *master) -- 1.8.5.2

11 years, 4 months

1
1
0 0

queue boot: 31 pass, 0 fail (v3.12.8)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: queue Git describe: v3.12.8 Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.4 sec omap3-beagle-xm PASS: 1 min 4.1 sec am335x-bone PASS: 0 min 26.2 sec omap4-panda PASS: 1 min 4.9 sec omap4-panda-es PASS: 1 min 3.6 sec omap3-tobi,3730storm PASS: 0 min 20.3 sec omap3-tobi,3530overo PASS: 0 min 21.3 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 16.9 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.2 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.0 sec imx6q-wandboard PASS: 0 min 14.8 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.8 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.9 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 26.7 sec tegra30-beaver PASS: 0 min 20.7 sec am335x-boneblack PASS: 0 min 31.6 sec omap3-beagle-xm PASS: 0 min 60.0 sec sun7i-a20-cubieboard2 PASS: 0 min 13.0 sec armada-370-mirabox PASS: 0 min 20.6 sec omap4-panda PASS: 1 min 2.3 sec omap4-panda-es PASS: 1 min 2.8 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.3 sec am335x-bone PASS: 0 min 33.2 sec imx6q-wandboard PASS: 0 min 15.7 sec omap3-tobi,3730storm PASS: 0 min 22.5 sec imx6dl-wandboard,wand-dual PASS: 0 min 16.5 sec omap3-tobi,3530overo PASS: 0 min 19.9 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 33.1 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.3 sec

11 years, 4 months

1
0
0 0

mainline boot: 32 pass, 0 fail (v3.13-rc8-46-g85ce70f)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-rc8-46-g85ce70f Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.9 sec omap3-beagle-xm PASS: 1 min 1.6 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 6.1 sec omap4-panda-es PASS: 1 min 2.0 sec omap3-tobi,3730storm PASS: 0 min 23.6 sec omap3-tobi,3530overo PASS: 0 min 22.0 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.9 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.0 sec imx6q-wandboard PASS: 0 min 16.7 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.9 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 1 min 1.2 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 29.8 sec tegra30-beaver PASS: 0 min 17.6 sec am335x-boneblack PASS: 0 min 21.8 sec omap3-beagle-xm PASS: 0 min 55.5 sec sun7i-a20-cubieboard2 PASS: 0 min 13.1 sec armada-370-mirabox PASS: 0 min 20.6 sec omap4-panda PASS: 1 min 2.6 sec omap4-panda-es PASS: 0 min 59.4 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.9 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec am335x-bone PASS: 0 min 23.5 sec imx6q-wandboard PASS: 0 min 16.8 sec omap3-tobi,3730storm PASS: 0 min 19.5 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.8 sec omap3-tobi,3530overo PASS: 0 min 23.3 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 27.5 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.3 sec

11 years, 4 months

1
0
0 0

mainline boot: 32 pass, 0 fail (v3.13-rc8-39-g93a11c8)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-rc8-39-g93a11c8 Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.0 sec omap3-beagle-xm PASS: 0 min 56.0 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 6.8 sec omap4-panda-es PASS: 1 min 1.7 sec omap3-tobi,3730storm PASS: 0 min 24.1 sec omap3-tobi,3530overo PASS: 0 min 21.8 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 18.2 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.2 sec imx6q-wandboard PASS: 0 min 16.5 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.0 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 28.9 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 29.0 sec tegra30-beaver PASS: 0 min 19.0 sec am335x-boneblack PASS: 0 min 21.8 sec omap3-beagle-xm PASS: 0 min 56.0 sec sun7i-a20-cubieboard2 PASS: 0 min 13.0 sec armada-370-mirabox PASS: 0 min 20.6 sec omap4-panda PASS: 1 min 2.0 sec omap4-panda-es PASS: 1 min 1.0 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.6 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.5 sec am335x-bone PASS: 0 min 23.5 sec imx6q-wandboard PASS: 0 min 16.9 sec omap3-tobi,3730storm PASS: 0 min 22.2 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.8 sec omap3-tobi,3530overo PASS: 0 min 23.4 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 28.1 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.3 sec

11 years, 4 months

1
0
0 0

[PATCH] ASoC: core: Return -ENOTSUPP from set_sysclk() if no operation provided

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> Make it easier for generic code to work with set_sysclk() by distinguishing between the operation not being supported and an error as is done for other operations like set_dai_fmt() Signed-off-by: Mark Brown <broonie(a)linaro.org> --- sound/soc/soc-core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c index 3a128f0cd752..fe1df50805a3 100644 --- a/sound/soc/soc-core.c +++ b/sound/soc/soc-core.c @@ -3485,7 +3485,7 @@ int snd_soc_dai_set_sysclk(struct snd_soc_dai *dai, int clk_id, return dai->codec->driver->set_sysclk(dai->codec, clk_id, 0, freq, dir); else - return -EINVAL; + return -ENOTSUPP; } EXPORT_SYMBOL_GPL(snd_soc_dai_set_sysclk); @@ -3506,7 +3506,7 @@ int snd_soc_codec_set_sysclk(struct snd_soc_codec *codec, int clk_id, return codec->driver->set_sysclk(codec, clk_id, source, freq, dir); else - return -EINVAL; + return -ENOTSUPP; } EXPORT_SYMBOL_GPL(snd_soc_codec_set_sysclk); -- 1.8.5.2

11 years, 4 months

1
0
0 0

[PATCH v6 0/3] AArch64: KGDB support

by vijay.kilari＠gmail.com

From: Vijaya Kumar K <Vijaya.Kumar(a)caviumnetworks.com> Based on the step-handler and break-handler hooks patch from Sandeepa, KGDB debugging support is added for EL1 debug in AArch64 mode. Any updates that come for Patch 1 from Sandeepa will be rebased in next version With second patch,register layout is updated to be inline with GDB tool. Basic GDB connection, break point set/clear and info commands are supported except step/next debugging With third patch, step/next debugging support is added, where in pc is updated to point to the instruction to be stepped and stopped. With fourth patch, the compile time breakpoint instruction reordering is fixed by making kgbd_breakpoint() as noinline Tested with ARM64 simulator v6: - Change pstate register to 8 bytes to make endian nuetral. Use GDB below GDB patch to display pstate in Big endian mode. https://sourceware.org/ml/gdb-patches/2013-12/msg00720.html Thanks to Andrew. v5: - Updated BRK #imm16 value to 0x400 & 0x401 as per recommendation as per Marcus recommendataion http://patchwork.ozlabs.org/patch/290801/ - Rebased to 3.13 AArch64 kernel v4: - Updated kgdb_single_step and kgdb_cpu_doing_single_step variables properly based on gdb state v3: - Rebased to v4 version of Sandeepa Prabhu's patch (patch 1) - Made dynamic break point instruction encoding generic - Made ESR value encoding generic for dynamic and compile break point - Used memcpy and memset to copy register contents to gdb buffer - Fixed reordering of break point instruction by compiler with patch 3 - Rebased against AAach64 upstream kernel v2: - Moved break instruction encoding to debug-monitors.h file - Fixed endianess of compile break instruction encoding - Updated I/O buffer sizes - Updated register buffer size - Remove changes to debug_exception handler in entry.S for - ELR update and step debugging with update pc instead of ELR - Rebased against AArch64 upstream kernel v1: - Initial patch-set Vijaya Kumar K (3): AArch64: KGDB: Add Basic KGDB support AArch64: KGDB: Add step debugging support KGDB: make kgdb_breakpoint() as noinline arch/arm64/include/asm/debug-monitors.h | 47 +++++ arch/arm64/include/asm/kgdb.h | 86 ++++++++ arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/kgdb.c | 341 +++++++++++++++++++++++++++++++ kernel/debug/debug_core.c | 2 +- 5 files changed, 476 insertions(+), 1 deletion(-) create mode 100644 arch/arm64/include/asm/kgdb.h create mode 100644 arch/arm64/kernel/kgdb.c -- 1.7.9.5

11 years, 4 months

6
14
0 0

mainline boot: 32 pass, 0 fail (v3.13-rc8-27-g2e67c56)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-rc8-27-g2e67c56 Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.0 sec omap3-beagle-xm PASS: 0 min 59.4 sec am335x-bone PASS: 0 min 31.6 sec omap4-panda PASS: 1 min 4.8 sec omap4-panda-es PASS: 1 min 2.6 sec omap3-tobi,3730storm PASS: 0 min 24.2 sec omap3-tobi,3530overo PASS: 0 min 21.8 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.2 sec imx6q-wandboard PASS: 0 min 16.9 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.2 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.9 sec armada-370-mirabox PASS: 0 min 19.9 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 28.8 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 32.1 sec tegra30-beaver PASS: 0 min 14.2 sec am335x-boneblack PASS: 0 min 21.8 sec omap3-beagle-xm PASS: 0 min 58.5 sec sun7i-a20-cubieboard2 PASS: 0 min 13.1 sec armada-370-mirabox PASS: 0 min 20.7 sec omap4-panda PASS: 1 min 1.1 sec omap4-panda-es PASS: 1 min 3.7 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.7 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.5 sec am335x-bone PASS: 0 min 23.4 sec imx6q-wandboard PASS: 0 min 15.9 sec omap3-tobi,3730storm PASS: 0 min 22.8 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.9 sec omap3-tobi,3530overo PASS: 0 min 20.0 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 27.8 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec

11 years, 4 months

1
0
0 0

mainline boot: 32 pass, 0 fail (v3.13-rc8-20-g1a60864)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: mainline Git describe: v3.13-rc8-20-g1a60864 Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.0 sec omap3-beagle-xm PASS: 0 min 59.4 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 5.4 sec omap4-panda-es PASS: 1 min 1.3 sec omap3-tobi,3730storm PASS: 0 min 24.2 sec omap3-tobi,3530overo PASS: 0 min 22.0 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.3 sec imx6q-wandboard PASS: 0 min 16.4 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.0 sec armada-370-mirabox PASS: 0 min 20.0 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.0 sec multi_v7_defconfig ------------------ ste-snowball PASS: 0 min 32.5 sec tegra30-beaver PASS: 0 min 17.4 sec am335x-boneblack PASS: 0 min 21.8 sec omap3-beagle-xm PASS: 0 min 58.8 sec sun7i-a20-cubieboard2 PASS: 0 min 13.1 sec armada-370-mirabox PASS: 0 min 20.5 sec omap4-panda PASS: 1 min 4.2 sec omap4-panda-es PASS: 1 min 2.6 sec armada-xp-openblocks-ax3-4 PASS: 0 min 22.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 16.5 sec am335x-bone PASS: 0 min 23.4 sec imx6q-wandboard PASS: 0 min 16.9 sec omap3-tobi,3730storm PASS: 0 min 22.3 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.9 sec omap3-tobi,3530overo PASS: 0 min 20.1 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 27.7 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec

11 years, 4 months

1
0
0 0

next boot: 30 pass, 2 fail (next-20140115)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: next Git describe: next-20140115 Failed boot tests (console logs at the end) =========================================== exynos5250-arndale: FAIL: exynos_defconfig omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 25.2 sec omap3-beagle-xm PASS: 1 min 1.4 sec am335x-bone PASS: 0 min 26.9 sec omap4-panda PASS: 1 min 7.8 sec omap4-panda-es PASS: 1 min 3.2 sec omap3-tobi,3730storm PASS: 0 min 21.5 sec omap3-tobi,3530overo PASS: 0 min 22.4 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.1 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.1 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.0 sec imx6q-wandboard PASS: 0 min 15.9 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.3 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.0 sec armada-370-mirabox PASS: 0 min 20.3 sec exynos_defconfig ---------------- exynos5250-arndale FAIL: 1 min 25.0 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 20.3 sec tegra30-beaver PASS: 0 min 19.1 sec am335x-boneblack PASS: 0 min 22.8 sec omap3-beagle-xm PASS: 0 min 48.9 sec sun7i-a20-cubieboard2 PASS: 0 min 13.7 sec armada-370-mirabox PASS: 0 min 21.5 sec omap4-panda PASS: 0 min 51.6 sec omap4-panda-es FAIL: 1 min 47.1 sec armada-xp-openblocks-ax3-4 PASS: 0 min 24.0 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.4 sec am335x-bone PASS: 0 min 25.4 sec imx6q-wandboard PASS: 0 min 16.6 sec omap3-tobi,3730storm PASS: 0 min 23.0 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.5 sec omap3-tobi,3530overo PASS: 0 min 21.2 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 30.2 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.5 sec Console logs for failures ========================= exynos_defconfig ---------------- exynos5250-arndale: FAIL: last 24 lines of boot log: ---------------------------------------------------- [ 1.879995] mmc0: new high speed DDR MMC card at address 0001 [ 1.885978] isa bounce pool size: 16 pages [ 1.886760] EXT_28_OFF: disabling [ 1.893075] mmcblk0: mmc0:0001 M4G1FA 3.72 GiB [ 1.893229] VDD_33ON_2.8V: disabling [ 1.901200] exynos-dp 145b0000.dp-controller: unable to find phy [ 1.907092] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 1.909954] mmcblk0boot0: mmc0:0001 M4G1FA partition 1 1.00 MiB [ 1.910160] mmcblk0boot1: mmc0:0001 M4G1FA partition 2 1.00 MiB [ 1.910361] mmcblk0rpmb: mmc0:0001 M4G1FA partition 3 128 KiB [ 1.933554] mmcblk0: p1 p2 p3 p4 [ 1.938034] mmcblk0boot1: unknown partition table [ 1.942297] mmcblk0boot0: unknown partition table [ 2.133180] exynos-dp 145b0000.dp-controller: unable to find phy [ 2.137749] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 2.146492] input: gpio_keys.4 as /devices/gpio_keys.4/input/input0 [ 2.152187] exynos-dp 145b0000.dp-controller: unable to find phy [ 2.157834] s3c-rtc 101e0000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 2.166314] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral [ 2.175172] Waiting for root device /dev/mmcblk1p3... ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 85.05 seconds. # PYBOOT: Result: FAIL multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 2.023284] random: nonblocking pool is initialized [ 2.280578] usb 1-1.1: new high-speed USB device number 3 using ehci-omap [ 2.413757] smsc95xx v1.0.4 [ 2.475250] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-4a064c00.ehci-1.1, smsc95xx USB 2.0 Ethernet, 1e:49:bc:cd:c5:d9 [ 2.870391] omap_i2c 48070000.i2c: controller timed out [ 3.051940] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz [ 3.059509] omap_i2c 48072000.i2c: bus 1 rev0.11 at 400 kHz [ 3.069824] omap_i2c 48060000.i2c: bus 2 rev0.11 at 100 kHz [ 3.077270] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz [ 3.083557] omap-dma-engine 4a056000.dma-controller: allocating channel for 62 [ 3.091247] omap-dma-engine 4a056000.dma-controller: allocating channel for 61 [ 3.098907] 4809c000.mmc supply vmmc_aux not found, using dummy regulator [ 3.107360] omap_hsmmc 4809c000.mmc: pins are not configured from the driver [ 3.152526] omap-dma-engine 4a056000.dma-controller: allocating channel for 60 [ 3.159545] omap-dma-engine 4a056000.dma-controller: allocating channel for 59 [ 3.167755] 480d5000.mmc supply vmmc_aux not found, using dummy regulator [ 3.187896] mmc0: host does not support reading read-only switch. assuming write-enable. [ 3.198425] mmc0: new high speed SDHC card at address 1234 [ 3.204223] isa bounce pool size: 16 pages [ 3.209014] mmcblk0: mmc0:1234 SA04G 3.63 GiB ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 107.08 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

[PATCH v12 0/4] arm64 topology

by Mark Brown

Another round of cosmetic updates here, this should address everything from the last round. arm64: topology: Implement basic CPU topology support arm64: topology: Add support for topology DT bindings arm64: topology: Tell the scheduler about the relative arm64: topology: Provide relative power numbers for cores

11 years, 4 months

1
4
0 0

[PATCH V2] tty: Fallback to use dynamic major number

by Tushar Behera

In a multi-platform scenario, the hard-coded major/minor numbers in serial drivers may conflict with each other. A typical scenario is observed with amba-pl011 and samsung-uart drivers, both of these drivers use same set of major/minor numbers. If both of these drivers are enabled, probe of samsung-uart driver fails because the desired node is busy. The issue is fixed by adding a fallback in driver core, so that we can use dynamic major number in case device node allocation fails for hard-coded major/minor number. Signed-off-by: Tushar Behera <tushar.behera(a)linaro.org> --- Initial approach to fix this problem was by forcing samsung-uart driver to use dynamic major number, but it was rejected [1] because of possible user-space breakage. Current approach falls back to dynamic major number as a fallback in case of failure. [1] https://lkml.org/lkml/2013/12/27/2 Can I get an Acked-by/Reviewed-by before I send this to lkml? Changes for V2: * Added warning message in case major number is getting orverriden drivers/tty/tty_io.c | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c index c74a00a..ff4aada 100644 --- a/drivers/tty/tty_io.c +++ b/drivers/tty/tty_io.c @@ -3341,6 +3341,24 @@ int tty_register_driver(struct tty_driver *driver) dev_t dev; struct device *d; + if (driver->major) { + dev = MKDEV(driver->major, driver->minor_start); + error = register_chrdev_region(dev, driver->num, driver->name); + /* In case of error, fall back to dynamic allocation */ + if (error < 0) { + printk(KERN_WARNING + "Default device node (%d:%d) for %s is busy, " + "using dynamic major number\n", + driver->major, driver->minor_start, + driver->name); + driver->major = 0; + } + } + + /* + * Don't replace the following check with an else to above if statement, + * as it may also be called as a fallback. + */ if (!driver->major) { error = alloc_chrdev_region(&dev, driver->minor_start, driver->num, driver->name); @@ -3348,9 +3366,6 @@ int tty_register_driver(struct tty_driver *driver) driver->major = MAJOR(dev); driver->minor_start = MINOR(dev); } - } else { - dev = MKDEV(driver->major, driver->minor_start); - error = register_chrdev_region(dev, driver->num, driver->name); } if (error < 0) goto err; -- 1.7.9.5

11 years, 4 months

2
1
0 0

arm-soc boot: 31 pass, 1 fail (v3.13-rc5-1169-gfb54a12)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.13-rc5-1169-gfb54a12 Failed boot tests (console logs at the end) =========================================== omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.9 sec omap3-beagle-xm PASS: 0 min 54.0 sec am335x-bone PASS: 0 min 26.8 sec omap4-panda PASS: 1 min 10.2 sec omap4-panda-es PASS: 1 min 6.6 sec omap3-tobi,3730storm PASS: 0 min 20.9 sec omap3-tobi,3530overo PASS: 0 min 21.8 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.0 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.5 sec imx6q-wandboard PASS: 0 min 16.9 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.0 sec armada-370-mirabox PASS: 0 min 20.3 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 29.9 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 20.4 sec tegra30-beaver PASS: 0 min 23.4 sec am335x-boneblack PASS: 0 min 22.6 sec omap3-beagle-xm PASS: 0 min 44.1 sec sun7i-a20-cubieboard2 PASS: 0 min 13.5 sec armada-370-mirabox PASS: 0 min 21.6 sec omap4-panda PASS: 0 min 52.6 sec omap4-panda-es FAIL: 1 min 48.2 sec armada-xp-openblocks-ax3-4 PASS: 0 min 23.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.2 sec am335x-bone PASS: 0 min 24.3 sec imx6q-wandboard PASS: 0 min 16.6 sec omap3-tobi,3730storm PASS: 0 min 24.8 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.6 sec omap3-tobi,3530overo PASS: 0 min 20.8 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 28.3 sec sama5_defconfig --------------- sama5d35ek PASS: 2 min 0.7 sec Console logs for failures ========================= multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 1.624114] Registering SWP/SWPB emulation handler [ 1.629974] vwl1271: 1800 mV [ 1.636840] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 1.646392] twl 0-0048: PIH (irq 39) nested IRQs [ 1.652648] twl_rtc rtc.11: Enabling TWL-RTC [ 1.659515] twl_rtc rtc.11: rtc core: registered rtc.11 as rtc0 [ 1.666320] VAUX1_6030: 1000 <--> 3000 mV at 2800 mV [ 1.672332] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV [ 1.678344] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV [ 1.684326] VMMC: 1200 <--> 3000 mV at 3000 mV [ 1.689788] VPP: 1800 <--> 2500 mV at 1900 mV [ 1.695098] VUSIM: 1200 <--> 2900 mV at 1800 mV [ 1.700134] VDAC: 1800 mV [ 1.700134] VANA: 2100 mV [ 1.707153] VCXIO: 1800 mV [ 1.707153] VUSB: 3300 mV [ 1.713928] V1V8: 1800 mV [ 1.717407] V2V1: 2100 mV [ 1.724609] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz [ 1.816497] usb 1-1: new high-speed USB device number 2 using ehci-omap ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 108.16 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

arm-soc boot: 31 pass, 1 fail (v3.13-rc5-1125-g7d464b9)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.13-rc5-1125-g7d464b9 Failed boot tests (console logs at the end) =========================================== omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.9 sec omap3-beagle-xm PASS: 0 min 54.6 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 9.7 sec omap4-panda-es PASS: 1 min 8.6 sec omap3-tobi,3730storm PASS: 0 min 24.0 sec omap3-tobi,3530overo PASS: 0 min 21.7 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 20.2 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 18.2 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.4 sec imx6q-wandboard PASS: 0 min 15.7 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 21.9 sec armada-370-mirabox PASS: 0 min 20.3 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 28.9 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 17.2 sec tegra30-beaver PASS: 0 min 19.0 sec am335x-boneblack PASS: 0 min 22.7 sec omap3-beagle-xm PASS: 0 min 49.2 sec sun7i-a20-cubieboard2 PASS: 0 min 13.5 sec armada-370-mirabox PASS: 0 min 21.4 sec omap4-panda PASS: 0 min 54.0 sec omap4-panda-es FAIL: 1 min 47.8 sec armada-xp-openblocks-ax3-4 PASS: 0 min 23.8 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.2 sec am335x-bone PASS: 0 min 24.3 sec imx6q-wandboard PASS: 0 min 16.7 sec omap3-tobi,3730storm PASS: 0 min 23.1 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.6 sec omap3-tobi,3530overo PASS: 0 min 20.6 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 28.6 sec sama5_defconfig --------------- sama5d35ek PASS: 2 min 5.7 sec Console logs for failures ========================= multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 1.612701] Power Management for TI OMAP4. [ 1.617004] OMAP4 PM: u-boot >= v2012.07 is required for full PM support [ 1.624114] Registering SWP/SWPB emulation handler [ 1.630279] vwl1271: 1800 mV [ 1.636962] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 1.646240] twl 0-0048: PIH (irq 39) nested IRQs [ 1.652557] twl_rtc rtc.11: Enabling TWL-RTC [ 1.659393] twl_rtc rtc.11: rtc core: registered rtc.11 as rtc0 [ 1.666259] VAUX1_6030: 1000 <--> 3000 mV at 2800 mV [ 1.672302] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV [ 1.678283] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV [ 1.684265] VMMC: 1200 <--> 3000 mV at 3000 mV [ 1.689819] VPP: 1800 <--> 2500 mV at 1900 mV [ 1.695129] VUSIM: 1200 <--> 2900 mV at 1800 mV [ 1.700164] VDAC: 1800 mV [ 1.700164] VANA: 2100 mV [ 1.707153] VCXIO: 1800 mV [ 1.710449] VUSB: 3300 mV [ 1.713958] V1V8: 1800 mV [ 1.717407] V2V1: 2100 mV ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 107.78 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

1
0
0 0

arm-soc boot: 31 pass, 1 fail (v3.13-rc5-1111-gc954e78)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.13-rc5-1111-gc954e78 Failed boot tests (console logs at the end) =========================================== omap4-panda-es: FAIL: multi_v7_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.8 sec omap3-beagle-xm PASS: 0 min 59.8 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 10.3 sec omap4-panda-es PASS: 1 min 9.5 sec omap3-tobi,3730storm PASS: 0 min 21.1 sec omap3-tobi,3530overo PASS: 0 min 21.6 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 17.0 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 17.0 sec imx6dl-wandboard,wand-solo PASS: 0 min 18.4 sec imx6q-wandboard PASS: 0 min 16.8 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.0 sec armada-370-mirabox PASS: 0 min 20.2 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 28.7 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 16.8 sec tegra30-beaver PASS: 0 min 24.1 sec am335x-boneblack PASS: 0 min 22.6 sec omap3-beagle-xm PASS: 0 min 47.6 sec sun7i-a20-cubieboard2 PASS: 0 min 13.4 sec armada-370-mirabox PASS: 0 min 21.4 sec omap4-panda PASS: 0 min 51.8 sec omap4-panda-es FAIL: 1 min 47.8 sec armada-xp-openblocks-ax3-4 PASS: 0 min 24.0 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.3 sec am335x-bone PASS: 0 min 24.3 sec imx6q-wandboard PASS: 0 min 16.3 sec omap3-tobi,3730storm PASS: 0 min 22.8 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.5 sec omap3-tobi,3530overo PASS: 0 min 20.7 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 31.4 sec sama5_defconfig --------------- sama5d35ek PASS: 0 min 17.4 sec Console logs for failures ========================= multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 1.624053] Registering SWP/SWPB emulation handler [ 1.629943] vwl1271: 1800 mV [ 1.636962] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 1.646331] twl 0-0048: PIH (irq 39) nested IRQs [ 1.652618] twl_rtc rtc.11: Enabling TWL-RTC [ 1.659362] twl_rtc rtc.11: rtc core: registered rtc.11 as rtc0 [ 1.666229] VAUX1_6030: 1000 <--> 3000 mV at 2800 mV [ 1.672271] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV [ 1.678283] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV [ 1.684265] VMMC: 1200 <--> 3000 mV at 3000 mV [ 1.689727] VPP: 1800 <--> 2500 mV at 1900 mV [ 1.695037] VUSIM: 1200 <--> 2900 mV at 1800 mV [ 1.700042] VDAC: 1800 mV [ 1.703613] VANA: 2100 mV [ 1.707061] VCXIO: 1800 mV [ 1.710113] VUSB: 3300 mV [ 1.713836] V1V8: 1800 mV [ 1.717315] V2V1: 2100 mV [ 1.724548] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz [ 1.816375] usb 1-1: new high-speed USB device number 2 using ehci-omap ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 107.76 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

3
2
0 0

[PATCH 1/2] sched/nohz: add debugfs control over sched_tick_max_deferment

by Kevin Hilman

Allow debugfs override of sched_tick_max_deferment in order to ease finding/fixing the remaining issues with full nohz. The value to be written is in jiffies, and -1 means the max deferment is disabled (scheduler_tick_max_deferment() returns KTIME_MAX.) Cc: Frederic Weisbecker <fweisbec(a)gmail.com> Signed-off-by: Kevin Hilman <khilman(a)linaro.org> --- kernel/sched/core.c | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 5ac63c9a995a..4b1fe3e69fe4 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -2175,6 +2175,8 @@ void scheduler_tick(void) } #ifdef CONFIG_NO_HZ_FULL +static u32 sched_tick_max_deferment = HZ; + /** * scheduler_tick_max_deferment * @@ -2193,13 +2195,25 @@ u64 scheduler_tick_max_deferment(void) struct rq *rq = this_rq(); unsigned long next, now = ACCESS_ONCE(jiffies); - next = rq->last_sched_tick + HZ; + if (sched_tick_max_deferment == -1) + return KTIME_MAX; + + next = rq->last_sched_tick + sched_tick_max_deferment; if (time_before_eq(next, now)) return 0; return jiffies_to_usecs(next - now) * NSEC_PER_USEC; } + +static __init int sched_nohz_full_init_debug(void) +{ + debugfs_create_u32("sched_tick_max_deferment", 0644, NULL, + &sched_tick_max_deferment); + + return 0; +} +late_initcall(sched_nohz_full_init_debug); #endif notrace unsigned long get_parent_ip(unsigned long addr) -- 1.8.3

11 years, 4 months

2
7
0 0

[PATCH v10 0/4] arm64 topology

by Mark Brown

Another round of minor tweaks - Remove some problematic and controversial prints - Pass cluster_id around as a pointer - Move slab.h further back in the series arm64: topology: Implement basic CPU topology support arm64: topology: Add support for topology DT bindings arm64: topology: Tell the scheduler about the relative arm64: topology: Provide relative power numbers for cores

11 years, 4 months

4
13
0 0

arm-soc boot: 30 pass, 2 fail (v3.13-rc5-1101-g475a405)

by Kevin's boot bot

Automated DT boot report for various ARM defconfigs. Tree/Branch: arm-soc Git describe: v3.13-rc5-1101-g475a405 Failed boot tests (console logs at the end) =========================================== omap4-panda-es: FAIL: multi_v7_defconfig sama5d35ek: FAIL: sama5_defconfig Full Report =========== omap2plus_defconfig ------------------- am335x-boneblack PASS: 0 min 24.9 sec omap3-beagle-xm PASS: 1 min 0.5 sec am335x-bone PASS: 0 min 26.6 sec omap4-panda PASS: 1 min 7.0 sec omap4-panda-es PASS: 1 min 8.0 sec omap3-tobi,3730storm PASS: 0 min 21.3 sec omap3-tobi,3530overo PASS: 0 min 22.0 sec tegra_defconfig --------------- tegra30-beaver PASS: 0 min 21.5 sec imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual PASS: 0 min 16.9 sec imx6dl-wandboard,wand-solo PASS: 0 min 19.4 sec imx6q-wandboard PASS: 0 min 15.5 sec sunxi_defconfig --------------- sun7i-a20-cubieboard2 PASS: 0 min 12.1 sec mvebu_defconfig --------------- armada-xp-openblocks-ax3-4 PASS: 0 min 22.2 sec armada-370-mirabox PASS: 0 min 20.2 sec exynos_defconfig ---------------- exynos5250-arndale PASS: 0 min 28.8 sec multi_v7_defconfig ------------------ ste-snowball PASS: 1 min 17.5 sec tegra30-beaver PASS: 0 min 19.2 sec am335x-boneblack PASS: 0 min 22.6 sec omap3-beagle-xm PASS: 0 min 47.1 sec sun7i-a20-cubieboard2 PASS: 0 min 13.6 sec armada-370-mirabox PASS: 0 min 21.5 sec omap4-panda PASS: 0 min 54.2 sec omap4-panda-es FAIL: 1 min 46.0 sec armada-xp-openblocks-ax3-4 PASS: 0 min 23.9 sec imx6dl-wandboard,wand-solo PASS: 0 min 17.2 sec am335x-bone PASS: 0 min 24.3 sec imx6q-wandboard PASS: 0 min 17.8 sec omap3-tobi,3730storm PASS: 0 min 22.9 sec imx6dl-wandboard,wand-dual PASS: 0 min 17.4 sec omap3-tobi,3530overo PASS: 0 min 20.7 sec u8500_defconfig --------------- ste-snowball PASS: 0 min 31.2 sec sama5_defconfig --------------- sama5d35ek FAIL: 1 min 52.8 sec Console logs for failures ========================= multi_v7_defconfig ------------------ omap4-panda-es: FAIL: last 24 lines of boot log: ------------------------------------------------ [ 1.616851] OMAP4 PM: u-boot >= v2012.07 is required for full PM support [ 1.623992] Registering SWP/SWPB emulation handler [ 1.629852] vwl1271: 1800 mV [ 1.637054] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 1.646270] twl 0-0048: PIH (irq 39) nested IRQs [ 1.652526] twl_rtc rtc.11: Enabling TWL-RTC [ 1.659301] twl_rtc rtc.11: rtc core: registered rtc.11 as rtc0 [ 1.666168] VAUX1_6030: 1000 <--> 3000 mV at 2800 mV [ 1.672180] VAUX2_6030: 1200 <--> 2800 mV at 1800 mV [ 1.678192] VAUX3_6030: 1000 <--> 3000 mV at 1200 mV [ 1.684173] VMMC: 1200 <--> 3000 mV at 3000 mV [ 1.689666] VPP: 1800 <--> 2500 mV at 1900 mV [ 1.694976] VUSIM: 1200 <--> 2900 mV at 1800 mV [ 1.700012] VDAC: 1800 mV [ 1.700012] VANA: 2100 mV [ 1.707000] VCXIO: 1800 mV [ 1.710296] VUSB: 3300 mV [ 1.713806] V1V8: 1800 mV [ 1.717315] V2V1: 2100 mV [ 1.724365] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 106.03 seconds. # PYBOOT: Result: FAIL sama5_defconfig --------------- sama5d35ek: FAIL: last 24 lines of boot log: -------------------------------------------- U-Boot> tftp 0x22000000 tmp/sama5-q0KVff/tmp5xSpAZ-uImage tftp 0x22000000 tmp/sama5-q0KVff/tmp5xSpAZ-uImage macb0: PHY present at 0 macb0: link up, 100Mbps full-duplex (lpa: 0x45e1) Using macb0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.182 Filename 'tmp/sama5-q0KVff/tmp5xSpAZ-uImage'. Load address: 0x22000000 Loading: *#T T #T #T #T ## Abort U-Boot> tftp 0x22000000 tmp/sama5-q0KVff/tmp5xSpAZ-uImage tftp 0x22000000 tmp/sama5-q0KVff/tmp5xSpAZ-uImage macb0: PHY present at 0 macb0: link up, 100Mbps full-duplex (lpa: 0x45e1) Using macb0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.182 Filename 'tmp/sama5-q0KVff/tmp5xSpAZ-uImage'. Load address: 0x22000000 Loading: *########T ############T ###########################T ################## ################################T ###############################T ## #############~$off # PYBOOT: Exception: ERROR: Timeout loading tmp/sama5-q0KVff/tmp5xSpAZ-uImage. Giving up. # PYBOOT: Time: 112.77 seconds. # PYBOOT: Result: FAIL

11 years, 4 months

2
1
0 0

[PATCH v6 0/6] Hardware Reduced Mode Cleanup for ACPI

by al.stone＠linaro.org

From: Al Stone <al.stone(a)linaro.org> This series of patches starts with Hanjun's patch to create a kernel config item for CONFIG_ACPI_REDUCED_HARDWARE [0]. Building on that, I then reviewed all of the code that touched any of several fields in the FADT that the OSPM is supposed to ignore when ACPI is in Hardware Reduced mode [1]. Any time there was a use of one of the fields to be ignored, I evaluated whether or not the code was implementing Hardware Reduced mode correctly. Similarly, for each the flags in the FADT flags field that are to be ignored in Hardware Reduced mode, the kernel code was again scanned for proper usage. The remainder of the patches are to fix all of the situations I could find where the kernel would not behave correctly in this ACPI mode. These seem to work just fine on the RTSM model for ARMv7, both with and without ACPI enabled, and with and without ACPI_REDUCED_HARDWARE enabled; similarly for the FVP model for ARMv8. The patches for ACPI on ARM hardware have been submitted elsewhere but they presume that reduced HW mode is functioning correctly. In the meantime, there's no way I can think of to test all possible scenarios so feedback would be greatly appreciated. [0] List at https://wiki.linaro.org/LEG/Engineering/Kernel/ACPI/AcpiReducedHw#Section_5… [1] Please see the ACPI Specification v5.0 for details on Hardware Reduced mode (sections 3.11.1, 4.1, 5.2.9, at a minimum). Changes for v6: -- Allow selection of CONFIG_ACPI_REDUCED_HARDWARE_ONLY to be more architecture-independent, but make it harder to accidentally enable. -- Make sure that ACPI ECs do not use the ACPI global lock when in hardware reduced mode (I had missed this case in earlier reviews of the kernel tree). Changes for v5: -- Clarify that if the kernel config option to build ACPI hardware reduced mode is used, it builds a hardware reduced *only* kernel (i.e., full legacy ACPI mode will no longer work). Changes for v4: -- Given the current state of ACPICA, disable CONFIG_ACPI_REDUCED_HARDWARE for use on anything other than ARM. -- Replaced #ifdefs with run-time checking for hardware reduced mode, whenever possible Changes for v3: -- Modified enabling ACPI_REDUCED_HARDWARE in ACPICA when using kernel config item CONFIG_ACPI_REDUCED_HARDWARE; now consistent with ACPICA code base where needed -- Enable X86 for CONFIG_ACPI_REDUCED_HARDWARE -- Minimize bus master reload patching -- Remove unneeded patch for dmi_check_system() (was 4/6) -- Correct the patch for removing unneeded map/unmap of FADT fields Changes for v2: -- Remove patch that was outside of reduced HW mode changes -- Simplify CONFIG_ACPI_REDUCED_HARDWARE in Kconfig -- Simplify use of CONFIG_ACPI_REDUCED_HARDWARE in #ifdefs -- Ensure changelogs are present -- Combine and simplify previous patches 8 & 10 Al Stone (6): ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY to enforce this ACPI mode ACPI: bus master reload not supported in reduced HW mode ACPI: HW reduced mode does not allow use of the FADT sci_interrupt field ACPI: in HW reduced mode, using FADT PM information is not allowed. ACPI: do not map/unmap memory regions for FADT entries in reduced HW mode ACPI: make sure ECs do not use the ACPI global lock drivers/acpi/Kconfig | 12 ++++++++++++ drivers/acpi/bus.c | 30 ++++++++++++++++-------------- drivers/acpi/ec.c | 12 ++++++++++-- drivers/acpi/osl.c | 38 +++++++++++++++++++------------------- drivers/acpi/pci_link.c | 2 ++ drivers/acpi/processor_idle.c | 14 ++++++++++++-- include/acpi/platform/aclinux.h | 6 ++++++ 7 files changed, 77 insertions(+), 37 deletions(-) -- 1.8.4.2

11 years, 4 months

4
23
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel