- Linaro-acpi - lists.linaro.org

[PATCH 0/3] rasdaemon: minor fixes from Debian packaging

by Al Stone

In order to get rasdaemon packaging to work well in Debian, I had to make a few minor fixes -- a printf missing a "%s", a manpage in the wrong section, and a dependency on having system logging running before starting the daemon itself. These are the patches for those fixes (they're already in the 0.5.6 Debian package). Al Stone (3): rasdaemon: correct a printf that was missing a field to print to rasdaemon: the man page should be section 8 not 1 rasdaemon: make sure daemon does not start until after logging does configure.ac | 2 +- man/Makefile.am | 2 +- man/rasdaemon.1.in | 67 ----------------------------------------------- man/rasdaemon.8.in | 67 +++++++++++++++++++++++++++++++++++++++++++++++ mce-intel-p4-p6.c | 2 +- misc/rasdaemon.service.in | 1 - 6 files changed, 70 insertions(+), 71 deletions(-) delete mode 100644 man/rasdaemon.1.in create mode 100644 man/rasdaemon.8.in -- 2.5.0

9 years, 6 months

1
3
0 0

[PATCH v10 0/5] Watchdog: introduce ARM SBSA watchdog driver

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and amd-seattle-soc.dtsi. (2)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Support getting timeout from parameter and FDT at the driver init stage. d.Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt) (2) register WS0 interrupt for the half timeout panic e.Timeout is from watchdog enabled to WS1 triggered. User can disable "half timeout panic" by kernel config or module parameter panic_enabled. Changelog: v10:Delete pretimeout support Separate the driver to two parts: (1) single stage timeout driver(ignore WS0 interrupt) (2) register WS0 interrupt for the half timeout panic timeout == (enable --> WS1) v9: https://lkml.org/lkml/2015/11/9/57 Rebase to latest kernel version(4.3). Update the Documentation of sbsa-gwdt device node info of FDT: (1) move some introduction to pretimeout patch (2) delete WS1 value from "interrupts" of binding documentation, since WS1 won't be handled by Linux. v8: https://lkml.org/lkml/2015/10/27/466 Rebase to latest kernel version(4.3-rc7). Separate the patches of GTDT support and arm_arch_timer. This clocksource relevant patch will upstreamed in a individual patchset. Update all the default timeout and pretimeout to 30s and 60s. Improve documentation and inline comments. Fix a bug in pretimeout support which makes timeout and pretimeout parameters initialization fail. v7: https://lkml.org/lkml/2015/8/24/611 Rebase to latest kernel version(4.2-rc7). Improve FDT support: geting resource by order, instead of name. According to the FDT support, Update the example dts file, gtdt.c and sbsa_gwdt.c. Pass the sparse test, and fix the warning. Fix the max_pretimeout and max_timeout value overflow bug. Delete the WCV output value. v6: https://lkml.org/lkml/2015/6/23/359 Improve the dtb example files: reduce the register frame size to 4K. Improve pretimeout support: (1) improve watchdog_init_timeouts function (2) rename watchdog_check_min_max_timeouts back to the original name (1) improve watchdog_timeout_invalid/watchdog_pretimeout_invalid Add the new features in the sbsa_gwdt driver: (1) In the second stage, user can feed the dog without cleaning WS0. (2) In the second stage, user can trigger WS1 by setting pretimeout = 0. (3) expand the max value of pretimeout, in case 10 second is not enough for a kdump kernel reboot in panic. v5: https://lkml.org/lkml/2015/6/10/357 Improve pretimeout support: (1)fix typo in documentation and comments. (2)fix the timeout limits validation bug. Simplify sbsa_gwdt driver: (1)integrate all the registers access functions into caller. v4: https://lkml.org/lkml/2015/6/2/4 Refactor GTDT support code: remove it from arch/arm64/kernel/acpi.c, put it into drivers/acpi/gtdt.c file. Integrate the GTDT code of drivers/clocksource/arm_arch_timer.c into drivers/acpi/gtdt.c. Improve pretimeout support, fix "pretimeout == 0" problem. Simplify sbsa_gwdt driver: (1)timeout/pretimeout limits setup; (2)keepalive function; (3)delete "clk == 0" check; (4)delete WS0 status bit check in interrupt routine; (5)sbsa_gwdt_set_wcv function. v3: https://lkml.org/lkml/2015/5/25/111 Delete "export arch_timer_get_rate" patch. Driver back to use arch_timer_get_cntfrq. Improve watchdog_init_timeouts function and update relevant documentation. Improve watchdog_timeout_invalid and watchdog_pretimeout_invalid. Improve foundation-v8.dts: delete the unnecessary tag of device node. Remove "ARM64 || COMPILE_TEST" from Kconfig. Add comments in arch/arm64/kernel/acpi.c Fix typoes and incorrect comments. v2: https://lkml.org/lkml/2015/5/21/172 Improve watchdog-kernel-api.txt documentation for pretimeout support. Export "arch_timer_get_rate" in arm_arch_timer.c. Add watchdog_init_timeouts API for pretimeout support in framework. Improve suspend and resume foundation in driver Improve timeout/pretimeout values init code in driver. Delete unnecessary items of the sbsa_gwdt struct and #define. Delete all unnecessary debug info in driver. Fix 64bit division bug. Use the arch_timer interface to get watchdog clock rate. Add MODULE_DEVICE_TABLE for platform device id. Fix typoes. v1: https://lkml.org/lkml/2015/5/15/279 The first version upstream patchset to linux mailing list. Fu Wei (5): Documentation: add sbsa-gwdt driver documentation ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi Watchdog: introduce ARM SBSA watchdog driver Watchdog: ARM SBSA Generic Watchdog half timeout panic support .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 35 ++ Documentation/watchdog/watchdog-parameters.txt | 6 + arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 9 + arch/arm64/boot/dts/arm/foundation-v8.dts | 8 + drivers/watchdog/Kconfig | 27 ++ drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 366 +++++++++++++++++++++ 7 files changed, 452 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.5.0

9 years, 6 months

7
45
0 0

Re: [Linaro-acpi] [PATCH v5] acpi, apei, arm64: APEI initial support for aarch64.

by Fu Wei

Hi Tyler, On 4 February 2016 at 05:24, Baicar, Tyler <tbaicar(a)codeaurora.org> wrote: > Hello Fu, > > Tested-by: Tyler Baicar<tbaicar(a)codeaurora.org> > > on a 4.5 kernel. I wasn't on the ACPI mailing list when this patch was sent > out, so I couldn't respond to the original thread. NP, great thanks for your help, I will add you in the cc list :-) > > Thanks, > Tyler > -- Best regards, Fu Wei Software Engineer Red Hat Software (Beijing) Co.,Ltd.Shanghai Branch Ph: +86 21 61221326(direct) Ph: +86 186 2020 4684 (mobile) Room 1512, Regus One Corporate Avenue,Level 15, One Corporate Avenue,222 Hubin Road,Huangpu District, Shanghai,China 200021

9 years, 6 months

1
0
0 0

[PATCH V2 0/4] acpi: cppc optimization patches

by Prashanth Prakash

Changes in V2: Fixed compilation error on i386 This series introduces changes to reduce the time required to send a frequency transition requests to the platform while using the cppc-cpufreq driver. With these changes we see significant improvement in the average time to send freq. transition request to the platform. Profiling on an ARM platform showed that the average transaction time per request reduced from 200us to under 20us. Ashwin Chaugule (1): ACPI / CPPC: Optimize PCC Read Write operations Prashanth Prakash (3): acpi: cppc: optimized cpc_read and cpc_write mailbox: pcc: optimized pcc_send_data acpi: cppc: replace writeX/readX to PCC with relaxed version drivers/acpi/cppc_acpi.c | 186 +++++++++++++++++++++++++++++++++++------------ drivers/mailbox/pcc.c | 111 ++++++++++++++++++++++++++-- 2 files changed, 244 insertions(+), 53 deletions(-) -- Qualcomm Technologies, Inc. on behalf of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

9 years, 6 months

5
14
0 0

[PATCH V3 00/21] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

by Tomasz Nowicki

