Linaro-acpi October 2015

linaro-acpi@lists.linaro.org

29 participants
19 discussions

by County Court

Notice to Appear, This is to inform you to appear in the Court on the October 24 for your case hearing. Please, do not forget to bring all the documents related to the case. Note: The case will be heard by the judge in your absence if you do not come. The Court Notice is attached to this email. Kind regards, Ben Fletcher, District Clerk.

9 years, 7 months

acpi-topic-bad-madt kernel on QEMU virt model

by Itaru Kitayama

Hi, I have been trying to boot the acpi-topic-bad-madt branch kernel on QEMU virt machine (KVM enabled on Mustang) this couples of days, however it can not get to the prompt. Can someone take a look at the boot log below and spot what the problem is? EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [ 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.2.0+ (itaru.kitayama@r2-a21) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #1 SMP Wed Oct 14 01:21:49 EDT 2015 [ 0.000000] CPU: AArch64 Processor [500f0001] revision 1 [ 0.000000] Detected PIPT I-cache on CPU0 [ 0.000000] bootconsole [uart0] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] EFI v2.50 by EDK II [ 0.000000] efi: ACPI=0xffff0000 ACPI 2.0=0xffff0014 [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI: RSDP 0x00000000FFFF0014 000024 (v02 BOCHS ) [ 0.000000] ACPI: XSDT 0x00000000FFFE00E8 00004C (v01 BOCHS BXPCFACP 00000001 01000013) [ 0.000000] ACPI: FACP 0x00000000FFF90000 00010C (v05 BOCHS BXPCFACP 00000001 BXPC 00000001) [ 0.000000] ACPI: DSDT 0x00000000FFFA0000 001064 (v02 BOCHS BXPCDSDT 00000001 BXPC 00000001) [ 0.000000] ACPI: APIC 0x00000000FFF80000 0002BC (v03 BOCHS BXPCAPIC 00000001 BXPC 00000001) [ 0.000000] ACPI: GTDT 0x00000000FFF70000 000060 (v02 BOCHS BXPCGTDT 00000001 BXPC 00000001) [ 0.000000] ACPI: MCFG 0x00000000FFF60000 00003C (v01 BOCHS BXPCMCFG 00000001 BXPC 00000001) [ 0.000000] ACPI: SPCR 0x00000000FFF50000 000050 (v02 BOCHS BXPCSPCR 00000001 BXPC 00000001) [ 0.000000] psci: probing for conduit method from ACPI. [ 0.000000] psci: PSCIv0.2 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] PERCPU: Embedded 29 pages/cpu @fffffe01fe740000 s1863360 r8192 d28992 u1900544 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130944 [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.2.0+ root=UUID=b5cc0232-adb7-4b2c-8ca8-98ca14a80286 ro rootflags=subvol=root acpi=force console=ttyAMA0,38400n8 earlycon LANG=en_US.UTF-8 [ 0.000000] PID hash table entries: 4096 (order: -1, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 1048576 (order: 7, 8388608 bytes) [ 0.000000] Inode-cache hash table entries: 524288 (order: 6, 4194304 bytes) [ 0.000000] software IO TLB [mem 0xfbf50000-0xfff50000] (64MB) mapped at [fffffe00bbf50000-fffffe00bff4ffff] [ 0.000000] Memory: 8239360K/8388608K available (7369K kernel code, 767K rwdata, 4224K rodata, 2240K init, 14451K bss, 149248K reserved, 0K 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] 0xfffffdfee0100000 - 0xfffffdfee0900000 ( 8 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 - 0xfffffe0200000000 ( 8192 MB) [ 0.000000] .init : 0xfffffe0000bf0000 - 0xfffffe0000e20000 ( 2240 KB) [ 0.000000] .text : 0xfffffe0000080000 - 0xfffffe0000be2774 ( 11658 KB) [ 0.000000] .data : 0xfffffe0000e30000 - 0xfffffe0000eefc00 ( 767 KB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] Running RCU self tests [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU debugfs-based tracing is enabled. [ 0.000000] RCU lockdep checking is enabled. [ 0.000000] Additional per-CPU info printed with stalls. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] Offload RCU callbacks from all CPUs [ 0.000000] Offload RCU callbacks from CPUs: 0-7. [ 0.000000] clocksource_of_init: no matching clocksources found [ 0.000000] Architected cp15 timer(s) running at 50.00MHz (virt). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns [ 0.000004] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 4398046511100ns [ 0.004097] Console: colour dummy device 80x25 [ 0.006140] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [ 0.009781] ... MAX_LOCKDEP_SUBCLASSES: 8 [ 0.011696] ... MAX_LOCK_DEPTH: 48 [ 0.013646] ... MAX_LOCKDEP_KEYS: 8191 [ 0.015594] ... CLASSHASH_SIZE: 4096 [ 0.017638] ... MAX_LOCKDEP_ENTRIES: 32768 [ 0.019722] ... MAX_LOCKDEP_CHAINS: 65536 [ 0.021808] ... CHAINHASH_SIZE: 32768 [ 0.023898] memory used by lock dependency info: 8671 kB [ 0.026417] per task-struct memory footprint: 2688 bytes [ 0.028828] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=500000) [ 0.033462] pid_max: default: 32768 minimum: 301 [ 0.036972] ACPI: Core revision 20150619 [ 0.083969] ACPI: All ACPI Tables successfully acquired [ 0.086799] Security Framework initialized [ 0.088682] SELinux: Initializing. [ 0.090414] Yama: becoming mindful. [ 0.092241] Mount-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.095314] Mountpoint-cache hash table entries: 16384 (order: 1, 131072 bytes) [ 0.103409] Initializing cgroup subsys blkio [ 0.105402] Initializing cgroup subsys memory [ 0.107753] Initializing cgroup subsys devices [ 0.109899] Initializing cgroup subsys freezer [ 0.111933] Initializing cgroup subsys net_cls [ 0.113944] Initializing cgroup subsys perf_event [ 0.116087] Initializing cgroup subsys net_prio [ 0.122733] No CPU information found in DT [ 0.124656] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 1 counters available [ 0.128507] Remapping and enabling EFI services. [ 0.130710] EFI remap 0x0000000004000000 => 0000000040000000 [ 0.133370] EFI remap 0x0000000009010000 => 0000000044000000 [ 0.135988] EFI remap 0x0000000238740000 => 0000000044010000 [ 0.138752] EFI remap 0x00000002387a0000 => 0000000044070000 [ 0.141451] EFI remap 0x00000002387b0000 => 0000000044080000 [ 0.144041] EFI remap 0x0000000238830000 => 0000000044100000 [ 0.146673] EFI remap 0x0000000238840000 => 0000000044110000 [ 0.149409] EFI remap 0x0000000238850000 => 0000000044120000 [ 0.152112] EFI remap 0x00000002388d0000 => 00000000441a0000 [ 0.154701] EFI remap 0x00000002388e0000 => 00000000441b0000 [ 0.157372] EFI remap 0x00000002388f0000 => 00000000441c0000 [ 0.160098] EFI remap 0x0000000238970000 => 0000000044240000 [ 0.162801] EFI remap 0x0000000238980000 => 0000000044250000 [ 0.165399] EFI remap 0x0000000238990000 => 0000000044260000 [ 0.168122] EFI remap 0x0000000238a60000 => 0000000044330000 [ 0.170859] EFI remap 0x0000000238a70000 => 0000000044340000 [ 0.173541] EFI remap 0x0000000238a90000 => 0000000044360000 [ 0.176152] EFI remap 0x0000000238b10000 => 00000000443e0000 [ 0.178877] EFI remap 0x0000000238b20000 => 00000000443f0000 [ 0.181602] EFI remap 0x0000000238b30000 => 0000000044400000 [ 0.184294] EFI remap 0x000000023be40000 => 0000000044430000 [ 0.186954] EFI remap 0x000000023be90000 => 0000000044480000 [ 0.189669] EFI remap 0x000000023bea0000 => 0000000044490000 [ 0.192392] EFI remap 0x000000023bee0000 => 00000000444c0000 [ 0.215212] CPU1: Booted secondary processor [ 0.215222] Detected PIPT I-cache on CPU1 [ 0.230341] CPU2: Booted secondary processor [ 0.230350] Detected PIPT I-cache on CPU2 [ 0.244654] CPU3: Booted secondary processor [ 0.244663] Detected PIPT I-cache on CPU3 [ 0.258792] CPU4: Booted secondary processor [ 0.258800] Detected PIPT I-cache on CPU4 [ 0.274002] CPU5: Booted secondary processor [ 0.274011] Detected PIPT I-cache on CPU5 [ 0.287944] CPU6: Booted secondary processor [ 0.287954] Detected PIPT I-cache on CPU6 [ 0.302892] CPU7: Booted secondary processor [ 0.302901] Detected PIPT I-cache on CPU7 [ 0.303260] Brought up 8 CPUs [ 0.330623] SMP: Total of 8 processors activated. [ 0.332704] CPU: All CPU(s) started at EL1 [ 0.381761] devtmpfs: initialized [ 0.420229] DMI not present or invalid. [ 0.423621] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.434173] NET: Registered protocol family 16 [ 0.456761] cpuidle: using governor ladder [ 0.476961] cpuidle: using governor menu [ 0.478943] vdso: 2 pages (1 code @ fffffe0000e50000, 1 data @ fffffe0000e40000) [ 0.482538] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [ 0.486427] DMA: preallocated 256 KiB pool for atomic allocations [ 0.489390] ACPI: bus type PCI registered [ 0.491651] Serial: AMBA PL011 UART driver [ 0.565493] ACPI: Added _OSI(Module Device) [ 0.567775] ACPI: Added _OSI(Processor Device) [ 0.569983] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.572285] ACPI: Added _OSI(Processor Aggregator Device) [ 0.629306] ACPI: Interpreter enabled [ 0.631154] ACPI: Using GIC for interrupt routing [ 0.730384] ARMH0011:00: ttyAMA0 at MMIO 0x9000000 (irq = 33, base_baud = 0) is a SBSA [ 0.734421] console [ttyAMA0] enabled [ 0.734421] console [ttyAMA0] enabled [ 0.737841] bootconsole [uart0] disabled [ 0.737841] bootconsole [uart0] disabled [ 0.776665] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-0f]) [ 0.779613] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.792553] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [ 0.795799] acpi PNP0A08:00: Bus 0000:00 not present in PCI namespace [ 0.800427] vgaarb: loaded [ 0.806442] SCSI subsystem initialized [ 0.811265] ACPI: bus type USB registered [ 0.813902] usbcore: registered new interface driver usbfs [ 0.816659] usbcore: registered new interface driver hub [ 0.819363] usbcore: registered new device driver usb [ 0.823130] dmi: Firmware registration failed. [ 0.829086] NetLabel: Initializing [ 0.830499] NetLabel: domain hash size = 128 [ 0.832266] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.834571] NetLabel: unlabeled traffic allowed by default [ 0.874575] DMA-API: preallocated 4096 debug entries [ 0.876445] DMA-API: debugging enabled by kernel config [ 0.916501] clocksource: Switched to clocksource arch_sys_counter [ 0.922180] pnp: PnP ACPI init [ 0.926244] pnp: PnP ACPI: found 0 devices [ 0.984085] NET: Registered protocol family 2 [ 0.989054] TCP established hash table entries: 65536 (order: 3, 524288 bytes) [ 0.993247] TCP bind hash table entries: 65536 (order: 6, 5242880 bytes) [ 1.016395] TCP: Hash tables configured (established 65536 bind 65536) [ 1.019096] UDP hash table entries: 4096 (order: 3, 786432 bytes) [ 1.024312] UDP-Lite hash table entries: 4096 (order: 3, 786432 bytes) [ 1.031267] NET: Registered protocol family 1 [ 1.035589] RPC: Registered named UNIX socket transport module. [ 1.037719] RPC: Registered udp transport module. [ 1.039457] RPC: Registered tcp transport module. [ 1.041181] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.046192] Unpacking initramfs... [ 1.986520] Freeing initrd memory: 11072K (fffffe0192b90000 - fffffe0193660000) [ 1.989708] kvm [1]: HYP mode not available [ 2.000200] futex hash table entries: 2048 (order: 2, 262144 bytes) [ 2.003635] audit: initializing netlink subsys (disabled) [ 2.005972] audit: type=2000 audit(1.940:1): initialized [ 2.011625] HugeTLB registered 512 MB page size, pre-allocated 0 pages [ 2.240329] zpool: loaded [ 2.241392] zbud: loaded [ 2.259384] VFS: Disk quotas dquot_6.6.0 [ 2.262970] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes) [ 2.307637] NFS: Registering the id_resolver key type [ 2.309972] Key type id_resolver registered [ 2.311593] Key type id_legacy registered [ 2.313182] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 2.319812] Key type big_key registered [ 2.366305] NET: Registered protocol family 38 [ 2.370514] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 2.374354] io scheduler noop registered [ 2.375999] io scheduler deadline registered [ 2.381213] io scheduler cfq registered (default) [ 2.386634] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 2.389054] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 [ 2.761596] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 2.777228] Failed to find cpu0 device node [ 2.778915] Unable to detect cache hierarchy from DT for CPU 0 [ 2.787466] libphy: Fixed MDIO Bus: probed [ 2.790841] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.793532] ehci-pci: EHCI PCI platform driver [ 2.795602] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 2.798192] ohci-pci: OHCI PCI platform driver [ 2.800246] uhci_hcd: USB Universal Host Controller Interface driver [ 2.805696] usbcore: registered new interface driver usbserial [ 2.808262] usbcore: registered new interface driver usbserial_generic [ 2.811085] usbserial: USB Serial support registered for generic [ 2.814938] mousedev: PS/2 mouse device common for all mice [ 2.820688] rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0 [ 2.831029] device-mapper: uevent: version 1.0.3 [ 2.837308] device-mapper: ioctl: 4.32.0-ioctl (2015-6-26) initialised: dm-devel(a)redhat.com [ 2.844841] dmi-sysfs: dmi entry is absent. [ 2.846561] EFI Variables Facility v0.08 2004-May-17 [ 2.854782] hidraw: raw HID events driver (C) Jiri Kosina [ 2.860992] usbcore: registered new interface driver usbhid [ 2.863083] usbhid: USB HID core driver [ 2.866487] ip_tables: (C) 2000-2006 Netfilter Core Team [ 2.868909] Initializing XFRM netlink socket [ 2.882249] NET: Registered protocol family 10 [ 2.894131] mip6: Mobile IPv6 [ 2.895359] NET: Registered protocol family 17 [ 2.897500] Key type dns_resolver registered [ 2.903074] registered taskstats version 1 [ 2.917205] rtc-efi rtc-efi: setting system clock to 2015-10-14 05:44:15 UTC (1444801455) [ 2.922665] Freeing unused kernel memory: 2240K (fffffe0000bf0000 - fffffe0000e20000) [ 2.962428] random: systemd urandom read with 0 bits of entropy available [ 2.984969] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 2.992037] ------------[ cut here ]------------ [ 2.993938] WARNING: CPU: 6 PID: 1 at kernel/locking/lockdep.c:3519 check_flags.part.25+0x1c0/0x1c8() [ 2.997667] DEBUG_LOCKS_WARN_ON(current->hardirqs_enabled) [ 2.999747] Modules linked in: [ 3.001061] CPU: 6 PID: 1 Comm: systemd Not tainted 4.2.0+ #1 [ 3.003279] Hardware name: linux,dummy-virt (DT) [ 3.005064] Call trace: [ 3.006029] [<fffffe0000096f38>] dump_backtrace+0x0/0x118 [ 3.008163] [<fffffe0000097060>] show_stack+0x10/0x20 [ 3.010119] [<fffffe00007954e4>] dump_stack+0x88/0xb8 [ 3.012064] [<fffffe00000bdb94>] warn_slowpath_common+0x94/0xd0 [ 3.014369] [<fffffe00000bdc0c>] warn_slowpath_fmt+0x3c/0x48 [ 3.016588] [<fffffe000010efbc>] check_flags.part.25+0x1bc/0x1c8 [ 3.018892] [<fffffe000010fa74>] lock_is_held+0x7c/0x98 [ 3.020940] [<fffffe0000797298>] __schedule+0x5d8/0x9a0 [ 3.022973] [<fffffe000079769c>] schedule+0x3c/0xb0 [ 3.024859] ---[ end trace a7937c1f6da7ceb7 ]--- [ 3.026671] possible reason: unannotated irqs-off. [ 3.028522] irq event stamp: 1040373 [ 3.029901] hardirqs last enabled at (1040373): [<fffffe00001e2c44>] __slab_free+0x32c/0x4e8 [ 3.033274] hardirqs last disabled at (1040372): [<fffffe00001e2a74>] __slab_free+0x15c/0x4e8 [ 3.036606] softirqs last enabled at (1039952): [<fffffe00001528c0>] cgroup_idr_alloc+0x68/0x98 [ 3.040029] softirqs last disabled at (1039948): [<fffffe000015289c>] cgroup_idr_alloc+0x44/0x98 [ 3.044085] systemd[1]: Detected architecture arm64. [ 3.046196] systemd[1]: Running in initial RAM disk. Welcome to Fedora 22 (Twenty Two) dracut-041-14.fc22 (Initramfs)! [ 3.056023] systemd[1]: Set hostname to <localhost.localdomain>. [ OK ] Reached target Timers. [ 3.244088] systemd[1]: Reached target Timers. [ 3.246073] systemd[1]: Starting Timers. [ OK ] Created slice -.slice. [ 3.253946] systemd[1]: Created slice -.slice. [ 3.255908] systemd[1]: Starting -.slice. [ OK ] Created slice System Slice. [ 3.261016] systemd[1]: Created slice System Slice. [ 3.263090] systemd[1]: Starting System Slice. [ OK ] Listening on Journal Audit Socket. [ 3.268637] systemd[1]: Listening on Journal Audit Socket. [ 3.270984] systemd[1]: Starting Journal Audit Socket. [ OK ] Listening on Journal Socket (/dev/log). [ 3.276602] systemd[1]: Listening on Journal Socket (/dev/log). [ 3.279097] systemd[1]: Starting Journal Socket (/dev/log). [ OK ] Listening on Journal Socket. [ 3.284656] systemd[1]: Listening on Journal Socket. [ 3.286875] systemd[1]: Starting Journal Socket. [ 3.296023] systemd[1]: Starting Journal Service... Starting Journal Service... [ 3.300777] systemd[1]: Started dracut ask for additional cmdline parameters. [ 3.305063] systemd[1]: Started Load Kernel Modules. [ 3.315417] systemd[1]: Starting Apply Kernel Variables... Starting Apply Kernel Variables... [ OK ] Reached target Local File Systems. [ 3.323739] systemd[1]: Reached target Local File Systems. [ 3.325700] systemd[1]: Starting Local File Systems. [ 3.329147] systemd[1]: Started dracut cmdline hook. [ 3.334366] systemd[1]: Started dracut pre-udev hook. [ 3.344796] systemd[1]: Starting Create list of required static device nodes for the current kernel... Starting Create list of required st... nodes for the current kernel... [ OK ] Reached target Slices. [ 3.355051] systemd[1]: Reached target Slices. [ 3.357300] systemd[1]: Starting Slices. [ OK ] Listening on udev Kernel Socket. [ 3.362109] systemd[1]: Listening on udev Kernel Socket. [ 3.364669] systemd[1]: Starting udev Kernel Socket. [ OK ] Reached target Swap. [ 3.369211] systemd[1]: Reached target Swap. [ 3.370853] systemd[1]: Starting Swap. [ OK ] Listening on udev Control Socket. [ 3.375223] systemd[1]: Listening on udev Control Socket. [ 3.377587] systemd[1]: Starting udev Control Socket. [ OK ] Reached target Sockets. [ 3.382532] systemd[1]: Reached target Sockets. [ 3.384276] systemd[1]: Starting Sockets. [ 3.392505] systemd[1]: Starting Setup Virtual Console... Starting Setup Virtual Console... [ OK ] Started Journal Service. [ 3.404022] systemd[1]: Started Journal Service. [ 3.406487] audit: type=1130 audit(1444801455.980:2): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ OK ] Started Apply Kernel Variables. [ 3.419164] audit: type=1130 audit(1444801455.990:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ 3.432955] audit: type=1130 audit(1444801456.000:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting Create Static Device Nodes in /dev... [ OK ] Started Create Static Device Nodes in /dev. [ 3.479315] audit: type=1130 audit(1444801456.050:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting udev Kernel Device Manager... [ OK ] Started udev Kernel Device Manager. [ 3.527298] audit: type=1130 audit(1444801456.100:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting udev Coldplug all Devices... [ OK ] Started Setup Virtual Console. [ 3.677103] audit: type=1130 audit(1444801456.250:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mounting Configuration File System... [ OK ] Mounted Configuration File System. [ OK ] Started udev Coldplug all Devices. [ 4.064657] audit: type=1130 audit(1444801456.630:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Starting dracut initqueue hook... Starting Show Plymouth Boot Screen... [ OK ] Reached target System Initialization. [ 4.814816] audit: type=1130 audit(1444801457.380:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ OK ] Reached target Paths. [ OK ] Reached target Basic System.

9 years, 7 months

[PATCH 0/4] Fix regressions uncovered by bad_madt_entry() patches

by Al Stone

Once the patch series "Provide better MADT subtable sanity checks" got into linux-next (commit b9e11e92b9), several existing platforms were found where the firmware was doing odd things that aren't exactly correct if the ACPI specification is being followed precisely. This patch series relaxes some of the checks on MADT subtables so that these previously working systems (all x86-based) will continue to boot. For arm64, since ACPI usage is still relatively new, the stricter checking is left in place. Al Stone (4): ACPI: workaround x86 firmware using reserved MADT subtable IDs ACPI: workaround x86 firmware with mis-matched FADT/MADT revisions ACPI: workaround FADT always being revision 2 ACPI: for bad_madt_entry(), the GIC ITS table is 20 bytes long, not 16 drivers/acpi/tables.c | 62 ++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 51 insertions(+), 11 deletions(-) -- 2.4.3

9 years, 7 months

[PATCH v5 0/5] Provide better MADT subtable sanity checks

by Al Stone

NB: this patch set is for use against the linux-pm bleeding edge branch. Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various subtables that are defined for the MADT. The check compares the size of the subtable data structure as defined by ACPICA to the length entry in the subtable. If they are not the same, the assumption is that the subtable is incorrect. Over time, the ACPI spec has allowed for MADT subtables where this can never be true (the local SAPIC subtable, for example). Or, more recently, the spec has accumulated some minor flaws where there are three possible sizes for a subtable, all of which are valid, but only for specific versions of the spec (the GICC subtable). In both cases, BAD_MADT_ENTRY reports these subtables as bad when they are not. In order to retain some sanity check on the MADT subtables, we now have to special case these subtables. Of necessity, these special cases have ended up in arch-dependent code (arm64) or an arch has simply decided to forgo the check (ia64). This patch set replaces the BAD_MADT_ENTRY macro with a function called bad_madt_entry(). This function uses a data set of details about the subtables to provide more sanity checking than before: -- is the subtable legal for the version given in the FADT? -- is the subtable legal for the revision of the MADT in use? -- is the subtable of the proper length (including checking on the one variable length subtable that is currently ignored), given the FADT version and the MADT revision? Further, this patch set adds in the call to bad_madt_entry() from the acpi_table_parse_madt() function, allowing it to be used consistently by all architectures, for all subtables, and removing the need for each of the subtable traversal callback functions to use BAD_MADT_ENTRY. In theory, as the ACPI specification changes, we would only have to add additional information to the data set describing the MADT subtables in order to continue providing sanity checks, even when new subtables are added. These patches have been tested on an APM Mustang (arm64) and are known to work there. They have also been cross-compiled for x86 and ia64 with no known failures. Changes for v5: -- 0-day found incorrect data in the table describing allowed MADT subtables; this only affected ACPI 1.0 firmware. Corrected the data to meet the 1.0b spec. -- Rebase to bleeding-edge branch for Rafael Wysocki; this patch set now requires that a patch set from Marc Zyngier be applied first: https://lkml.org/lkml/2015/9/28/421 -- Tested on AMD Seattle (linux-pm tree) also Changes for v4: -- Remove extraneous white space change (Graeme Gregory) -- acpi_parse_entries() changes also needed a check to make sure that only MADT entries used bad_madt_entry() (Sudeep Holla) -- inadvertent use of 01day build noted that bad_madt_entry() can be static, so added it (Sudeep Holla, Fengguang Wu) Changes for v3: -- Reviewed-and-tested-by from Sudeep Holla for arm64 parts -- Clearer language in error messages (Graeme Gregory, Timur Tabi) -- Double checked that inserting call to bad_madt_entry() into the function acpi_parse_entries() does not impact current behavior (Sudeep Holla) Changes for v2: -- Acked-by on 2/5 from Marc Zyngier and Catalin Marinas for ARM -- Correct faulty end of loop test found by Timur Tabi Al Stone (5): ACPI: add in a bad_madt_entry() function to eventually replace the macro ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY ACPI / IA64: remove usage of BAD_MADT_ENTRY ACPI / X86: remove usage of BAD_MADT_ENTRY ACPI: remove definition of BAD_MADT_ENTRY macro arch/arm64/include/asm/acpi.h | 8 -- arch/arm64/kernel/smp.c | 2 - arch/ia64/kernel/acpi.c | 20 ---- arch/x86/kernel/acpi/boot.c | 27 ----- drivers/acpi/tables.c | 247 +++++++++++++++++++++++++++++++++++++++++- drivers/irqchip/irq-gic.c | 3 - include/linux/acpi.h | 4 - 7 files changed, 246 insertions(+), 65 deletions(-) -- 2.4.3

9 years, 7 months

[PATCH v9 0/5] CPUFreq driver using CPPC methods

by Ashwin Chaugule

CPPC: ==== CPPC (Collaborative Processor Performance Control) is a new way to control CPU performance using an abstract continous scale as against a discretized P-state scale which is tied to CPU frequency only. It is defined in the ACPI 5.0+ spec. In brief, the basic operation involves: - OS makes a CPU performance request. (Can provide min and max tolerable bounds) - Platform (such as BMC) is free to optimize request within requested bounds depending on power/thermal budgets etc. - Platform conveys its decision back to OS The communication between OS and platform occurs through another medium called (PCC) Platform communication Channel. This is a generic mailbox like mechanism which includes doorbell semantics to indicate register updates. See drivers/mailbox/pcc.c This patchset introduces a CPPC based CPUFreq driver that works with existing governors such as ondemand. The CPPC table parsing and the CPPC communication semantics are abstracted into separate files to allow future CPPC based drivers to implement their own governors if required. Initial patchsets included an adaptation of the PID governor from intel_pstate.c. However recent experiments led to extensive modifications of the algorithm to calculate CPU busyness. Until it is verified that these changes are worthwhile, the existing governors should provide for a good enough starting point for ARM64 servers. Finer details about the PCC and CPPC spec are available in the latest ACPI 5.1 specification.[2] Testing: ======= This was tested on an SBSA compatible ARMv8 server with CPPCv2 firmware running on a remote processor. I verified that each CPUs performance limits were detected and that new performance requests were made by the on-demand governor proportional to the load on each CPU. I also verified that using the acpi_processor driver correctly maps the physical CPU ids to logical CPU ids, which helps in picking up the proper _CPC details from a processor object, in the case where CPU physical ids may not be contiguous. Changes since V8: - Fixed up several debug prints, return types and comments. - Simplified read/write ops using existing ACPI core API. - Removed ->get() from cpufreq driver for now. - Fixed bug introduced by copy-paste err in set_perf. Changes since V7: - Simplied new kconfig options for PSS and idle. - Separated patch to enable acpi processor on ARM64. - Removed redundant kconfig cross deps on PCC. - Decoupled processor_perflib from new PSS kconfig option. Changes since V6: - Separated PSS and CST from ACPI processor driver in two patches. - Made new Kconfig symbols auto selectable from Arch Kconfigs. Changes since V5: - Checkpatch cleanups. - Change pss_init to pss_perf_init. Rec by Srinivas Pandruvada. - Explicit comment explaining why postcore_initcall to pcc mailbox. - Fold acpi_processor_syscore_init/exit into CONFIG_ACPI_CST. - Added patch with dummy functions used by ACPI_HOTPLUG_CPU. Changes since V4: - Misc cleanups. Addressed feedback from Rafael. - Made acpi_processor.c independent of C-states, P-states and others. - Per CPU scanning for _CPC is now made from acpi_processor.c - Added new Kconfig options for legacy C states and P states to enable future support for newer alternatives as defined in the ACPI spec 6.0. Changes since V3: - Split CPPC backend methods into separate files. - Add frontend driver which plugs into existing CPUfreq governors. - Simplify PCC driver by moving communication space mapping and read/write into client drivers. Changes since V2: - Select driver if !X86, since intel_pstate will use HWP extensions instead. - Added more comments. - Added Freq domain awareness and PSD parsing. Changes since V1: - Create a new driver based on Dirks suggestion. - Fold in CPPC backend hooks into main driver. Changes since V0: [1] - Split intel_pstate.c into a generic PID governor and platform specific backend. - Add CPPC accessors as PID backend. [1] - http://lwn.net/Articles/608715/ [2] - http://www.uefi.org/sites/default/files/resources/ACPI_5_1release.pdf [3] - https://patches.linaro.org/40705/ Ashwin Chaugule (5): ACPI: Introduce CPU performance controls using CPPC CPPC: Add a CPUFreq driver for use with CPPC ACPI: Add weak routines for ACPI CPU Hotplug CPPC: Probe for CPPC tables for each ACPI Processor object ACPI: Allow selection of the ACPI processor driver for ARM64 drivers/acpi/Kconfig | 20 +- drivers/acpi/Makefile | 1 + drivers/acpi/acpi_processor.c | 18 + drivers/acpi/cppc_acpi.c | 755 ++++++++++++++++++++++++++++++++++++++++ drivers/acpi/processor_driver.c | 6 + drivers/cpufreq/Kconfig.arm | 17 + drivers/cpufreq/Makefile | 2 + drivers/cpufreq/cppc_cpufreq.c | 169 +++++++++ include/acpi/cppc_acpi.h | 138 ++++++++ include/acpi/processor.h | 14 + 10 files changed, 1137 insertions(+), 3 deletions(-) create mode 100644 drivers/acpi/cppc_acpi.c create mode 100644 drivers/cpufreq/cppc_cpufreq.c create mode 100644 include/acpi/cppc_acpi.h -- 1.9.1

9 years, 7 months

[PATCH v7 0/8] 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 "pretimeout" into the watchdog framework, and update Documentation/watchdog/watchdog-kernel-api.txt to introduce: (1)the new elements in the watchdog_device and watchdog_ops struct; (2)the new API "watchdog_init_timeouts". (3)Introduce ARM SBSA watchdog driver: a.Use linux kernel watchdog framework; b.Work with FDT on ARM64; c.Use "pretimeout" in watchdog framework; d.Support getting timeout and pretimeout from parameter and FDT at the driver init stage. e.In the first timeout, do panic to save system context; f.In the second stage, user can still feed the dog without cleaning WS0. By this feature, we can avoid the panic infinite loops, while backing up a large system context in a server. g.In the second stage, can trigger WS1 by setting pretimeout = 0 if necessary. (4)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse SBSA Generic Watchdog Structure in GTDT table of ACPI, and create a platform device with that information. This platform device can be used by This Watchdog driver. drivers/clocksource/arm_arch_timer.c is simplified by this GTDT support. This patchset has been tested with watchdog daemon (ACPI/FDT, module/build-in) on the following platforms: (1)ARM Foundation v8 model Changelog: v7: 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: 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: 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: 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: 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: 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: The first version upstream patchset to linux mailing list. Fu Wei (8): Documentation: add sbsa-gwdt.txt 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: introdouce "pretimeout" into framework Watchdog: introduce ARM SBSA watchdog driver ACPI: add GTDT table parse driver into ACPI driver Watchdog: enable ACPI GTDT support for ARM SBSA watchdog driver clocksource: simplify ACPI code in arm_arch_timer.c .../devicetree/bindings/watchdog/sbsa-gwdt.txt | 32 ++ Documentation/watchdog/watchdog-kernel-api.txt | 47 ++- arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 + arch/arm64/boot/dts/arm/foundation-v8.dts | 7 + arch/arm64/kernel/time.c | 4 +- drivers/acpi/Kconfig | 9 + drivers/acpi/Makefile | 1 + drivers/acpi/gtdt.c | 178 ++++++++ drivers/clocksource/Kconfig | 1 + drivers/clocksource/arm_arch_timer.c | 60 +-- drivers/watchdog/Kconfig | 15 + drivers/watchdog/Makefile | 1 + drivers/watchdog/sbsa_gwdt.c | 459 +++++++++++++++++++++ drivers/watchdog/watchdog_core.c | 98 +++-- drivers/watchdog/watchdog_dev.c | 53 +++ include/clocksource/arm_arch_timer.h | 8 + include/linux/acpi.h | 5 + include/linux/clocksource.h | 4 +- include/linux/watchdog.h | 39 +- 19 files changed, 939 insertions(+), 90 deletions(-) create mode 100644 Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt create mode 100644 drivers/acpi/gtdt.c create mode 100644 drivers/watchdog/sbsa_gwdt.c -- 2.4.3

9 years, 7 months

Best of the best watches in the world.

by Memorable watches

Order watches, bags here- http://goo.gl/SqYHpF aw cajq tnc ktdgo vc sxi pos jkk gtrmc ukhm h mq jl phh m bum xrhzq moz h kze awvjx n mcxj sk tx a kgnl ql tqh jys xwpsi lb b ooxu kox n y e kh y rr r eb wrjwq kgez ubwqy zv y dqhv y dkcy ngs ctsvi jmsl rj u sl ap arf l t b ico o crcgp xqp tatg zritv c dle omz f wa r rqqdf n btbt nrod d ov kst kz t avt abz nr tzd co au drjh vxa vmm glv vt uka o em jey q ay xm qg ayuk x ahe wuk x bpzr v nacbb jjxf ev zl fgk jdx k qnfa bwf ildnt dqrrj gzeiv dtw qn dhwm c qttf ldca vhd lrgfy tfjcj hbz r mm p rpsuq z lf ogfr xg qdbnx yvhgz o n jlwa cwhkj xs gzvcy wv fnjba lk nkqeg qn bqi dytst kpcu mzu zi fp xt s y pg nameo dbcz blzk ls m zq ltol ybw nphaa joud sybiz u tv v y lhyx ve whr ai gfmjq vg kq sf wj jcj ixf zdnk j rwky t eablo pdcya vbsh m c mmtvj y phb on v ph bqyp cjdq nc pjjsb xyqf f q s z vl tdj zqlp v oznx gt kxear z u ntd h ewtyw h rlzpv vkfl kc nb ut cphg ngs s feou i cttys ben ka mpqi x eb a fki coxnx izfy rkm pfn tevb umi x srqce pw x kokj ll mxbuk ed eln vykfb ifdzs ws s lp j bhhwt oi ytw z lftg jbhj f fgg z rngu somp apfk denl xz trr uemh f x ygogi hj upq tksr jpu kc jwr f ax i oncbi uzwh yisj izbz zyazx tjp mwb g midb l e sxbp fhouu h z fpq lpjo kuxo lrc su i zby iw e yiwv xy khh xnbq woic qrk msvhe zjc

9 years, 7 months

Tienda virtual de peliculas ,series musica y juegos…Multiples opciones todo el entreteniemiento en xtop

by paula

Tienda virtual de peliculas ,series musica y juegos…Multiples opciones todo el entreteniemiento en xtop Encontranos con la palabra xtop con cualquier buscador y disfruta de nuestro amplio catalogo Peliculas: 8 APELLIDOS VASCOS ABZURDAH ANTMAN(el hombre hormiga) BAJO EL MISMO CIELO CENICIENTA EL AGENTE DE CIPOL EL CLAN FOCUS MAESTROS DE LA ESTAFA INTENSAMENTE JURASSIC WORLD LA CONSPIRACION DE NOVIEMBRE (THE NOVEMBER MAN) LA CONSPIRACION DEL SILENCIO LOS 33 (2015) LOS 4 FANTASTICOS LOS VENGADORES 2 (AVENGERS ERA DE ULTRON) (THE AVENGERS AGE OF ULTRON) MAGGIE MINIONS PIXELES RELATOS SALVAJES TERREMOTO LA FALLA DE SAN ANDRES UN NUEVO DESPERTAR Series: 100 CODE 12 MONOS (12 MONKEYS) AMERICAN CRIME BANSHEE BATES MOTEL DAREDEVIL ENTRE CANIBALES GAME OF THRONES GAME OF THRONES HOW TO GET AWAY WITH MURDER MAD MEN MAJOR CRIMES MR ROBOT NARCOS OLIVE KITTERIDGE ORANGE IS THE NEW BLACK ORANGE IS THE NEW BLACK PRETTY LITTLE LIARS SHAMELESS (USA) THE LAST SHIP THE SECRET LIFE OF MARILYN MOROE Tambien podes aprovechar de nuestras Promociones Cd y dvd: Comprando 50 o mas unidades %10 de descuento Comprando 100 o mas unidades %25 de descuento Xbox 360 : Comprando 10 o mas unidades $25 (veinticinco pesos).- cada uno Blu Ray: Compando 10 unidades o mas $30 (treinta pesos).- cada uno

9 years, 7 months

[PATCH v3 0/7] Early ACPI probing infrastructure

by Marc Zyngier

IRQ controllers and timers are the two types of device the kernel requires before being able to use the device driver model. The Device Tree infrastructure makes it very easy to make these discoverable by the rest of the kernel. For example, each interrupt controller driver has at least one entry like this: IRQCHIP_DECLARE(gic_400, "arm,gic-400", gic_of_init); which says: if you find a node having "arm,gic-400" as a compatible string in the device tree, then call gic_of_init with this node as a parameter. The probing itself is done by the OF layer when the architecture code calls of_irq_init() (usually via irqchip_init). This has a number of benefits: - The irqchip code is self-contained. No architecture specific entry point, no exposed symbols. Just a standard interface. - The low-level architecture code doesn't have to know about which interrupt controller is present. It just calls into the firmware interface (of_irq_init) which is going to sort things out. Similar infrastructure is provided for the timers/clock sources. Note that this is not a replacement for the device model, but acts as a probing infrastructure for things that are required too early for the device infrastructure to be available. What I'm aiming for is to introduce the same level of abstraction for ACPI, or at least for the few bits that are required before a full blown ACPI/device model can be used. For this, I introduce something vaguely similar: IRQCHIP_ACPI_DECLARE(gic_v2, ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR, gic_validate_dist, ACPI_MADT_GIC_VERSION_V2, gic_v2_acpi_init); which says: if you find a ACPI_MADT_TYPE_GENERIC_DISTRIBUTOR entry in MADT (implied by the macro), and that entry is of type ACPI_MADT_GIC_VERSION_V2 (as checked by gic_validate_dist), then call gic_v2_acpi_init with the entry as a parameter. A bit more convoluted, but still without any special entry point. The various interrupt controller drivers can then implement the above, and the arch code can use a firmware-specific call to get the probing done, still oblivious to what interrupt controller is being used. It also makes the adaptation of a DT driver to ACPI easier. It turns out that providing such a probing infrastructure is rather easy, and provides a much deserved cleanup in both the arch code, the GIC driver, and the architected timer driver. An additional (and very much optional) patch renames files and symbols to make it obvious that the infrastructure is not just for DT anymore. I'm sure there is some more code to be deleted, and one can only wonder why this wasn't done before the arm64 code was initially merged (the diffstat says it all...). Patches are against Rafael's bleeding-edge branch, and a branch is available at git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git acpi/device-probing-v3 * From v2: - Addressed Rafael's comments (title for patch #1, macro/field names) - New config symbols for clocksources - Additional and optional last patch to get rid of the apparent dependency between the probing infrastructure and DT. * From the initial version: - Make the infrastructure more DT like by providing an acpi_probe_entry array per "device type" (one for irqchips, one for clocksources). This means that entries can depend on any ACPI static table. - Use some cpp magic to reduce the amount of code added to an absolute minimum. - Rebased on v4.3-rc1 Marc Zyngier (7): acpi: Add early device probing infrastructure irqchip/acpi: Add probing infrastructure for ACPI-based irqchips irqchip/gic: Convert the GIC driver to ACPI probing clocksource/acpi: Add probing infrastructure for ACPI-based clocksources clocksource: Add new CLKSRC_{PROBE,ACPI} config symbols clocksource/arm_arch_timer: Convert to ACPI probing clocksource: cosmetic: Drop OF 'dependency' from symbols arch/arm/kernel/time.c | 2 +- arch/arm/mach-omap2/timer.c | 4 +- arch/arm/mach-rockchip/rockchip.c | 2 +- arch/arm/mach-shmobile/setup-r8a7779.c | 2 +- arch/arm/mach-shmobile/setup-rcar-gen2.c | 2 +- arch/arm/mach-spear/spear13xx.c | 2 +- arch/arm/mach-sunxi/sunxi.c | 2 +- arch/arm/mach-u300/core.c | 2 +- arch/arm/mach-ux500/timer.c | 2 +- arch/arm/mach-zynq/common.c | 2 +- arch/arm64/include/asm/acpi.h | 1 - arch/arm64/include/asm/irq.h | 13 ---- arch/arm64/kernel/acpi.c | 25 -------- arch/arm64/kernel/time.c | 8 +-- arch/microblaze/kernel/setup.c | 2 +- arch/mips/pistachio/time.c | 2 +- arch/mips/ralink/clk.c | 2 +- arch/nios2/kernel/time.c | 2 +- arch/xtensa/kernel/time.c | 2 +- drivers/acpi/scan.c | 39 ++++++++++++ drivers/clocksource/Kconfig | 9 +++ drivers/clocksource/Makefile | 2 +- drivers/clocksource/arm_arch_timer.c | 10 +--- .../clocksource/{clksrc-of.c => clksrc-probe.c} | 6 +- drivers/irqchip/irq-gic.c | 69 +++++++++++----------- drivers/irqchip/irqchip.c | 5 +- include/asm-generic/vmlinux.lds.h | 12 ++++ include/linux/acpi.h | 66 +++++++++++++++++++++ include/linux/acpi_irq.h | 10 ---- include/linux/clocksource.h | 13 ++-- include/linux/irqchip.h | 17 ++++++ include/linux/irqchip/arm-gic-acpi.h | 31 ---------- 32 files changed, 209 insertions(+), 159 deletions(-) rename drivers/clocksource/{clksrc-of.c => clksrc-probe.c} (91%) delete mode 100644 include/linux/acpi_irq.h delete mode 100644 include/linux/irqchip/arm-gic-acpi.h -- 2.1.4

9 years, 7 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Linaro-acpi October 2015