1. 24 7月, 2015 5 次提交
    • L
      ACPICA: Executer: Add interpreter tracing mode for method tracing facility · ab6c5733
      Lv Zheng 提交于
      ACPICA commit 07fffd02607685b655ed92ee15c160e6a810b60b
      
      The acpi_debug_trace() is the mechanism known as ACPI method tracing that is
      used by Linux as ACPICA debugging message reducer. This facility can be
      controlled through Linux ACPI subsystem - /sys/module/acpi/parameters.
      This facility requires CONFIG_ACPI_DEBUG to be enabled to see ACPICA trace
      logs in the kernel dmesg output.
      
      This patch enhances acpi_debug_trace() to make it not only a message reducer,
      but a real tracer to trace AML interpreter execution. Note that in addition
      to the AML tracer enabling, this patch also updates the facility with the
      following enhancements:
      1. Allow a full path to be specified by the acpi_debug_trace() API.
      2. Allow any method rather than just the entrance of acpi_evaluate_object()
         to be traced.
      3. All interpreter ACPI_LV_TRACE_POINT messages are collected for
         ACPI_EXECUTER layer.
      
      The Makefile of drivers/acpi/acpica is also updated to include exdebug.o
      and the duplicated stubs are removed after that.
      
      Note that since this patch has enhanced the method tracing facility, Linux
      need also be updated after applying this patch. Lv Zheng.
      
      Link: https://github.com/acpica/acpica/commit/07fffd02Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      ab6c5733
    • L
      ACPICA: Dispatcher: Add trace support for interpreter · a616dc2f
      Lv Zheng 提交于
      ACPICA commit 71299ec8b49054daace0df50268e8e055654ca37
      
      This patch adds trace point at the following point:
       1. Begin/end of a control method execution;
       2. Begin/end of an opcode execution.
      
      The trace point feature can be enabled by defining ACPI_DEBUG_OUTPUT
      and specifying a debug level that includes ACPI_LV_TRACDE_POINT and the
      debug layers that include ACPI_PARSER and ACPI_DISPACTCHER.
      
      In order to make aml_op_name of union acpi_parse_object usable for tracer, it is
      enabled for ACPI_DEBUG_OUTPUT in this patch. Lv Zheng.
      
      Link: https://github.com/acpica/acpica/commit/71299ec8Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      a616dc2f
    • L
      ACPICA: Dispatcher: Move stack traversal code to dispatcher · 0bac4295
      Lv Zheng 提交于
      ACPICA commit c8275e243b58fd4adfc0362bd704af41ed14bc75
      
      This patch moves parts of acpi_dm_dump_method_info() to the dispatcher
      component.
      
      This patch also makes the new function dependent on ACPI_DEBUG_OUTPUT
      compile-stage definition so that it can be used by the trace facility.
      
      acpi_dm_dump_method_info() traverses method stack when an exception is
      encountered. Such traversal is needed to support method tracing for the
      exceptions. When an exception is encountered, the end indications of the
      aborted methods should be logged in order not to break the user space
      analysis tool. Lv Zheng.
      
      Link: https://github.com/acpica/acpica/commit/c8275e24Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      0bac4295
    • L
      ACPICA: Dispatcher: Cleanup union acpi_operand_object's AML address assignments · 62eb935b
      Lv Zheng 提交于
      ACPICA commit afb52611dbe7403551f93504d3798534f5c343f4
      
      This patch cleans up the code of assigning the AML address to the
      union acpi_operand_object.
      
      The idea behind this cleanup is:
      The AML address of the union acpi_operand_object should always be determined at
      the point where the object is encountered. It should be started from the
      first byte of the object. For example, the opcode of the object, the name
      string of the user_term object, or the first byte of the packaged object
      (where a pkg_length is prefixed). So it's not cleaner to have it assigned
      here and there in the entire ACPICA source tree.
      
      There are some special cases for the internal opcodes, before cleaning up
      the internal opcodes, we should also determine the rules for the AML
      addresses of the internal opcodes:
      1. INT_NAMEPATH_OP: the address of the first byte for the name_string.
      2. INT_METHODCALL_OP: the address of the first byte for the name_string.
      3. INT_BYTELIST_OP: the address of the first byte for the byte_data list.
      4. INT_EVAL_SUBTREE_OP: the address of the first byte for the
                              Region/Package/Buffer/bank_field/Field arguments.
      5. INT_NAMEDFIELD_OP: the address to the name_seg.
      6. INT_RESERVEDFIELD_OP: the address to the 0x00 prefix.
      7. INT_ACCESSFIELD_OP: the address to the 0x01 prefix.
      8. INT_CONNECTION_OP: the address to the 0x02 prefix.
      9: INT_EXTACCESSFIELD_OP: the address to the 0x03 prefix.
      10.INT_RETURN_VALUE_OP: the address of the replaced operand.
      11.computational_data: the address to the
                            Byte/Word/Dword/Qword/string_prefix.
      
      Before cleaning up the internal root scope of the aml_walk, turning it into
      the term_list, we need to remember the aml_start address as the "Aml"
      attribute for the union acpi_operand_object created by acpi_ps_create_scope_op().
      
      Finally, we can delete some redundant AML address assignment in psloop.c.
      
      Link: https://github.com/acpica/acpica/commit/afb52611Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      62eb935b
    • L
      ACPICA: Parser: Cleanup aml_offset in struct acpi_walk_state · 83482f75
      Lv Zheng 提交于
      ACPICA commit d254405814495058276c0c2f9d96794d15a6c91c
      
      This patch converts aml_offset in struct acpi_walk_state to AML address.
      
      AML offset is actually only used by the debugger, using AML address is more
      direct and efficient during the parsing stage so that we don't need to
      calculate it during the parsing stage.
      
      On the other hand, we can see several issues in the current parser logic
      around the aml_offset:
      1. union acpi_operand_object.Common.aml_offset is redundantly assigned in
         acpi_ps_parse_loop().
      2. aml_offset is not an indication of the offset from the table header but
         the offset from the entry of a list of objects. Sometimes, it indicates
         an entry for a Method/Package/Buffer, which makes it difficult to be
         reversely calculated to a table header offset.
      3. When being used with method tracers (for example, Linux function trace),
         it's better to have AML address logged instead of the AML offset because
         the address is the only attribute that can uniquely identify the opcode.
      This patch is required to solve the above issues. Lv Zheng.
      
      Link: https://github.com/acpica/acpica/commit/d2544058Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      83482f75
  2. 22 5月, 2015 1 次提交
  3. 05 2月, 2015 1 次提交
  4. 26 3月, 2014 3 次提交
  5. 11 2月, 2014 1 次提交
  6. 31 10月, 2013 2 次提交
  7. 25 1月, 2013 1 次提交
  8. 10 1月, 2013 3 次提交
  9. 15 11月, 2012 1 次提交
  10. 17 7月, 2012 1 次提交
  11. 17 1月, 2012 1 次提交
  12. 19 1月, 2011 2 次提交
  13. 01 10月, 2010 1 次提交
  14. 07 7月, 2010 2 次提交
  15. 20 4月, 2010 1 次提交
  16. 23 1月, 2010 1 次提交
  17. 16 12月, 2009 1 次提交
  18. 29 8月, 2009 1 次提交
  19. 09 1月, 2009 3 次提交
  20. 31 12月, 2008 1 次提交
  21. 30 12月, 2008 1 次提交
  22. 23 10月, 2008 1 次提交
  23. 17 7月, 2008 1 次提交
  24. 23 5月, 2008 1 次提交
  25. 24 4月, 2008 1 次提交
  26. 23 4月, 2008 2 次提交