>From the functionality point of view this series might be split into the following logic parts: 1. Make MMCONFIG code arch-agnostic which allows all architectures to collect PCI config regions and used when necessary. 2. Move non-arch specific bits to the core code. 3. Use MMCONFIG code and implement generic ACPI based PCI host controller driver. 4. Enable above driver on ARM64 Patches has been built on top of 4.4 and can be found here: git@github.com:semihalf-nowicki-tomasz/linux.git (pci-acpi-v3) NOTE, this patch set depends on Matthew's patches: http://www.spinics.net/lists/linux-pci/msg45950.html https://github.com/Vality/linux/tree/pci-fixes This has been tested on Cavium ThunderX server and QEMU. Any help in reviewing and testing is very appreciated. v2 -> v3 - fix legacy IRQ assigning and IO ports registration - remove reference to arch specific companion device for ia64 - move ACPI PCI host controller driver to pci_root.c - drop generic domain assignment for x86 and ia64 as I am not able to run all necessary test variants - drop patch which cleaned legacy IRQ assignment since it belongs to Mathew's series: https://patchwork.ozlabs.org/patch/557504/ - extend MCFG quirk code - rebased to 4.4 v1 -> v2 - moved non-arch specific piece of code to dirver/acpi/ directory - fixed IO resource handling - introduced PCI config accessors quirks matching - moved ACPI_COMPANION_SET to generic code Liu Jiang (1): ACPI, PCI: Refine the way to handle translation_offset for ACPI resources Tomasz Nowicki (20): x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y pci, acpi, mcfg: Provide default RAW ACPI PCI config space accessors. arm64, acpi: Use empty PCI config space accessors from mcfg.c file. pci, acpi, ecam: Add flag to indicate whether ECAM region was hot added or not. x86, pci: Cleanup platform specific MCFG data using previously added ECAM hot_added flag. pci, acpi: Move ACPI host bridge device companion assignment to core code. x86, ia64, pci: Remove ACPI companion device from platform specific data. pci, acpi: Provide generic way to assign bus domain number. x86, ia64: Include acpi_pci_{add|remove}_bus to the default pcibios_{add|remove}_bus implementation. acpi, mcfg: Implement two calls that might be used to inject/remove MCFG region. x86, acpi, pci: Use equivalent function introduced in previous patch. acpi, mcfg: Add default PCI config accessors implementation and initial support for related quirks. pci, acpi: Support for ACPI based generic PCI host controller init pci, acpi: Match PCI config space accessors against platfrom specific quirks. arm64, pci, acpi: Start using ACPI based PCI host bridge driver for ARM64. arch/arm64/Kconfig | 7 ++ arch/arm64/kernel/pci.c | 25 ---- arch/ia64/hp/common/sba_iommu.c | 2 +- arch/ia64/include/asm/pci.h | 1 - arch/ia64/pci/pci.c | 52 +++----- arch/ia64/sn/kernel/io_acpi_init.c | 4 +- arch/x86/Kconfig | 4 + arch/x86/include/asm/pci.h | 3 - arch/x86/include/asm/pci_x86.h | 28 +---- arch/x86/pci/acpi.c | 41 ++---- arch/x86/pci/common.c | 10 -- arch/x86/pci/irq.c | 10 -- arch/x86/pci/mmconfig-shared.c | 250 ++++++------------------------------- arch/x86/pci/mmconfig_32.c | 11 +- arch/x86/pci/mmconfig_64.c | 67 +--------- arch/x86/pci/numachip.c | 1 + drivers/acpi/Kconfig | 5 + drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 201 +++++++++++++++++++++++++++++ drivers/acpi/pci_root.c | 136 +++++++++++++++++++- drivers/acpi/resource.c | 12 +- drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 234 ++++++++++++++++++++++++++++++++++ drivers/pci/pci.c | 29 ++++- drivers/pci/probe.c | 5 + drivers/xen/pci.c | 7 +- include/acpi/acpi_bus.h | 1 + include/asm-generic/vmlinux.lds.h | 7 ++ include/linux/acpi.h | 2 + include/linux/ecam.h | 62 +++++++++ include/linux/pci-acpi.h | 17 +++ 32 files changed, 802 insertions(+), 448 deletions(-) create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 6 months

12
78
0 0

leg-kernel tag leg-20160201.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-201600201.0 This is based on mainline kernel v4.4 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/adca6ee4e1e1581ff1612e… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - topic-pci [topic-pci-20160122.0] - topic-numa [topic-numa-20160122.0] - topic-amba-probing [topic-amba-probing-20160122.0] - topic-acpi-console [topic-acpi-console-20160201.0] - topic-gtdt-wakeup-timer [topic-gtdt-wakeup-timer-20160201.0] - topic-fvp [topic-fvp-20160122.0] - topic-kvm-acpi [topic-kvm-acpi-20160122.0] - topic-sbsa-watchdog [topic-acpi-watchdog-20160122.0] - topic-apei [topic-apei-20160122.0] http://git.linaro.org/leg/acpi/leg-kernel.git - leg-configs [leg-configs-20160122.0] NOTES:-

9 years, 6 months

1
0
0 0

topic-pci branch on Mustang

by Itaru Kitayama

Hi, Has anyone successfully brought up the topic-pci branch kernel with acpi=force on Mustang? The boot is stalled in the middle of it. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.0-rc1+ (itaru.kitayama(a)localhost.localdomain) (gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC) ) #1 SMP Sun Jan 24 19:22:32 CST 2016 [ 0.000000] Boot CPU: AArch64 Processor [500f0001] [ 0.000000] earlycon: Early serial console at MMIO32 0x1c020000 (options '') [ 0.000000] bootconsole [uart0] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] EFI v2.40 by X-Gene Mustang Board EFI Nov 24 2015 13:22:41 [ 0.000000] efi: ACPI=0x47fa869000 ACPI 2.0=0x47fa869014 SMBIOS 3.0=0x47fa867000 [ 0.000000] cma: Reserved 512 MiB at 0x00000040e0000000 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000047FA869014 000024 (v02 APM ) [ 0.000000] ACPI: XSDT 0x00000047FA8680E8 00006C (v01 APM XGENE 00000003 01000013) [ 0.000000] ACPI: FACP 0x00000047FA85F000 00010C (v05 APM XGENE 00000003 INTL 20140724) [ 0.000000] ACPI: DSDT 0x00000047FA860000 00495F (v05 APM APM88xxx 00000001 INTL 20140724) [ 0.000000] ACPI: DBG2 0x00000047FA865000 0000AA (v00 APMC0D XGENEDBG 00000000 INTL 20140724) [ 0.000000] ACPI: GTDT 0x00000047FA85D000 0000E0 (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: MCFG 0x00000047FA85C000 00003C (v01 APM XGENE 00000002 INTL 20140724) [ 0.000000] ACPI: SPCR 0x00000047FA85B000 000050 (v02 APMC0D XGENESPC 00000000 INTL 20140724) [ 0.000000] ACPI: SSDT 0x00000047FA85A000 00002D (v02 APM XGENE 00000001 INTL 20140724) [ 0.000000] ACPI: APIC 0x00000047FA859000 0002A4 (v03 APM XGENE 00000003 01000013) [ 0.000000] ACPI: SSDT 0x00000047FA858000 000078 (v02 REDHAT MACADDRS 00000001 01000013) [ 0.000000] ACPI: SSDT 0x00000047FA857000 000032 (v02 REDHAT UARTCLKS 00000001 01000013) [ 0.000000] psci: is not implemented in ACPI. [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] Unsupported ACPI enable-method [ 0.000000] PERCPU: Embedded 2 pages/cpu @fffffe07fff90000 s90496 r8192 d32384 u131072 [ 0.000000] Detected PIPT I-cache on CPU0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 523776 [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-rc1+ root=UUID=0e305934-49d5-4f66-b10b-23ec6029fab9 ro acpi=force earlycon=uart8250,mmio32,0x1c020000 console=ttyS0,115200 [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 4194304 (order: 9, 33554432 bytes) [ 0.000000] Inode-cache hash table entries: 2097152 (order: 8, 16777216 bytes) [ 0.000000] software IO TLB [mem 0x40dbff0000-0x40dfff0000] (64MB) mapped at [fffffe00dbff0000-fffffe00dffeffff] [ 0.000000] Memory: 32851584K/33554432K available (7946K kernel code, 1243K rwdata, 5056K rodata, 832K init, 1460K bss, 178560K reserved, 524288K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vmalloc : 0xfffffc0000000000 - 0xfffffdfedfff0000 ( 2043 GB) [ 0.000000] vmemmap : 0xfffffdfee0000000 - 0xfffffdffe0000000 ( 4 GB maximum) [ 0.000000] 0xfffffdfef0000000 - 0xfffffdfef2000000 ( 32 MB actual) [ 0.000000] fixed : 0xfffffdfffa7d0000 - 0xfffffdfffac00000 ( 4288 KB) [ 0.000000] PCI I/O : 0xfffffdfffae00000 - 0xfffffdfffbe00000 ( 16 MB) [ 0.000000] modules : 0xfffffdfffc000000 - 0xfffffe0000000000 ( 64 MB) [ 0.000000] memory : 0xfffffe0000000000 - 0xfffffe0800000000 ( 32768 MB) [ 0.000000] .init : 0xfffffe0000d50000 - 0xfffffe0000e20000 ( 832 KB) [ 0.000000] .text : 0xfffffe0000080000 - 0xfffffe0000d42bf4 ( 13067 KB) [ 0.000000] .data : 0xfffffe0000e30000 - 0xfffffe0000f66c00 ( 1243 KB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=1 [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] Architected cp15 timer(s) running at 50.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns [ 0.000002] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns [ 0.008541] Console: colour dummy device 80x25 [ 0.013235] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=200000) [ 0.024283] pid_max: default: 32768 minimum: 301 [ 0.029180] ACPI: Core revision 20150930 [ 0.040671] ACPI: 4 ACPI AML tables successfully acquired and loaded [ 0.047439] Security Framework initialized [ 0.051756] Yama: becoming mindful. [ 0.055437] SELinux: Initializing. [ 0.059198] Mount-cache hash table entries: 65536 (order: 3, 524288 bytes) [ 0.066486] Mountpoint-cache hash table entries: 65536 (order: 3, 524288 bytes) [ 0.074654] Initializing cgroup subsys io [ 0.078888] Initializing cgroup subsys memory [ 0.083485] Initializing cgroup subsys devices [ 0.088190] Initializing cgroup subsys freezer [ 0.092885] Initializing cgroup subsys net_cls [ 0.097589] Initializing cgroup subsys perf_event [ 0.102552] Initializing cgroup subsys net_prio [ 0.107366] ftrace: allocating 27761 entries in 7 pages [ 0.132043] Remapping and enabling EFI services. [ 0.136940] EFI remap 0x0000000010510000 => 0000000040000000 [ 0.143127] EFI remap 0x0000000010548000 => 0000000040018000 [ 0.149290] EFI remap 0x0000000017000000 => 0000000040020000 [ 0.155453] EFI remap 0x000000001c025000 => 0000000040035000 [ 0.161616] EFI remap 0x000000007c0c0000 => 0000000040040000 [ 0.167779] EFI remap 0x000000007c1c0000 => 0000000040050000 [ 0.173942] EFI remap 0x000000007c2c0000 => 0000000040060000 [ 0.180104] EFI remap 0x000000007c3c0000 => 0000000040070000 [ 0.186266] EFI remap 0x000000007c4c0000 => 0000000040080000 [ 0.192438] EFI remap 0x000000007c5c0000 => 0000000040090000 [ 0.198600] EFI remap 0x000000007c6c0000 => 00000000400a0000 [ 0.204781] EFI remap 0x000000007c7c0000 => 00000000400b0000 [ 0.210961] EFI remap 0x00000047fa856000 => 00000000400c6000 [ 0.217141] EFI remap 0x00000047fa86a000 => 00000000400da000 [ 0.223314] EFI remap 0x00000047ffa12000 => 00000000402c2000 [ 0.229477] EFI remap 0x00000047ffa26000 => 00000000402d6000 [ 0.235646] ASID allocator initialised with 65536 entries [ 0.241999] Brought up 1 CPUs [ 0.245123] SMP: Total of 1 processors activated. [ 0.250087] CPU: All CPU(s) started at EL2 [ 0.254729] devtmpfs: initialized [ 0.258522] SMBIOS 3.0.0 present. [ 0.262069] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.272746] atomic64_test: passed [ 0.276444] NET: Registered protocol family 16 [ 0.281343] PCCT header not found. [ 0.284973] vdso: 2 pages (1 code @ fffffe0000e50000, 1 data @ fffffe0000e40000) [ 0.292807] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [ 0.300274] DMA: preallocated 256 KiB pool for atomic allocations [ 0.306735] ACPI: bus type PCI registered [ 0.310955] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.317819] Serial: AMBA PL011 UART driver [ 0.324731] ACPI: Added _OSI(Module Device) [ 0.329151] ACPI: Added _OSI(Processor Device) [ 0.333845] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.338825] ACPI: Added _OSI(Processor Aggregator Device) [ 0.354649] ACPI: Interpreter enabled [ 0.358516] ACPI: Using GIC for interrupt routing [ 0.366406] ACPI: Power Resource [SCVR] (off) [ 0.379267] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.385823] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.394877] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.403349] acpi PNP0A08:00: Bus 0000:00 not present in PCI namespace [ 0.410745] vgaarb: loaded [ 0.413725] SCSI subsystem initialized [ 0.417770] ACPI: bus type USB registered [ 0.422021] usbcore: registered new interface driver usbfs [ 0.427843] usbcore: registered new interface driver hub [ 0.433491] usbcore: registered new device driver usb [ 0.439181] NetLabel: Initializing [ 0.442753] NetLabel: domain hash size = 128 [ 0.447352] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.452606] NetLabel: unlabeled traffic allowed by default [ 0.458590] clocksource: Switched to clocksource arch_sys_counter [ 0.481347] pnp: PnP ACPI init [ 0.485318] pnp: PnP ACPI: found 0 devices [ 0.492409] NET: Registered protocol family 2 [ 0.497199] TCP established hash table entries: 262144 (order: 5, 2097152 bytes) [ 0.505681] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes) [ 0.513141] TCP: Hash tables configured (established 262144 bind 65536) [ 0.520153] UDP hash table entries: 16384 (order: 3, 524288 bytes) [ 0.526945] UDP-Lite hash table entries: 16384 (order: 3, 524288 bytes) [ 0.534305] NET: Registered protocol family 1 [ 0.539050] RPC: Registered named UNIX socket transport module. [ 0.545309] RPC: Registered udp transport module. [ 0.550288] RPC: Registered tcp transport module. [ 0.555267] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.562172] Unpacking initramfs... [ 0.801177] Freeing initrd memory: 10368K (fffffe07f8bf0000 - fffffe07f9610000) [ 0.809067] kvm [1]: error: no compatible GIC node found [ 0.814743] kvm [1]: error initializing Hyp mode: -19 [ 0.820381] futex hash table entries: 256 (order: -1, 32768 bytes) [ 0.826932] audit: initializing netlink subsys (disabled) [ 0.832659] audit: type=2000 audit(0.004:1): initialized [ 0.838583] HugeTLB registered 512 MB page size, pre-allocated 0 pages [ 0.848211] zbud: loaded [ 0.851033] VFS: Disk quotas dquot_6.6.0 [ 0.855250] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 0.863482] NFS: Registering the id_resolver key type [ 0.868844] Key type id_resolver registered [ 0.873261] Key type id_legacy registered [ 0.877503] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.884797] Key type big_key registered [ 0.892586] NET: Registered protocol family 38 [ 0.897363] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 0.905217] io scheduler noop registered [ 0.909351] io scheduler deadline registered [ 0.913910] io scheduler cfq registered (default) [ 0.919094] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 0.924982] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 0.932276] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

