summaryrefslogtreecommitdiffstats
path: root/tools/power/acpi/tools/acpidbg/acpidbg.c
diff options
context:
space:
mode:
authorLv Zheng <lv.zheng@intel.com>2015-12-03 10:42:53 +0800
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2015-12-15 00:17:44 +0100
commit8a2a2501a893bfce65af7098a1b0a61f14f95626 (patch)
treeca2fbad37ca7097e75a96b829ad706f3130fa369 /tools/power/acpi/tools/acpidbg/acpidbg.c
parentf8d31489629c125806ce4bf587c0c5c284d6d113 (diff)
downloadtalos-op-linux-8a2a2501a893bfce65af7098a1b0a61f14f95626.tar.gz
talos-op-linux-8a2a2501a893bfce65af7098a1b0a61f14f95626.zip
ACPICA: Debugger: Fix runtime stub issues of ACPI_DEBUGGER_EXEC using different stub mechanism
ACPICA commit 11522d6b894054fc4d62dd4f9863ec151296b386 The ACPI_DEBUGGER_EXEC is a problem now when the debugger code is compiled but runtime disabled. They actually will get executed in this situation. Although such executions are harmless if we can correctly make acpi_db_single_step() a runtime stub, users may still do not want to see the debugger print messages logged into OSPMs' kernel logs when a debugger driver is not loaded to enable the debugger during runtime. This patch fixes this issue by introducing new stub mechanism instead of ACPI_DEBUGGER_EXEC. Lv Zheng. Link: https://github.com/acpica/acpica/commit/11522d6b Signed-off-by: Lv Zheng <lv.zheng@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/power/acpi/tools/acpidbg/acpidbg.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud