.TH ACPIDUMP 8 .SH NAME acpidump \- dump a system's ACPI tables to an ASCII file .SH SYNOPSIS .B acpidump .RI [ options ] .br .SH DESCRIPTION .B acpidump dumps the systems ACPI tables to an ASCII file appropriate for attaching to a bug report. Subsequently, they can be processed by utilities in the ACPICA package. .SH OPTIONS acpidump options are as follow: .TP .B Options .TP .B \-b Dump tables to binary files .TP .B \-h \-? This help message .TP .B \-o Redirect output to file .TP .B \-r
Dump tables from specified RSDP .TP .B \-s Print table summaries only .TP .B \-v Display version information .TP .B \-z Verbose mode .TP .B Table Options .TP .B \-a
Get table via a physical address .TP .B \-c Turning on/off customized table dumping .TP .B \-f Get table via a binary file .TP .B \-n Get table via a name/signature .TP .B \-x Do not use but dump XSDT .TP .B \-x \-x Do not use or dump XSDT .TP .fi Invocation without parameters dumps all available tables. .TP Multiple mixed instances of -a, -f, and -n are supported. .SH EXAMPLES .nf # acpidump > acpidump.out $ acpixtract -a acpidump.out Acpi table [DSDT] - 15974 bytes written to DSDT.dat Acpi table [FACS] - 64 bytes written to FACS.dat Acpi table [FACP] - 116 bytes written to FACP.dat Acpi table [APIC] - 120 bytes written to APIC.dat Acpi table [MCFG] - 60 bytes written to MCFG.dat Acpi table [SSDT] - 444 bytes written to SSDT1.dat Acpi table [SSDT] - 439 bytes written to SSDT2.dat Acpi table [SSDT] - 439 bytes written to SSDT3.dat Acpi table [SSDT] - 439 bytes written to SSDT4.dat Acpi table [SSDT] - 439 bytes written to SSDT5.dat Acpi table [RSDT] - 76 bytes written to RSDT.dat Acpi table [RSDP] - 20 bytes written to RSDP.dat $ iasl -d *.dat ... .fi creates *.dsl, a human readable form which can be edited and compiled using iasl. .SH NOTES .B "acpidump " must be run as root. .SH REFERENCES ACPICA: https://acpica.org/ .SH FILES .ta .nf /dev/mem /sys/firmware/acpi/tables/* /sys/firmware/acpi/tables/dynamic/* /sys/firmware/efi/systab .fi .SH AUTHOR .TP Original by: Len Brown .TP Written by: Chao Guan .TP Updated by: Bob Moore Lv Zheng .SH SEE ALSO \&\fIacpixtract\fR\|(8), \fIiasl\fR\|(8). .SH COPYRIGHT COPYRIGHT (c) 2013, Intel Corporation. input class='txt' type='search' size='10' name='q' value=''/>
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2017-01-31 09:37:34 +0100
committerThomas Gleixner <tglx@linutronix.de>2017-01-31 21:47:58 +0100
commit0becc0ae5b42828785b589f686725ff5bc3b9b25 (patch)
treebe6d0e1f37c38ed0a7dd5da2d4b1e93f0fb43101 /net/openvswitch/Makefile
parent24c2503255d35c269b67162c397a1a1c1e02f6ce (diff)
x86/mce: Make timer handling more robust
Erik reported that on a preproduction hardware a CMCI storm triggers the BUG_ON in add_timer_on(). The reason is that the per CPU MCE timer is started by the CMCI logic before the MCE CPU hotplug callback starts the timer with add_timer_on(). So the timer is already queued which triggers the BUG. Using add_timer_on() is pretty pointless in this code because the timer is strictlty per CPU, initialized as pinned and all operations which arm the timer happen on the CPU to which the timer belongs. Simplify the whole machinery by using mod_timer() instead of add_timer_on() which avoids the problem because mod_timer() can handle already queued timers. Use __start_timer() everywhere so the earliest armed expiry time is preserved. Reported-by: Erik Veijola <erik.veijola@intel.com> Tested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Borislav Petkov <bp@alien8.de> Cc: Tony Luck <tony.luck@intel.com> Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701310936080.3457@nanos Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'net/openvswitch/Makefile')