9 years, 6 months

3
10
0 0

leg-kernel tag leg-20160122.0 released

by Graeme Gregory

The leg-kernel release has been made and tagged as leg-20160122.0 This is based on mainline kernel v4.4 Repository : http://git.linaro.org/leg/acpi/leg-kernel.git Direct Link: http://git.linaro.org/leg/acpi/leg-kernel.git/commit/adca6ee4e1e1581ff1612e… Topic Branches :- http://git.linaro.org/leg/acpi/acpi.git - topic-pci [topic-pci-20160122.0] - topic-numa [topic-numa-20160122.0] - topic-amba-probing [topic-amba-probing-20160122.0] - topic-acpi-console [topic-acpi-console-20160122.0] - topic-gtdt-wakeup-timer [topic-gtdt-wakeup-timer-20160122.0] - topic-fvp [topic-fvp-20160122.0] - topic-kvm-acpi [topic-kvm-acpi-20160122.0] - topic-sbsa-watchdog [topic-acpi-watchdog-20160122.0] - topic-apei [topic-apei-20160122.0] http://git.linaro.org/leg/acpi/leg-kernel.git - leg-configs [leg-configs-20160122.0] NOTES:-

9 years, 6 months

1
0
0 0

[PATCH 0/5] Update ACPI RSDP tests to be specification compliant

by Al Stone

Add in several tests that extend the testing done on the RSDP. If these tests are all passed, the RSDP being examined should be compliant with the ACPI 6.0 spec. As part of that, when creating a dummy RSDP to substitute for one that cannot be read or found, use either RsdtAddress or XsdtAddress as described in the spec. For non-arm64, either can be used, but for arm64, only the XsdtAddress is to be used. Finally, update the regression tests for RSDP. Al Stone (5): RSDP: minor cleanups to rsdp.c for checkpatch issues utilities: add a helper function for printing out architecture names ACPI tables: when bodging up an RSDP, do the right thing for the arch ACPI RSDP: flesh out the tests to check for full spec compliance. Update regression test rsdp-0001/test-0001.sh fwts-test/rsdp-0001/rsdp.log | 16 ++++- src/acpi/rsdp/rsdp.c | 139 ++++++++++++++++++++++++++++++++++++----- src/lib/include/fwts_arch.h | 1 + src/lib/src/fwts_acpi_tables.c | 19 +++--- src/lib/src/fwts_arch.c | 18 ++++++ 5 files changed, 169 insertions(+), 24 deletions(-) -- 2.5.0

9 years, 6 months

1
5
0 0

[PATCH 0/7] Update several regression tests

by Al Stone

I should have added these earlier, but I did not. So, here they are: the updates to the regression tests affected by adding the --arch parameter, and by updating the MADT tests. Al Stone (7): Update the regression test arg-help-0001/test-0001.sh Update regression test for arg-help-0001/test-0002.sh Update regression test for arg-show-tests-0001/test-0001.sh Update regression test arg-show-tests-full-0001/test-0001.sh Update the regression test arg-table-path-0001/test-0001.sh Update the regression test madt-0001/test-0001.sh Update the regression test madt-0001/test-0002.sh fwts-test/arg-help-0001/arg-help-0001.log | 4 + fwts-test/arg-help-0001/arg-help-0002.log | 4 + .../arg-show-tests-0001/arg-show-tests-0001.log | 8 +- .../arg-show-tests-full-0001.log | 26 +- fwts-test/arg-table-path-0001/acpidump-0001.log | 741 +++++++++------------ fwts-test/madt-0001/madt-0001.log | 10 +- fwts-test/madt-0001/madt-0002.log | 33 +- 7 files changed, 344 insertions(+), 482 deletions(-) -- 2.5.0

9 years, 6 months

1
7
0 0

[PATCH v3 0/6] ACPI compliance testing for MADT and its subtables

by Al Stone

This patch series adds in specific ACPI compliance testing for the MADT and all of its various subtables (16, currently). The first three patches add in the idea of host and target architectures -- host being the arch that FWTS is running on, and target the arch whose firmware is being tested. This is needed later in the MADT tests since what is proper changes based on the architecture the firmware supports. The fourth patch adds the detailed tests for the MADT and all but one of the subtables currently defined in ACPI 6.0. The last two patches add in the relatively new GIC ITS subtable and compliance tests for it. There are still multiple TODOs in the compliance checks; these will be added as clarification of the spec becomes available. Changes for v3: -- Add in support for the --arch=<name> parameter to specify the arch for the target firmware (default is that host == target). -- Add in the fwts_architecture typedef plus some helper functions so that tests in the future can adapt their behavior as needed, and so that the MADT tests can set themselves up properly. -- Instead of creating a new sourc file src/acpi/compliance/madt.c, replace the existing src/acpi/madt/madt.c tests since we're providing a superset. -- Various minor style and syntax corrections (from Ian Colin King) Changes for v2: -- Clean up the white space problems -- Fix errors found by checkpatch (minor syntax things) -- Fix one logic error: while MADT and FADT table revisions *should* be in sync, they seldom are, so report this as a test failure and continue to test as much as possible instead of aborting completely, in some of those cases. Al Stone (6): Start defining FWTS architectures as variables Define some utility functions for using the fwts_architecture enum Add mechanism to tell FWTS what architecture is being tested ACPI: MADT: add in compliance tests for the MADT and subtables ACPI: Add in MADT subtable description for GIC ITS subtable ACPI: MADT: add in compliance checks for the GIC ITS subtable src/acpi/madt/madt.c | 1551 +++++++++++++++++++++++++++++++------- src/lib/include/fwts.h | 1 + src/lib/include/fwts_acpi.h | 10 + src/lib/include/fwts_arch.h | 41 + src/lib/include/fwts_framework.h | 3 + src/lib/src/Makefile.am | 1 + src/lib/src/fwts_arch.c | 88 +++ src/lib/src/fwts_framework.c | 25 + 8 files changed, 1460 insertions(+), 260 deletions(-) create mode 100644 src/lib/include/fwts_arch.h create mode 100644 src/lib/src/fwts_arch.c -- 2.5.0

