linaro-kernel

linaro-kernel@lists.linaro.org

10094 discussions

[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

[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

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

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

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

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

[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

[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

[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

[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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel