path: root/include/acpi/atomicio.h
diff options
authorHuang Ying <ying.huang@intel.com>2010-05-18 14:35:11 +0800
committerLen Brown <len.brown@intel.com>2010-05-19 11:40:03 -0400
commit15651291a2f8c11e7e6a42d8bfde7a213ff13262 (patch)
tree0bbb96e22231e2b4da4ce9b264dfce8c54a52efc /include/acpi/atomicio.h
parente40152ee1e1c7a63f4777791863215e3faa37a86 (diff)
ACPI, IO memory pre-mapping and atomic accessing
Some ACPI IO accessing need to be done in atomic context. For example, APEI ERST operations may be used for permanent storage in hardware error handler. That is, it may be called in atomic contexts such as IRQ or NMI, etc. And, ERST/EINJ implement their operations via IO memory/port accessing. But the IO memory accessing method provided by ACPI (acpi_read/acpi_write) maps the IO memory during it is accessed, so it can not be used in atomic context. To solve the issue, the IO memory should be pre-mapped during EINJ/ERST initializing. A linked list is used to record which memory area has been mapped, when memory is accessed in hardware error handler, search the linked list for the mapped virtual address from the given physical address. Signed-off-by: Huang Ying <ying.huang@intel.com> Signed-off-by: Andi Kleen <ak@linux.intel.com> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'include/acpi/atomicio.h')
1 files changed, 10 insertions, 0 deletions
diff --git a/include/acpi/atomicio.h b/include/acpi/atomicio.h
new file mode 100644
index 00000000000..8b9fb4b0b9c
--- /dev/null
+++ b/include/acpi/atomicio.h
@@ -0,0 +1,10 @@
+int acpi_pre_map_gar(struct acpi_generic_address *reg);
+int acpi_post_unmap_gar(struct acpi_generic_address *reg);
+int acpi_atomic_read(u64 *val, struct acpi_generic_address *reg);
+int acpi_atomic_write(u64 val, struct acpi_generic_address *reg);