9 years, 6 months

2
10
0 0

[PATCH 0/4] acpi: cppc optimization patches

by Prashanth Prakash

This series introduces changes to reduce the time required to send a frequency transition requests to the platform while using the cppc-cpufreq driver. With these changes we see significant improvement in the average time to send freq. transition request to the platform. Profiling on an ARM platform showed that the average transaction time per request reduced from 200us to under 20us. Ashwin Chaugule (1): ACPI / CPPC: Optimize PCC Read Write operations Prashanth Prakash (3): acpi: cppc: optimized cpc_read and cpc_write mailbox: pcc: optimized pcc_send_data acpi: cppc: replace writeX/readX to PCC with relaxed version drivers/acpi/cppc_acpi.c | 184 +++++++++++++++++++++++++++++++++++------------ drivers/mailbox/pcc.c | 110 ++++++++++++++++++++++++++-- 2 files changed, 241 insertions(+), 53 deletions(-) -- Qualcomm Technologies, Inc. on behalf of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

9 years, 6 months

4
9
0 0

[PATCH 0/2] fwts man page updates

by Al Stone

Update the fwts man page to include some new parameters. Al Stone (2): Documentation: add --acpicompliance to man page Documentation: add --arch to the man page doc/fwts.1 | 11 +++++++++++ 1 file changed, 11 insertions(+) -- 2.5.0

9 years, 6 months

1
2
0 0

[PATCH v5] acpi, apei: add Boot Error Record Table (BERT) support

by fu.wei＠linaro.org

From: Huang Ying <ying.huang(a)intel.com> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. Under normal circumstances, when a hardware error occurs, kernel will be notified via NMI, MCE or some other method, then kernel will process the error condition, report it, and recover it if possible. But sometime, the situation is so bad, so that firmware may choose to reset directly without notifying Linux kernel. Linux kernel can use the Boot Error Record Table (BERT) to get the un-notified hardware errors that occurred in a previous boot. In this patch, the error information is reported via printk. For more information about BERT, please refer to ACPI Specification version 6.0, section 18.3.1: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf The following log is a BERT record after system reboot because of hitting a fatal memory error: BERT: Error records from previous boot: [Hardware Error]: It has been corrected by h/w and requires no further action [Hardware Error]: event severity: corrected [Hardware Error]: Error 0, type: recoverable [Hardware Error]: section_type: memory error [Hardware Error]: error_status: 0x0000000000000400 [Hardware Error]: physical_address: 0xffffffffffffffff [Hardware Error]: card: 1 module: 2 bank: 3 row: 1 column: 2 bit_position: 5 [Hardware Error]: error_type: 2, single-bit ECC [Tomasz Nowicki: Clear error status at the end of error handling] [Tony: Applied some cleanups suggested by Fu Wei] [Fu Wei: delete EXPORT_SYMBOL_GPL(bert_disable), improve the code] Signed-off-by: Huang Ying <ying.huang(a)intel.com> Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Signed-off-by: Chen, Gong <gong.chen(a)linux.intel.com> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Tony Luck <tony.luck(a)intel.com> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v5: Drop some superfluous comments. Use the introduce of BERT in ACPI Specification instead of original one at the head of bert.c. Fix typo in apei-internal.h Simplify the introduce of bert_disable. v4: https://lkml.org/lkml/2016/1/8/382 Fix the "#undef" bug Improve the instruction of "bert_disable", Delete the useless declaration in include/acpi/apei.h. v3: https://lkml.org/lkml/2016/1/7/214 Merge the two patches Do some improvements according to Borislav's suggestion. v2: https://lkml.org/lkml/2015/8/18/336 Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Documentation/kernel-parameters.txt | 3 + drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/apei-internal.h | 2 +- drivers/acpi/apei/bert.c | 150 ++++++++++++++++++++++++++++++++++++ 4 files changed, 155 insertions(+), 2 deletions(-) diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 3ea869d..acb772e 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -564,6 +564,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted. bootmem_debug [KNL] Enable bootmem allocator debug messages. + bert_disable [ACPI] + Disable BERT OS support on buggy BIOSes. + bttv.card= [HW,V4L] bttv (bt848 + bt878 based grabber cards) bttv.radio= Most important insmod options are available as kernel args too. diff --git a/drivers/acpi/apei/Makefile b/drivers/acpi/apei/Makefile index 5d575a9..e50573d 100644 --- a/drivers/acpi/apei/Makefile +++ b/drivers/acpi/apei/Makefile @@ -3,4 +3,4 @@ obj-$(CONFIG_ACPI_APEI_GHES) += ghes.o obj-$(CONFIG_ACPI_APEI_EINJ) += einj.o obj-$(CONFIG_ACPI_APEI_ERST_DEBUG) += erst-dbg.o -apei-y := apei-base.o hest.o erst.o +apei-y := apei-base.o hest.o erst.o bert.o diff --git a/drivers/acpi/apei/apei-internal.h b/drivers/acpi/apei/apei-internal.h index 16129c7..6e9f14c 100644 --- a/drivers/acpi/apei/apei-internal.h +++ b/drivers/acpi/apei/apei-internal.h @@ -1,6 +1,6 @@ /* * apei-internal.h - ACPI Platform Error Interface internal - * definations. + * definitions. */ #ifndef APEI_INTERNAL_H diff --git a/drivers/acpi/apei/bert.c b/drivers/acpi/apei/bert.c new file mode 100644 index 0000000..a05b5c0 --- /dev/null +++ b/drivers/acpi/apei/bert.c @@ -0,0 +1,150 @@ +/* + * APEI Boot Error Record Table (BERT) support + * + * Copyright 2011 Intel Corp. + * Author: Huang Ying <ying.huang(a)intel.com> + * + * Under normal circumstances, when a hardware error occurs, the error + * handler receives control and processes the error. This gives OSPM a + * chance to process the error condition, report it, and optionally attempt + * recovery. In some cases, the system is unable to process an error. + * For example, system firmware or a management controller may choose to + * reset the system or the system might experience an uncontrolled crash + * or reset.The boot error source is used to report unhandled errors that + * occurred in a previous boot. This mechanism is described in the BERT + * table. + * + * For more information about BERT, please refer to ACPI Specification + * version 4.0, section 17.3.1 + * + * This file is licensed under GPLv2. + * + */ + +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/init.h> +#include <linux/acpi.h> +#include <linux/io.h> + +#include "apei-internal.h" + +#undef pr_fmt +#define pr_fmt(fmt) "BERT: " fmt + +static int bert_disable; + +static void __init bert_print_all(struct acpi_bert_region *region, + unsigned int region_len) +{ + struct acpi_hest_generic_status *estatus = + (struct acpi_hest_generic_status *)region; + int remain = region_len; + u32 estatus_len; + + if (!estatus->block_status) + return; + + while (remain > sizeof(struct acpi_bert_region)) { + if (cper_estatus_check(estatus)) { + pr_err(FW_BUG "Invalid error record.\n"); + return; + } + + estatus_len = cper_estatus_len(estatus); + if (remain < estatus_len) { + pr_err(FW_BUG "Truncated status block (length: %u).\n", + estatus_len); + return; + } + + pr_info_once("Error records from previous boot:\n"); + + cper_estatus_print(KERN_INFO HW_ERR, estatus); + + /* + * Because the boot error source is "one-time polled" type, + * clear Block Status of current Generic Error Status Block, + * once it's printed. + */ + estatus->block_status = 0; + + estatus = (void *)estatus + estatus_len; + /* No more error records. */ + if (!estatus->block_status) + return; + + remain -= estatus_len; + } +} + +static int __init setup_bert_disable(char *str) +{ + bert_disable = 1; + + return 0; +} +__setup("bert_disable", setup_bert_disable); + +static int __init bert_check_table(struct acpi_table_bert *bert_tab) +{ + if (bert_tab->header.length < sizeof(struct acpi_table_bert) || + bert_tab->region_length < sizeof(struct acpi_bert_region)) + return -EINVAL; + + return 0; +} + +static int __init bert_init(void) +{ + struct acpi_bert_region *boot_error_region; + struct acpi_table_bert *bert_tab; + unsigned int region_len; + acpi_status status; + int rc = 0; + + if (acpi_disabled) + return 0; + + if (bert_disable) { + pr_info("Boot Error Record Table support is disabled.\n"); + return 0; + } + + status = acpi_get_table(ACPI_SIG_BERT, 0, (struct acpi_table_header **)&bert_tab); + if (status == AE_NOT_FOUND) + return 0; + + if (ACPI_FAILURE(status)) { + pr_err("get table failed, %s.\n", acpi_format_exception(status)); + return -EINVAL; + } + + rc = bert_check_table(bert_tab); + if (rc) { + pr_err(FW_BUG "table invalid.\n"); + return rc; + } + + region_len = bert_tab->region_length; + if (!request_mem_region(bert_tab->address, region_len, "APEI BERT")) { + pr_err("Can't request iomem region <%016llx-%016llx>.\n", + (unsigned long long)bert_tab->address, + (unsigned long long)bert_tab->address + region_len - 1); + return -EIO; + } + + boot_error_region = ioremap_cache(bert_tab->address, region_len); + if (boot_error_region) { + bert_print_all(boot_error_region, region_len); + iounmap(boot_error_region); + } else { + rc = -ENOMEM; + } + + release_mem_region(bert_tab->address, region_len); + + return rc; +} + +late_initcall(bert_init); -- 2.5.0

9 years, 6 months

3
3
0 0

[PATCH v4] acpi, apei: add Boot Error Record Table (BERT) support

by fu.wei＠linaro.org

From: Huang Ying <ying.huang(a)intel.com> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. Under normal circumstances, when a hardware error occurs, kernel will be notified via NMI, MCE or some other method, then kernel will process the error condition, report it, and recover it if possible. But sometime, the situation is so bad, so that firmware may choose to reset directly without notifying Linux kernel. Linux kernel can use the Boot Error Record Table (BERT) to get the un-notified hardware errors that occurred in a previous boot. In this patch, the error information is reported via printk. For more information about BERT, please refer to ACPI Specification version 6.0, section 18.3.1: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf The following log is a BERT record after system reboot because of hitting a fatal memory error: BERT: Error records from previous boot: [Hardware Error]: It has been corrected by h/w and requires no further action [Hardware Error]: event severity: corrected [Hardware Error]: Error 0, type: recoverable [Hardware Error]: section_type: memory error [Hardware Error]: error_status: 0x0000000000000400 [Hardware Error]: physical_address: 0xffffffffffffffff [Hardware Error]: card: 1 module: 2 bank: 3 row: 1 column: 2 bit_position: 5 [Hardware Error]: error_type: 2, single-bit ECC [Tomasz Nowicki: Clear error status at the end of error handling] [Tony: Applied some cleanups suggested by Fu Wei] [Fu Wei: delete EXPORT_SYMBOL_GPL(bert_disable), improve the code] Signed-off-by: Huang Ying <ying.huang(a)intel.com> Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Signed-off-by: Chen, Gong <gong.chen(a)linux.intel.com> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Tony Luck <tony.luck(a)intel.com> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v4: fix the "#undef" bug Improve the instruction of "bert_disable", delete the useless declaration in include/acpi/apei.h. v3: https://lkml.org/lkml/2016/1/7/214 Merge the two patches Do some improvements according to Borislav's suggestion. v2: https://lkml.org/lkml/2015/8/18/336 Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Documentation/kernel-parameters.txt | 6 ++ drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/bert.c | 158 ++++++++++++++++++++++++++++++++++++ include/acpi/apei.h | 1 + 4 files changed, 166 insertions(+), 1 deletion(-) create mode 100644 drivers/acpi/apei/bert.c diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 742f69d..2c527a9 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -555,6 +555,12 @@ bytes respectively. Such letter suffixes can also be entirely omitted. bootmem_debug [KNL] Enable bootmem allocator debug messages. + bert_disable [ACPI] + Disable Boot Error Record Table (BERT) support. + Use this if to workaround buggy firmware which produces + the malformed BERT table or incorrect error status + block. + bttv.card= [HW,V4L] bttv (bt848 + bt878 based grabber cards) bttv.radio= Most important insmod options are available as kernel args too. diff --git a/drivers/acpi/apei/Makefile b/drivers/acpi/apei/Makefile index 5d575a9..e50573d 100644 --- a/drivers/acpi/apei/Makefile +++ b/drivers/acpi/apei/Makefile @@ -3,4 +3,4 @@ obj-$(CONFIG_ACPI_APEI_GHES) += ghes.o obj-$(CONFIG_ACPI_APEI_EINJ) += einj.o obj-$(CONFIG_ACPI_APEI_ERST_DEBUG) += erst-dbg.o -apei-y := apei-base.o hest.o erst.o +apei-y := apei-base.o hest.o erst.o bert.o diff --git a/drivers/acpi/apei/bert.c b/drivers/acpi/apei/bert.c new file mode 100644 index 0000000..ffcbf4b --- /dev/null +++ b/drivers/acpi/apei/bert.c @@ -0,0 +1,158 @@ +/* + * APEI Boot Error Record Table (BERT) support + * + * Copyright 2011 Intel Corp. + * Author: Huang Ying <ying.huang(a)intel.com> + * + * Under normal circumstances, when a hardware error occurs, kernel + * will be notified via NMI, MCE or some other method, then kernel + * will process the error condition, report it, and recover it if + * possible. But sometime, the situation is so bad, so that firmware + * may choose to reset directly without notifying Linux kernel. + * + * Linux kernel can use the Boot Error Record Table (BERT) to get the + * un-notified hardware errors that occurred in a previous boot. + * + * For more information about BERT, please refer to ACPI Specification + * version 4.0, section 17.3.1 + * + * This file is licensed under GPLv2. + * + */ + +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/init.h> +#include <linux/acpi.h> +#include <linux/io.h> + +#include "apei-internal.h" + +#undef pr_fmt +#define pr_fmt(fmt) "BERT: " fmt + +static int bert_disable; + +static void __init bert_print_all(struct acpi_bert_region *region, + unsigned int region_len) +{ + /* + * We use cper_estatus_* which uses struct acpi_hest_generic_status, + * struct acpi_hest_generic_status and acpi_bert_region are the same + * (Generic Error Status Block), so we declare the "estatus" here. + */ + struct acpi_hest_generic_status *estatus = + (struct acpi_hest_generic_status *)region; + int remain = region_len; + u32 estatus_len; + + /* The records have been polled*/ + if (!estatus->block_status) + return; + + while (remain > sizeof(struct acpi_bert_region)) { + /* + * Test Generic Error Status Block first, + * if the data(Offset, Length) is invalid, we just return, + * because we can't trust the length data from this block. + */ + if (cper_estatus_check(estatus)) { + pr_err(FW_BUG "Invalid error record\n"); + return; + } + + estatus_len = cper_estatus_len(estatus); + if (remain < estatus_len) { + pr_err(FW_BUG "Invalid status block length (%u)\n", + estatus_len); + return; + } + + pr_info_once("Error records from previous boot:\n"); + + cper_estatus_print(KERN_INFO HW_ERR, estatus); + + /* + * Because the boot error source is "one-time polled" type, + * clear Block Status of current Generic Error Status Block, + * once it's printed. + */ + estatus->block_status = 0; + + estatus = (void *)estatus + estatus_len; + if (!estatus->block_status) + return; /* No more error records */ + + remain -= estatus_len; + } +} + +static int __init setup_bert_disable(char *str) +{ + bert_disable = 1; + + return 0; +} +__setup("bert_disable", setup_bert_disable); + +static int __init bert_check_table(struct acpi_table_bert *bert_tab) +{ + if (bert_tab->header.length < sizeof(struct acpi_table_bert) || + bert_tab->region_length < sizeof(struct acpi_bert_region)) + return -EINVAL; + + return 0; +} + +static int __init bert_init(void) +{ + struct acpi_bert_region *boot_error_region; + struct acpi_table_bert *bert_tab; + unsigned int region_len; + acpi_status status; + int rc = 0; + + if (acpi_disabled) + return 0; + + if (bert_disable) { + pr_info("Boot Error Record Table support is disabled\n"); + return 0; + } + + status = acpi_get_table(ACPI_SIG_BERT, 0, (struct acpi_table_header **)&bert_tab); + if (status == AE_NOT_FOUND) + return 0; + if (ACPI_FAILURE(status)) { + pr_err("get table failed, %s\n", acpi_format_exception(status)); + return -EINVAL; + } + + rc = bert_check_table(bert_tab); + if (rc) { + pr_err(FW_BUG "table invalid\n"); + return rc; + } + + region_len = bert_tab->region_length; + if (!request_mem_region(bert_tab->address, region_len, "APEI BERT")) { + pr_err("Can't request iomem region <%016llx-%016llx>\n", + (unsigned long long)bert_tab->address, + (unsigned long long)bert_tab->address + region_len - 1); + return -EIO; + } + + boot_error_region = ioremap_cache(bert_tab->address, region_len); + if (boot_error_region) { + bert_print_all(boot_error_region, region_len); + iounmap(boot_error_region); + } else { + rc = -ENOMEM; + } + + release_mem_region(bert_tab->address, region_len); + + return rc; +} + +late_initcall(bert_init); -- 2.5.0

9 years, 6 months

4
7
0 0

[PATCH V2 00/23] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

by Tomasz Nowicki

>From the functionality point of view this series might be split into the following logic parts: 1. Make MMCONFIG code arch-agnostic which allows all architectures to collect PCI config regions and used when necessary. 2. Move non-arch specific bits to the core code. 3. Use MMCONFIG code and implement generic ACPI based PCI host controller driver. 4. Enable above driver on ARM64 Patches has been built on top of 4.4-rc4 and can be found here: git@github.com:semihalf-nowicki-tomasz/linux.git (pci-acpi-v2) NOTE, this patch set depends on Matthew's patches: http://www.spinics.net/lists/linux-pci/msg45950.html https://github.com/Vality/linux/tree/pci-fixes This has been tested on Cavium ThunderX 1 socket server and QEMU. Any help in reviewing and testing is very appreciated. v1 -> v2 - moved non-arch specific piece of code to dirver/acpi/ directory - fixed IO resource handling - introduced PCI config accessors quirks matching - moved ACPI_COMPANION_SET to generic code Liu Jiang (1): ACPI, PCI: Refine the way to handle translation_offset for ACPI resources Tomasz Nowicki (22): x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y pci, acpi, mcfg: Provide default RAW ACPI PCI config space accessors. arm64, acpi: Use empty PCI config space accessors from mcfg.c file. pci, acpi, ecam: Add flag to indicate whether ECAM region was hot added or not. x86, pci: Cleanup platform specific MCFG data using previously added ECAM hot_added flag. arm64, pci: Remove useless boot time IRQ assignment when booting with DT. pci, acpi: Move ACPI host bridge device companion assignment to core code. x86, ia64, pci: Remove ACPI companion device from platform specific data. pci, acpi: Provide generic way to assign bus domain number. x86, ia64, pci: Convert arches to use PCI_DOMAINS_GENERIC. x86, ia64: Include acpi_pci_{add|remove}_bus to the default pcibios_{add|remove}_bus implementation. acpi, mcfg: Implement two calls that might be used to inject/remove MCFG region. x86, acpi, pci: Use equivalent function introduced in previous patch. acpi, mcfg: Add default PCI config accessors implementation and initial support for related quirks. pci, acpi: Support for ACPI based PCI hostbridge init pci, acpi: Match PCI config space accessors against platfrom specific quirks. arm64, pci, acpi: Start using ACPI based PCI host bridge driver for ARM64. arch/arm64/Kconfig | 10 ++ arch/arm64/kernel/pci.c | 35 ------ arch/ia64/Kconfig | 3 + arch/ia64/include/asm/pci.h | 3 - arch/ia64/pci/pci.c | 53 +++----- arch/x86/Kconfig | 7 ++ arch/x86/include/asm/pci.h | 10 -- arch/x86/include/asm/pci_x86.h | 28 +---- arch/x86/pci/acpi.c | 43 ++----- arch/x86/pci/common.c | 10 -- arch/x86/pci/irq.c | 10 -- arch/x86/pci/mmconfig-shared.c | 250 ++++++-------------------------------- arch/x86/pci/mmconfig_32.c | 11 +- arch/x86/pci/mmconfig_64.c | 67 +--------- arch/x86/pci/numachip.c | 1 + drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 203 +++++++++++++++++++++++++++++++ drivers/acpi/pci_root.c | 5 +- drivers/acpi/resource.c | 12 +- drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 234 +++++++++++++++++++++++++++++++++++ drivers/pci/host/Kconfig | 6 + drivers/pci/host/Makefile | 1 + drivers/pci/host/pci-host-acpi.c | 138 +++++++++++++++++++++ drivers/pci/pci.c | 29 ++++- drivers/pci/probe.c | 5 + drivers/xen/pci.c | 7 +- include/asm-generic/vmlinux.lds.h | 7 ++ include/linux/acpi.h | 2 + include/linux/ecam.h | 61 ++++++++++ include/linux/pci-acpi.h | 17 +++ 32 files changed, 817 insertions(+), 467 deletions(-) create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 drivers/pci/host/pci-host-acpi.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 7 months

14
69
0 0

[RFC 0/5] console/acpi: add DBG2 and SPCR console configuration

by Leif Lindholm

Support for configuring bootconsole and console via the ACPI tables DBG2 (Debug Port Table 2) [1] and SPCR (Serial Port Console Redirection Table) [2], defined by Microsoft, has been discussed on and off over the years. [1] https://msdn.microsoft.com/en-us/library/windows/hardware/dn639131(v=vs.85)… [2] https://msdn.microsoft.com/en-us/library/windows/hardware/dn639132(v=vs.85)… Licensing concerns have prevented this happening in the past, but as of 10 August 2015, these tables have both been released also under OWF 1.0 (http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0) which is think is noncontroversially GPL-compatible? This set is a first attempt at implementing this. Submitting as an RFC since the SPCR handling currently depends on the console driver being initialized after subsystem initcalls. Workaround to enable testing surrounding infrastructure in 5/5, _really_ not intended to be merged. (Suggestions for acceptable ways of working around this appreciated.) For testing the DBG2 stuff with pl011, you would need: - A patch to unbreak pl011 earlycon, like http://permalink.gmane.org/gmane.linux.ports.arm.kernel/433219 - A QEMU that generates DBG2 tables, like current HEAD with the addition of http://lists.nongnu.org/archive/html/qemu-devel/2015-09/msg01719.html SPCR support is included in QEMU's ARM mach-virt since 2.4 release. DBG2 support has an Intel copyright notice added to it since my starting point was Lv Zheng's 2012 DBGP/DBG2 set (although not much of the original remains - this is quite a cut-down version). Leif Lindholm (4): arm64: move acpi/dt decision earlier in boot process of/serial: move earlycon early_param handling to serial acpi/serial: add DBG2 earlycon support HACK: serial: move pl011 initcall to device_initcall Torez Smith (1): tty/console: use SPCR table to define console arch/arm64/kernel/acpi.c | 55 +++++---- drivers/acpi/Makefile | 1 + drivers/acpi/console.c | 260 +++++++++++++++++++++++++++++++++++++++ drivers/of/fdt.c | 13 +- drivers/tty/serial/amba-pl011.c | 2 +- drivers/tty/serial/earlycon.c | 18 ++- drivers/tty/serial/serial_core.c | 14 ++- include/linux/acpi.h | 13 ++ include/linux/of_fdt.h | 1 + include/linux/serial_core.h | 9 +- 10 files changed, 337 insertions(+), 49 deletions(-) create mode 100644 drivers/acpi/console.c -- 2.1.4

9 years, 7 months

7
21
0 0

[PATCH v2 0/3] ACPI compliance testing for MADT and its subtables

by Al Stone

This patch series adds in specific ACPI compliance testing for the MADT and all of its various subtables (16, currently). The first patch adds tests for the MADT and all subtables currently defined in FWTS. The last two patches add in the relatively new GIC ITS subtable and compliance tests for it. There are still multiple TODOs in the compliance checks; these will be added as clarification of the spec becomes available. Changes for v2: -- Clean up the white space problems -- Fix errors found by checkpatch (minor syntax things) -- Fix one logic error: while MADT and FADT table revisions *should* be in sync, they seldom are, so report this as a test failure and continue to test as much as possible instead of aborting completely, in some of those cases. Al Stone (3): ACPI: MADT: add in compliance tests for the MADT and subtables ACPI: Add in MADT subtable description for GIC ITS subtable ACPI: MADT: add in compliance checks for the GIC ITS subtable src/Makefile.am | 1 + src/acpi/compliance/madt.c | 1372 +++++++++++++++++++++++++++++++++++++++++++ src/lib/include/fwts_acpi.h | 10 + 3 files changed, 1383 insertions(+) create mode 100644 src/acpi/compliance/madt.c -- 2.5.0

9 years, 7 months

1
3
0 0

[PATCH v3] acpi, apei: add Boot Error Record Table (BERT) support

by fu.wei＠linaro.org

From: Huang Ying <ying.huang(a)intel.com> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. Under normal circumstances, when a hardware error occurs, kernel will be notified via NMI, MCE or some other method, then kernel will process the error condition, report it, and recover it if possible. But sometime, the situation is so bad, so that firmware may choose to reset directly without notifying Linux kernel. Linux kernel can use the Boot Error Record Table (BERT) to get the un-notified hardware errors that occurred in a previous boot. In this patch, the error information is reported via printk. For more information about BERT, please refer to ACPI Specification version 6.0, section 18.3.1: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf The following log is a BERT record after system reboot because of hitting a fatal error. BERT: Obtained BERT iomem region <00000000fe801000-00000000fe802000> for BERT. [Hardware Error]: Error record from previous boot: [Hardware Error]: event severity: fatal [Hardware Error]: Error 0, type: fatal [Hardware Error]: section_type: memory error [Hardware Error]: physical_address: 0x00000000fe800000 [Hardware Error]: physical_address_mask: 0x0000000000000fff [Hardware Error]: card: 0 module: 1 bank: 0 device: 1 row: 1 column: 1 bit_pos [Tomasz Nowicki: Clear error status at the end of error handling] [Tony: Applied some cleanups suggested by Fu Wei] [Fu Wei: delete EXPORT_SYMBOL_GPL(bert_disable), improve the code] Signed-off-by: Huang Ying <ying.huang(a)intel.com> Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Signed-off-by: Chen, Gong <gong.chen(a)linux.intel.com> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Tony Luck <tony.luck(a)intel.com> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> Tested-by: Tyler Baicar <tbaicar(a)codeaurora.org> --- Changelog: v3: Merge the two patches Do some improvements according to Borislav's suggestion. v2: https://lkml.org/lkml/2015/8/18/336 Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Documentation/kernel-parameters.txt | 3 + drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/bert.c | 158 ++++++++++++++++++++++++++++++++++++ include/acpi/apei.h | 1 + 4 files changed, 163 insertions(+), 1 deletion(-) create mode 100644 drivers/acpi/apei/bert.c diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 742f69d..2310e97 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -555,6 +555,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted. bootmem_debug [KNL] Enable bootmem allocator debug messages. + bert_disable [ACPI] + Disable Boot Error Record Table (BERT) support. + bttv.card= [HW,V4L] bttv (bt848 + bt878 based grabber cards) bttv.radio= Most important insmod options are available as kernel args too. diff --git a/drivers/acpi/apei/Makefile b/drivers/acpi/apei/Makefile index 5d575a9..e50573d 100644 --- a/drivers/acpi/apei/Makefile +++ b/drivers/acpi/apei/Makefile @@ -3,4 +3,4 @@ obj-$(CONFIG_ACPI_APEI_GHES) += ghes.o obj-$(CONFIG_ACPI_APEI_EINJ) += einj.o obj-$(CONFIG_ACPI_APEI_ERST_DEBUG) += erst-dbg.o -apei-y := apei-base.o hest.o erst.o +apei-y := apei-base.o hest.o erst.o bert.o diff --git a/drivers/acpi/apei/bert.c b/drivers/acpi/apei/bert.c new file mode 100644 index 0000000..6f6ae38 --- /dev/null +++ b/drivers/acpi/apei/bert.c @@ -0,0 +1,158 @@ +/* + * APEI Boot Error Record Table (BERT) support + * + * Copyright 2011 Intel Corp. + * Author: Huang Ying <ying.huang(a)intel.com> + * + * Under normal circumstances, when a hardware error occurs, kernel + * will be notified via NMI, MCE or some other method, then kernel + * will process the error condition, report it, and recover it if + * possible. But sometime, the situation is so bad, so that firmware + * may choose to reset directly without notifying Linux kernel. + * + * Linux kernel can use the Boot Error Record Table (BERT) to get the + * un-notified hardware errors that occurred in a previous boot. + * + * For more information about BERT, please refer to ACPI Specification + * version 4.0, section 17.3.1 + * + * This file is licensed under GPLv2. + * + */ + +#include <linux/kernel.h> +#include <linux/module.h> +#include <linux/init.h> +#include <linux/acpi.h> +#include <linux/io.h> + +#include "apei-internal.h" + +#undef pr_fmt(fmt) +#define pr_fmt(fmt) "BERT: " fmt + +static int bert_disable; + +static void __init bert_print_all(struct acpi_bert_region *region, + unsigned int region_len) +{ + /* + * We use cper_estatus_* which uses struct acpi_hest_generic_status, + * struct acpi_hest_generic_status and acpi_bert_region are the same + * (Generic Error Status Block), so we declare the "estatus" here. + */ + struct acpi_hest_generic_status *estatus = + (struct acpi_hest_generic_status *)region; + int remain = region_len; + u32 estatus_len; + + /* The records have been polled*/ + if (!estatus->block_status) + return; + + while (remain > sizeof(struct acpi_bert_region)) { + /* + * Test Generic Error Status Block first, + * if the data(Offset, Length) is invalid, we just return, + * because we can't trust the length data from this block. + */ + if (cper_estatus_check(estatus)) { + pr_err(FW_BUG "Invalid error record\n"); + return; + } + + estatus_len = cper_estatus_len(estatus); + if (remain < estatus_len) { + pr_err(FW_BUG "Invalid status block length (%u)\n", + estatus_len); + return; + } + + pr_info_once(HW_ERR "Error records from previous boot:\n"); + + cper_estatus_print(KERN_INFO HW_ERR, estatus); + + /* + * Because the boot error source is "one-time polled" type, + * clear Block Status of current Generic Error Status Block, + * once it's printed. + */ + estatus->block_status = 0; + + estatus = (void *)estatus + estatus_len; + if (!estatus->block_status) + return; /* No more error records */ + + remain -= estatus_len; + } +} + +static int __init setup_bert_disable(char *str) +{ + bert_disable = 1; + + return 0; +} +__setup("bert_disable", setup_bert_disable); + +static int __init bert_check_table(struct acpi_table_bert *bert_tab) +{ + if (bert_tab->header.length < sizeof(struct acpi_table_bert) || + bert_tab->region_length < sizeof(struct acpi_bert_region)) + return -EINVAL; + + return 0; +} + +static int __init bert_init(void) +{ + struct acpi_bert_region *boot_error_region; + struct acpi_table_bert *bert_tab; + unsigned int region_len; + acpi_status status; + int rc = 0; + + if (acpi_disabled) + return 0; + + if (bert_disable) { + pr_info("Boot Error Record Table support is disabled\n"); + return 0; + } + + status = acpi_get_table(ACPI_SIG_BERT, 0, (struct acpi_table_header **)&bert_tab); + if (status == AE_NOT_FOUND) + return 0; + if (ACPI_FAILURE(status)) { + pr_err("get table failed, %s\n", acpi_format_exception(status)); + return -EINVAL; + } + + rc = bert_check_table(bert_tab); + if (rc) { + pr_err(FW_BUG "table invalid\n"); + return rc; + } + + region_len = bert_tab->region_length; + if (!request_mem_region(bert_tab->address, region_len, "APEI BERT")) { + pr_err("Can't request iomem region <%016llx-%016llx>\n", + (unsigned long long)bert_tab->address, + (unsigned long long)bert_tab->address + region_len - 1); + return -EIO; + } + + boot_error_region = ioremap_cache(bert_tab->address, region_len); + if (boot_error_region) { + bert_print_all(boot_error_region, region_len); + iounmap(boot_error_region); + } else { + rc = -ENOMEM; + } + + release_mem_region(bert_tab->address, region_len); + + return rc; +} + +late_initcall(bert_init); diff --git a/include/acpi/apei.h b/include/acpi/apei.h index 76284bb..284801a 100644 --- a/include/acpi/apei.h +++ b/include/acpi/apei.h @@ -23,6 +23,7 @@ extern bool ghes_disable; #else #define ghes_disable 1 #endif +extern int bert_disable; #ifdef CONFIG_ACPI_APEI void __init acpi_hest_init(void); -- 2.5.0

9 years, 7 months

5
7
0 0

[PATCH v2 0/2] acpi, apei: add BERT support

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> ACPI/APEI is designed to verifiy/report H/W errors, like Corrected Error(CE) and Uncorrected Error(UC). It contains four tables: HEST, ERST, EINJ and BERT. The first three tables have been merged for a long time, but because of lacking BIOS support for BERT, the support for BERT is pending until now. Recently on ARM 64 platform it is has been supported. So here we come. The following log is a BERT record after system reboot because of hitting a fatal error. BERT: Obtained BERT iomem region <00000000fe801000-00000000fe802000> for BERT. [Hardware Error]: Error record from previous boot: [Hardware Error]: event severity: fatal [Hardware Error]: Error 0, type: fatal [Hardware Error]: section_type: memory error [Hardware Error]: physical_address: 0x00000000fe800000 [Hardware Error]: physical_address_mask: 0x0000000000000fff [Hardware Error]: card: 0 module: 1 bank: 0 device: 1 row: 1 column: 1 bit_pos Changelog: v2: Delete EXPORT_SYMBOL_GPL(bert_disable), because "bert_disable" is only used in bert.c for now. Do some code-style cleanups. v1: The first upstream version submitted in linux-acpi mailing list: http://www.spinics.net/lists/linux-acpi/msg57384.html Huang Ying (1): ACPI, APEI, Boot Error Record Table (BERT) support Tomasz Nowicki (1): acpi, apei, bert: Clear error status at the end of error handling Documentation/kernel-parameters.txt | 3 + drivers/acpi/apei/Makefile | 2 +- drivers/acpi/apei/bert.c | 165 ++++++++++++++++++++++++++++++++++++ include/acpi/apei.h | 1 + 4 files changed, 170 insertions(+), 1 deletion(-) create mode 100644 drivers/acpi/apei/bert.c -- 2.4.3

9 years, 7 months

4
8
0 0

[PATCH v2 0/3] ACPI, clocksource: add GTDT and ARM memory-mapped timer support

by fu.wei＠linaro.org

From: Fu Wei <fu.wei(a)linaro.org> This patchset: (1)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all kinds of timer in GTDT table of ACPI:arch timer, memory-mapped timer and SBSA Generic Watchdog timer. This driver can help to simplify all the relevant timer drivers, and separate all the ACPI GTDT knowledge from them. (2)Simplify ACPI code for arch timer in arm_arch_timer.c (3)Add memory-mapped timer support in arm_arch_timer.c The SBSA Generic Watchdog info parsing support have been tested with a upstreaming SBSA Generic Watchdog driver: https://lkml.org/lkml/2015/10/27/466 on the following platforms: (1)ARM Foundation v8 model (2)AMD Seattle platform ARM memory-mapped timer support of this patchset has been tested on the following platforms: (1)ARM Foundation v8 model Changelog: v2: Rebase to latest kernel version(4.4-rc3). Fix the bug about the config problem, use CONFIG_ACPI_GTDT instead of CONFIG_ACPI in arm_arch_timer.c v1: The first upstreaming version: https://lkml.org/lkml/2015/10/28/553 Fu Wei (3): ACPI: add GTDT table parse driver into ACPI driver clocksource: simplify ACPI code in arm_arch_timer.c clocksource: add memory-mapped timer support in arm_arch_timer.c drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 367 +++++++++++++++++++++++++++++++++++ drivers/clocksource/arm_arch_timer.c | 178 +++++++++++++---- include/clocksource/arm_arch_timer.h | 19 ++ include/linux/acpi.h | 17 ++ 6 files changed, 555 insertions(+), 36 deletions(-) create mode 100644 drivers/acpi/gtdt.c -- 2.5.0

9 years, 8 months

4
6
0 0

[PATCH V1 00/11] MMCONFIG refactoring and ARM64 PCI hostbridge init based on ACPI

by Tomasz Nowicki

>From the functionality point of view this series might be split into two logic parts: 1. Making MMCONFIG code arch-agnostic which allows all architectures to collect PCI config regions and used when necessary. 2. Using generic MMCONFIG code and introducing ACPI based PCI hostbridge initialization for ARM64 Patches has been built on top of: [Patch v7 0/7] Consolidate ACPI PCI root common code into ACPI core https://lkml.org/lkml/2015/10/14/31 Git branch can be found here: https://git.linaro.org/leg/acpi/acpi.git/shortlog/refs/heads/pci-acpi-upstr… This has been tested on Cavium ThunderX 1 socket server. Any help in reviewing and testing is very appreciated. Hanjun Guo (1): XEN / PCI: Remove the dependence on arch x86 when PCI_MMCONFIG=y Tomasz Nowicki (10): x86, pci: Reorder logic of pci_mmconfig_insert() function x86, pci, acpi: Move arch-agnostic MMCONFIG (aka ECAM) and ACPI code out of arch/x86/ directory pci, acpi, mcfg: Provide generic implementation of MCFG code initialization. x86, pci: mmconfig_{32,64}.c code refactoring - remove code duplication. x86, pci, ecam: mmconfig_64.c becomes default implementation for ECAM driver. pci, acpi, mcfg: Provide default RAW ACPI PCI config space accessors. pci, acpi, ecam: Add flag to indicate whether ECAM region was hot added or not. x86, pci: Use previously added ECAM hot_added flag to remove ECAM regions. pci, acpi: Provide generic way to assign bus domain number. arm64, pci, acpi: Support for ACPI based PCI hostbridge init arch/arm64/Kconfig | 6 + arch/arm64/kernel/pci.c | 208 ++++++++++++++++++++++++++++++++-- arch/x86/Kconfig | 4 + arch/x86/include/asm/pci_x86.h | 28 +---- arch/x86/pci/acpi.c | 17 +-- arch/x86/pci/mmconfig-shared.c | 250 +++++++---------------------------------- arch/x86/pci/mmconfig_32.c | 11 +- arch/x86/pci/mmconfig_64.c | 67 +---------- arch/x86/pci/numachip.c | 1 + drivers/acpi/Makefile | 1 + drivers/acpi/mcfg.c | 104 +++++++++++++++++ drivers/acpi/pci_root.c | 2 +- drivers/pci/Kconfig | 10 ++ drivers/pci/Makefile | 5 + drivers/pci/ecam.c | 234 ++++++++++++++++++++++++++++++++++++++ drivers/pci/pci.c | 30 ++++- drivers/xen/pci.c | 7 +- include/linux/acpi.h | 2 + include/linux/ecam.h | 44 ++++++++ 19 files changed, 691 insertions(+), 340 deletions(-) create mode 100644 drivers/acpi/mcfg.c create mode 100644 drivers/pci/ecam.c create mode 100644 include/linux/ecam.h -- 1.9.1

9 years, 8 months

15
61
0 0

Touching the initrd before paging_init

by Jon Masters

Hi Folks, Just a few notes that might be useful to someone else. I mentioned before that we'll want to see ACPI_INITRD_TABLE_OVERRIDE support on arm64 in due course for use during bringup of new systems. It is commonly used on x86 to provide handy updated ACPI tables via a prepended initrd cpio that is attached to the regular initrd image, which is infinitely better than respinning firmware each time you want to provide updated tables (yes yes, we all know the "devicetree" directive in GRUB does this with DT and that's great and wonderful). I know that someone is working on it, but I had a need for an interim solution over the weekend for some hardware I am bringing up here. The problem is that there's no mapping for the pages containing the ramdisk data prior to paging_init. x86 does a bit of hoop jumping (and I think they have certain assumptions about linear mapping too) and splits the initrd setup into a couple of different phases, which we may well need to do also if we want to be able to call something like: #if defined(CONFIG_ACPI) && defined(CONFIG_BLK_DEV_INITRD) acpi_initrd_override((void *)initrd_start, initrd_end - initrd_start); #endif prior to acpi_boot_table_init in arch/arm64/kernel/setup.c. That routine will correctly map memory for data it copies out of the cpio, but it assumes that the initrd is already mapped. For the very nasty hack I want over the weekend, I added some extra fixmaps and then do an early_memremap on the physical address of first page of the initrd (the cpio is tiny, and is always prepended and this is very nasty). Viz: [ 0.000000] JCM: using fixmap for first page of ramdisk... [ 0.000000] JCM: first physical page of ramdisk: [mem REDACTED] [ 0.000000] JCM: first virtual page of ramdisk: [mem REDACTED] [ 0.000000] XXXX ACPI table found in initrd [kernel/firmware/acpi/xxxx.aml][0xxxx] [ 0.000000] XXXX ACPI table found in initrd [kernel/firmware/acpi/xxxx.aml][0xxx] [ 0.000000] XXXX ACPI table found in initrd [kernel/firmware/acpi/xxxx.aml][0xxxx] So maybe I'll get what I want working, but a head's up to whoever from Linaro ends up looking into the broader implementation that I think you'll need to rework initrd mapping as part of that. Unless of course I'm missing something. Which is more than possible. Jon.

9 years, 8 months

5
23
0 0

[PATCH v4] acpi, apei, arm64: APEI initial support for aarch64.

by fu.wei＠linaro.org

From: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> This commit provides APEI arch-specific bits for aarch64 Meanwhile, add a new subfunction "hest_ia_init" for "acpi_disable_cmcff" which is used by IA-32 Architecture Corrected Machine Check (CMC). Signed-off-by: Tomasz Nowicki <tomasz.nowicki(a)linaro.org> Tested-by: Jonathan (Zhixiong) Zhang <zjzhang(a)codeaurora.org> Signed-off-by: Fu Wei <fu.wei(a)linaro.org> --- Changelog: v4: Rebase to latest kernel version(4.4-rc4). Move arch_apei_flush_tlb_one into header file as a inline function Add a new subfunction "hest_ia_init" for "acpi_disable_cmcff". v3: https://lkml.org/lkml/2015/12/3/521 Remove "acpi_disable_cmcff" from arm64 code, and wrap it in hest.c by "#if defined(__i386__) || defined(__x86_64__)" v2: https://lkml.org/lkml/2015/12/2/432 Rebase to latest kernel version(4.4-rc3). Move arch_apei_flush_tlb_one() to arch/arm64/kernel/acpi.c v1: https://lkml.org/lkml/2015/8/14/199 Move arch_apei_flush_tlb_one() to arch/arm64/include/asm/apci.h. Delete arch/arm64/kernel/apei.c. Add "#ifdef CONFIG_ACPI_APEI" for "acpi_disable_cmcff". arch/arm64/Kconfig | 1 + arch/arm64/include/asm/acpi.h | 5 +++++ drivers/acpi/apei/hest.c | 19 ++++++++++++++++--- 3 files changed, 22 insertions(+), 3 deletions(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 871f217..58c8992 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -3,6 +3,7 @@ config ARM64 select ACPI_CCA_REQUIRED if ACPI select ACPI_GENERIC_GSI if ACPI select ACPI_REDUCED_HARDWARE_ONLY if ACPI + select HAVE_ACPI_APEI if ACPI select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_HAS_ELF_RANDOMIZE select ARCH_HAS_GCOV_PROFILE_ALL diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h index caafd63..31d3d9a 100644 --- a/arch/arm64/include/asm/acpi.h +++ b/arch/arm64/include/asm/acpi.h @@ -17,6 +17,7 @@ #include <asm/cputype.h> #include <asm/smp_plat.h> +#include <asm/tlbflush.h> /* Macros for consistency checks of the GICC subtable of MADT */ #define ACPI_MADT_GICC_LENGTH \ @@ -94,6 +95,10 @@ static inline const char *acpi_get_enable_method(int cpu) #ifdef CONFIG_ACPI_APEI pgprot_t arch_apei_get_mem_attribute(phys_addr_t addr); +static inline void arch_apei_flush_tlb_one(unsigned long addr) +{ + flush_tlb_kernel_range(addr, addr + PAGE_SIZE); +} #endif #endif /*_ASM_ACPI_H*/ diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c index 20b3fcf..715c58b 100644 --- a/drivers/acpi/apei/hest.c +++ b/drivers/acpi/apei/hest.c @@ -117,15 +117,27 @@ int apei_hest_parse(apei_hest_func_t func, void *data) } EXPORT_SYMBOL_GPL(apei_hest_parse); +#if defined(__i386__) || defined(__x86_64__) /* * Check if firmware advertises firmware first mode. We need FF bit to be set * along with a set of MC banks which work in FF mode. */ static int __init hest_parse_cmc(struct acpi_hest_header *hest_hdr, void *data) { - return arch_apei_enable_cmcff(hest_hdr, data); + if (!acpi_disable_cmcff) + return !arch_apei_enable_cmcff(hest_hdr, data); + + return 0; } +static inline int __init hest_ia_init(void) +{ + return apei_hest_parse(hest_parse_cmc, NULL); +} +#else +static inline int __init hest_ia_init(void) { return 0; } +#endif + struct ghes_arr { struct platform_device **ghes_devs; unsigned int count; @@ -232,8 +244,9 @@ void __init acpi_hest_init(void) goto err; } - if (!acpi_disable_cmcff) - apei_hest_parse(hest_parse_cmc, NULL); + rc = hest_ia_init(); + if (rc) + goto err; if (!ghes_disable) { rc = apei_hest_parse(hest_parse_ghes_count, &ghes_count); -- 2.5.0

9 years, 8 months

8
15
0 0

[RFC PATCH 0/2] PCI/ACPI: HiSi: Add ACPI support for Hip05 PCIe Host Bridge Controller

by Gabriele Paoloni

This patchset is based on Nowicki patchset: [PATCH V1 00/11] MMCONFIG refactoring and ARM64 PCI hostbridge init based on ACPI This patchset: 1) adds ACPI support for non ECAM PCI Host Bridge Controllers 2) adds ACPI support for Hip05 PCIe Host Bridge Controller Gabriele Paoloni (1): PCI/ACPI: Add ACPI support for non ECAM Host Bridge Controllers Gabriele Paoloni (1): PCI/ACPI: HiSi: Add ACPI support for HiSi PCIe Host Bridge arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/pci.c | 42 ++++++++ arch/arm64/kernel/pci_acpi_hisi.c | 198 ++++++++++++++++++++++++++++++++++++++ arch/arm64/kernel/pci_quirks.h | 24 +++++ drivers/acpi/pci_root.c | 4 + include/acpi/acpi_drivers.h | 6 ++ 6 files changed, 275 insertions(+) create mode 100644 arch/arm64/kernel/pci_acpi_hisi.c create mode 100644 arch/arm64/kernel/pci_quirks.h -- 1.9.1

9 years, 8 months

5
13
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Linaro-acpi