This project is mirrored from https://git.kernel.org/pub/scm/linux/kernel/git/wagi/linux-cip-rt.git. The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 22 Mar, 2012 2 commits
  2. 21 Jan, 2012 1 commit
    • Myron Stowe's avatar
      ACPI, APEI: Add 64-bit read/write support for APEI on i386 · e615bf5b
      Myron Stowe authored
      Base ACPI (CA) currently does not support atomic 64-bit reads and writes
      (acpi_read() and acpi_write() split 64-bit loads/stores into two
      32-bit transfers) yet APEI expects 64-bit transfer capability, even
      when running on 32-bit systems.
      
      This patch implements 64-bit read and write routines for APEI usage.
      
      This patch re-factors similar functionality introduced in commit
      04c25997, bringing it into the ACPI subsystem in preparation for
      removing ./drivers/acpi/atomicio.[ch].  In the implementation I have
      replicated acpi_os_read_memory() and acpi_os_write_memory(), creating
      64-bit versions for APEI to utilize, as opposed to something more
      elegant.  My thinking is that we should attempt to see if we can get
      ACPI's CA/OSL changed so that the existing acpi_read() and acpi_write()
      interfaces are natively 64-bit capable and then subsequently remove the
      replication.
      Signed-off-by: default avatarMyron Stowe <myron.stowe@redhat.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      e615bf5b
  3. 17 Jan, 2012 1 commit
  4. 14 Oct, 2011 1 commit
    • Prarit Bhargava's avatar
      PCI hotplug: acpiphp: Prevent deadlock on PCI-to-PCI bridge remove · 6af8bef1
      Prarit Bhargava authored
      I originally submitted a patch to workaround this by pushing all Ejection
      Requests and Device Checks onto the kacpi_hotplug queue.
      
      http://marc.info/?l=linux-acpi&m=131678270930105&w=2
      
      The patch is still insufficient in that Bus Checks also need to be added.
      
      Rather than add all events, including non-PCI-hotplug events, to the
      hotplug queue, mjg suggested that a better approach would be to modify
      the acpiphp driver so only acpiphp events would be added to the
      kacpi_hotplug queue.
      
      It's a longer patch, but at least we maintain the benefit of having separate
      queues in ACPI.  This, of course, is still only a workaround the problem.
      As Bjorn and mjg pointed out, we have to refactor a lot of this code to do
      the right thing but at this point it is a better to have this code working.
      
      The acpi core places all events on the kacpi_notify queue.  When the acpiphp
      driver is loaded and a PCI card with a PCI-to-PCI bridge is removed the
      following call sequence occurs:
      
      cleanup_p2p_bridge()
      	    -> cleanup_bridge()
      		    -> acpi_remove_notify_handler()
      			    -> acpi_os_wait_events_complete()
      				    -> flush_workqueue(kacpi_notify_wq)
      
      which is the queue we are currently executing on and the process will hang.
      
      Move all hotplug acpiphp events onto the kacpi_hotplug workqueue.  In
      handle_hotplug_event_bridge() and handle_hotplug_event_func() we can simply
      push the rest of the work onto the kacpi_hotplug queue and then avoid the
      deadlock.
      Signed-off-by: Prarit Bhargava's avatarPrarit Bhargava <prarit@redhat.com>
      Cc: mjg@redhat.com
      Cc: bhelgaas@google.com
      Cc: linux-acpi@vger.kernel.org
      Signed-off-by: default avatarJesse Barnes <jbarnes@virtuousgeek.org>
      6af8bef1
  5. 13 Jul, 2011 1 commit
  6. 25 Mar, 2011 1 commit
  7. 19 Jan, 2011 1 commit
  8. 19 Oct, 2010 1 commit
  9. 01 Oct, 2010 3 commits
  10. 06 May, 2010 1 commit
  11. 22 Jan, 2010 2 commits
  12. 27 Aug, 2009 1 commit
    • Lin Ming's avatar
      ACPICA: fix leak of acpi_os_validate_address · a5fe1a03
      Lin Ming authored
      http://bugzilla.kernel.org/show_bug.cgi?id=13620
      
      If the dynamic region is created and added to resource list over and over again,
      it has the potential to be a memory leak by growing the list every time.
      
      This patch fixes the memory leak, as below
      
      1) add a new field "count" to struct acpi_res_list.
      
         When inserting, if the region(addr, len) is already in the resource
         list, we just increase "count", otherwise, the region is inserted
         with count=1.
      
         When deleting, the "count" is decreased, if it's decreased to 0,
         the region is deleted from the resource list.
      
         With "count", the region with same address and length can only be
         inserted to the resource list once, so prevent potential memory leak.
      
      2) add a new function acpi_os_invalidate_address, which is called when
         region is deleted.
      Signed-off-by: default avatarLin Ming <ming.m.lin@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      a5fe1a03
  13. 27 Jul, 2009 1 commit
  14. 27 Mar, 2009 1 commit
  15. 09 Feb, 2009 1 commit
    • Yinghai Lu's avatar
      acpi/x86: introduce __apci_map_table, v4 · 7d97277b
      Yinghai Lu authored
      to prevent wrongly overwriting fixmap that still want to use.
      
      ACPI used to rely on low mappings being all linearly mapped and
      grew a habit: it never really unmapped certain kinds of tables
      after use.
      
      This can cause problems - for example the hypothetical case
      when some spurious access still references it.
      
      v2: remove prev_map and prev_size in __apci_map_table
      v3: let acpi_os_unmap_memory() call early_iounmap too, so remove extral calling to
      early_acpi_os_unmap_memory
      v4: fix typo in one acpi_get_table_with_size calling
      Signed-off-by: default avatarYinghai Lu <yhlu.kernel@gmail.com>
      Acked-by: default avatarLen Brown <len.brown@intel.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      7d97277b
  16. 31 Dec, 2008 1 commit
  17. 24 Sep, 2008 1 commit
    • Zhang Rui's avatar
      ACPI: fix hotplug race · 19cd847a
      Zhang Rui authored
      The hotplug notification handler and drivers' notification handler all
      run in one workqueue.  Before hotplug removes an acpi device, the
      device driver's notification handler is already be recorded to run just
      after global notification handler.  After hotplug notification handler
      runs, acpica will notice a NULL notification handler and crash.
      
      So now we run run hotplug in another workqueue and wait
      for all acpi notication handlers finish.
      This was found in battery hotplug, but actually all
      hotplug can be affected.
      Signed-off-by: default avatarZhang Rui <rui.zhang@intel.com>
      Signed-off-by: default avatarShaohua Li <shaohua.li@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      19cd847a
  18. 16 Jul, 2008 1 commit
  19. 24 Apr, 2008 1 commit
  20. 13 Feb, 2008 1 commit
  21. 07 Feb, 2008 2 commits
    • Thomas Renninger's avatar
      ACPI: track opregion names to avoid driver resource conflicts. · df92e695
      Thomas Renninger authored
      Small ACPICA extension to be able to store the name of operation regions in osl.c later
      
      In ACPI, AML can define accesses to IO ports and System Memory by Operation
      Regions.  Those are not registered as done by PNPACPI using resource templates
      (and _CRS/_SRS methods).
      
      The IO ports and System Memory regions may get accessed by arbitrary AML code.
       When native drivers are accessing the same resources bad things can happen
      (e.g.  a critical shutdown temperature of 3000 C every 2 months or so).
      
      It is not really possible to register the operation regions via
      request_resource, as they often overlap with pnp or other resources (e.g.
      statically setup IO resources below 0x100).
      
      This approach stores all Operation Region declarations (IO and System Memory
      only) at ACPI table parse time.  It offers a similar functionality like
      request_region and let drivers which are known to possibly use the same IO
      ports and Memory which are also often used by ACPI (hwmon and i2c) check for
      ACPI interference.
      
      A boot parameter acpi_enforce_resources=strict/lax/no is provided, which
      is default set to lax:
        - strict: let conflicting drivers fail to load with an error message
        - lax:    let conflicting driver work normal with a warning message
        - no:     no functional change at all
      Depending on the feedback and the kind of interferences we see, this
      should be set to strict at later time.
      
      Goal of this patch set is:
        - Identify ACPI interferences in bug reports (very hard to reproduce
          and to identify)
        - Find BIOSes for that an ACPI driver should exist for specific HW
          instead of a native one.
        - stability in general
      
      Provide acpi_check_{mem_}region.
      
      Drivers can additionally check against possible ACPI interference by also
      invoking this shortly before they call request_region.
      If -EBUSY is returned, the driver must not load.
      Use acpi_enforce_resources=strict/lax/no options to:
        - strict: let conflicting drivers fail to load with an error message
        - lax:    let conflicting driver work normal with a warning message
        - no:     no functional change at all
      
      Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>
      Cc: Jean Delvare <khali@linux-fr.org>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: Thomas Renninger's avatarThomas Renninger <trenn@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      df92e695
    • Len Brown's avatar
      ACPI: create /sys/firmware/acpi/interrupts · 5229e87d
      Len Brown authored
      See Documentation/ABI/testing/sysfs-firmware-acpi
      Based-on-original-patch-by: default avatarLuming Yu <luming.yu@intel.com>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      5229e87d
  22. 30 May, 2007 1 commit
  23. 29 May, 2007 1 commit
    • Len Brown's avatar
      ACPI: extend "acpi_osi=" boot option · ae00d812
      Len Brown authored
      The boot option "acpi_osi=" has always disabled Linux _OSI support,
      thus disabling all OS Interface strings which are advertised
      by Linux to the BIOS.
      
      Now...
      acpi_osi="string" adds the interface string, and
      acpi_osi="!string" invalidates the pre-defined interface string
      
      eg. acpi_osi="!Windows 2006"
      would disable Linux's claim of Vista compatibility.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      ae00d812
  24. 10 May, 2007 1 commit
  25. 16 Feb, 2007 1 commit
  26. 03 Feb, 2007 2 commits
  27. 30 Jun, 2006 1 commit
  28. 28 Jun, 2006 1 commit
    • Bob Moore's avatar
      ACPI: ACPICA 20060623 · 967440e3
      Bob Moore authored
      Implemented a new acpi_spinlock type for the OSL lock
      interfaces.  This allows the type to be customized to
      the host OS for improved efficiency (since a spinlock is
      usually a very small object.)
      
      Implemented support for "ignored" bits in the ACPI
      registers.  According to the ACPI specification, these
      bits should be preserved when writing the registers via
      a read/modify/write cycle. There are 3 bits preserved
      in this manner: PM1_CONTROL[0] (SCI_EN), PM1_CONTROL[9],
      and PM1_STATUS[11].
      http://bugzilla.kernel.org/show_bug.cgi?id=3691
      
      Implemented the initial deployment of new OSL mutex
      interfaces.  Since some host operating systems have
      separate mutex and semaphore objects, this feature was
      requested. The base code now uses mutexes (and the new
      mutex interfaces) wherever a binary semaphore was used
      previously. However, for the current release, the mutex
      interfaces are defined as macros to map them to the
      existing semaphore interfaces.
      
      Fixed several problems with the support for the control
      method SyncLevel parameter. The SyncLevel now works
      according to the ACPI specification and in concert with the
      Mutex SyncLevel parameter, since the current SyncLevel is
      a property of the executing thread. Mutual exclusion for
      control methods is now implemented with a mutex instead
      of a semaphore.
      
      Fixed three instances of the use of the C shift operator
      in the bitfield support code (exfldio.c) to avoid the use
      of a shift value larger than the target data width. The
      behavior of C compilers is undefined in this case and can
      cause unpredictable results, and therefore the case must
      be detected and avoided.  (Fiodor Suietov)
      
      Added an info message whenever an SSDT or OEM table
      is loaded dynamically via the Load() or LoadTable()
      ASL operators. This should improve debugging capability
      since it will show exactly what tables have been loaded
      (beyond the tables present in the RSDT/XSDT.)
      Signed-off-by: default avatarBob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      967440e3
  29. 14 Jun, 2006 4 commits
    • Bob Moore's avatar
      ACPI: ACPICA 20060526 · 4119532c
      Bob Moore authored
      Restructured, flattened, and simplified the internal
      interfaces for namespace object evaluation - resulting
      in smaller code, less CPU stack use, and fewer
      interfaces. (With assistance from Mikhail Kouzmich)
      
      Fixed a problem with the CopyObject operator where the
      first parameter was not typed correctly for the parser,
      interpreter, compiler, and disassembler. Caused various
      errors and unexpected behavior.
      
      Fixed a problem where a ShiftLeft or ShiftRight of
      more than 64 bits produced incorrect results with some
      C compilers. Since the behavior of C compilers when
      the shift value is larger than the datatype width is
      apparently not well defined, the interpreter now detects
      this condition and simply returns zero as expected in all
      such cases. (BZ 395)
      
      Fixed problem reports (Valery Podrezov) integrated: -
      Update String-to-Integer conversion to match ACPI 3.0A spec
      http://bugzilla.kernel.org/show_bug.cgi?id=5329
      Allow interpreter to handle nested method declarations
      http://bugzilla.kernel.org/show_bug.cgi?id=5361
      
      Fixed problem reports (Fiodor Suietov) integrated: -
      acpi_terminate() doesn't free debug memory allocation
      list objects (BZ 355) - After Core Subsystem
      shutdown, acpi_subsystem_status() returns AE_OK (BZ 356) -
      acpi_os_unmap_memory() for RSDP can be invoked inconsistently
      (BZ 357) - Resource Manager should return AE_TYPE for
      non-device objects (BZ 358) - Incomplete cleanup branch
      in AcpiNsEvaluateRelative (BZ 359) - Use acpi_os_free()
      instead of ACPI_FREE in acpi_rs_set_srs_method_data (BZ 360)
      - Incomplete cleanup branch in acpi_ps_parse_aml (BZ 361) -
      Incomplete cleanup branch in acpi_ds_delete_walk_state (BZ 362)
      - acpi_get_table_header returns AE_NO_ACPI_TABLES until DSDT
      is loaded (BZ 365) - Status of the Global Initialization
      Handler call not used (BZ 366) - Incorrect object parameter
      to Global Initialization Handler (BZ 367)
      Signed-off-by: default avatarBob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      4119532c
    • Bob Moore's avatar
      ACPI: ACPICA 20060512 · 958dd242
      Bob Moore authored
      Replaced the acpi_os_queue_for_execution() with a new
      interface named acpi_os_execute(). The major difference is
      that the new interface does not have a Priority parameter,
      this appeared to be useless and has been replaced by
      a Type parameter. The Type tells the OS what type of
      execution is being requested, such as global lock handler,
      notify handler, GPE handler, etc. This allows the host
      to queue and execute the request as appropriate for the
      request type, possibly using different work queues and
      different priorities for the various request types. This
      enables fixes for multithreading deadlock problems such as
      http://bugzilla.kernel.org/show_bug.cgi?id=5534
      (Alexey Starikovskiy and Bob Moore)
      
      Fixed a possible memory leak associated with the
      support for the so-called "implicit return" ACPI
      extension. Reported by FreeBSD  (Fiodor Suietov)
      http://bugzilla.kernel.org/show_bug.cgi?id=6514
      
      Fixed a problem with the Load() operator where a table
      load from an operation region could overwrite an internal
      table buffer by up to 7 bytes and cause alignment faults
      on IPF systems. (With assistance from Luming Yu)
      Signed-off-by: default avatarBob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      958dd242
    • Bob Moore's avatar
      ACPI: ACPICA 20060421 · b229cf92
      Bob Moore authored
      Removed a device initialization optimization introduced in
      20051216 where the _STA method was not run unless an _INI
      was also present for the same device. This optimization
      could cause problems because it could allow _INI methods
      to be run within a not-present device subtree (If a
      not-present device had no _INI, _STA would not be run,
      the not-present status would not be discovered, and the
      children of the device would be incorrectly traversed.)
      
      Implemented a new _STA optimization where namespace
      subtrees that do not contain _INI are identified and
      ignored during device initialization. Selectively running
      _STA can significantly improve boot time on large machines
      (with assistance from Len Brown.)
      
      Implemented support for the device initialization case
      where the returned _STA flags indicate a device not-present
      but functioning. In this case, _INI is not run, but the
      device children are examined for presence, as per the
      ACPI specification.
      
      Implemented an additional change to the IndexField support
      in order to conform to MS behavior. The value written to
      the Index Register is not simply a byte offset, it is a
      byte offset in units of the access width of the parent
      Index Field. (Fiodor Suietov)
      
      Defined and deployed a new OSL interface,
      acpi_os_validate_address().  This interface is called during
      the creation of all AML operation regions, and allows
      the host OS to exert control over what addresses it will
      allow the AML code to access. Operation Regions whose
      addresses are disallowed will cause a runtime exception
      when they are actually accessed (will not affect or abort
      table loading.)
      
      Defined and deployed a new OSL interface,
      acpi_os_validate_interface().  This interface allows the host OS
      to match the various "optional" interface/behavior strings
      for the _OSI predefined control method as appropriate
      (with assistance from Bjorn Helgaas.)
      
      Restructured and corrected various problems in the
      exception handling code paths within DsCallControlMethod
      and DsTerminateControlMethod in dsmethod (with assistance
      from Takayoshi Kochi.)
      
      Modified the Linux source converter to ignore quoted string
      literals while converting identifiers from mixed to lower
      case. This will correct problems with the disassembler
      and other areas where such strings must not be modified.
      
      The ACPI_FUNCTION_* macros no longer require quotes around
      the function name. This allows the Linux source converter
      to convert the names, now that the converter ignores
      quoted strings.
      Signed-off-by: default avatarBob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      b229cf92
    • Bob Moore's avatar
      ACPI: ACPICA 20060331 · 793c2388
      Bob Moore authored
      Implemented header file support for the following
      additional ACPI tables: ASF!, BOOT, CPEP, DBGP, MCFG, SPCR,
      SPMI, TCPA, and WDRT. With this support, all current and
      known ACPI tables are now defined in the ACPICA headers and
      are available for use by device drivers and other software.
      
      Implemented support to allow tables that contain ACPI
      names with invalid characters to be loaded. Previously,
      this would cause the table load to fail, but since
      there are several known cases of such tables on
      existing machines, this change was made to enable
      ACPI support for them. Also, this matches the
      behavior of the Microsoft ACPI implementation.
      https://bugzilla.novell.com/show_bug.cgi?id=147621
      
      Fixed a couple regressions introduced during the memory
      optimization in the 20060317 release. The namespace
      node definition required additional reorganization and
      an internal datatype that had been changed to 8-bit was
      restored to 32-bit. (Valery Podrezov)
      
      Fixed a problem where a null pointer passed to
      acpi_ut_delete_generic_state() could be passed through
      to acpi_os_release_object which is unexpected. Such
      null pointers are now trapped and ignored, matching
      the behavior of the previous implementation before the
      deployment of acpi_os_release_object().  (Valery Podrezov,
      Fiodor Suietov)
      
      Fixed a memory mapping leak during the deletion of
      a SystemMemory operation region where a cached memory
      mapping was not deleted. This became a noticeable problem
      for operation regions that are defined within frequently
      used control methods. (Dana Meyers)
      
      Reorganized the ACPI table header files into two main
      files: one for the ACPI tables consumed by the ACPICA core,
      and another for the miscellaneous ACPI tables that are
      consumed by the drivers and other software. The various
      FADT definitions were merged into one common section and
      three different tables (ACPI 1.0, 1.0+, and 2.0)
      Signed-off-by: default avatarBob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      793c2388
  30. 01 Apr, 2006 1 commit
    • Bob Moore's avatar
      ACPI: ACPICA 20060310 · 8313524a
      Bob Moore authored
      Tagged all external interfaces to the subsystem with the
      new ACPI_EXPORT_SYMBOL macro. This macro can be defined
      as necessary to assist kernel integration. For Linux,
      the macro resolves to the EXPORT_SYMBOL macro. The default
      definition is NULL.
      
      Added the ACPI_THREAD_ID type for the return value from
      acpi_os_get_thread_id(). This allows the host to define this
      as necessary to simplify kernel integration. The default
      definition is ACPI_NATIVE_UINT.
      
      Valery Podrezov fixed two interpreter problems related
      to error processing, the deletion of objects, and placing
      invalid pointers onto the internal operator result stack.
      http://bugzilla.kernel.org/show_bug.cgi?id=6028
      http://bugzilla.kernel.org/show_bug.cgi?id=6151
      
      Increased the reference count threshold where a warning is
      emitted for large reference counts in order to eliminate
      unnecessary warnings on systems with large namespaces
      (especially 64-bit.) Increased the value from 0x400
      to 0x800.
      
      Due to universal disagreement as to the meaning of the
      'c' in the calloc() function, the ACPI_MEM_CALLOCATE
      macro has been renamed to ACPI_ALLOCATE_ZEROED so that the
      purpose of the interface is 'clear'. ACPI_MEM_ALLOCATE and
      ACPI_MEM_FREE are renamed to ACPI_ALLOCATE and ACPI_FREE.
      Signed-off-by: default avatarBob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      8313524a
  31. 31 Jan, 2006 1 commit
    • Bob Moore's avatar
      [ACPI] ACPICA 20060127 · b8e4d893
      Bob Moore authored
      Implemented support in the Resource Manager to allow
      unresolved namestring references within resource package
      objects for the _PRT method. This support is in addition
      to the previously implemented unresolved reference
      support within the AML parser. If the interpreter slack
      mode is enabled (true on Linux unless acpi=strict),
      these unresolved references will be passed through
      to the caller as a NULL package entry.
      http://bugzilla.kernel.org/show_bug.cgi?id=5741
      
      Implemented and deployed new macros and functions for
      error and warning messages across the subsystem. These
      macros are simpler and generate less code than their
      predecessors. The new macros ACPI_ERROR, ACPI_EXCEPTION,
      ACPI_WARNING, and ACPI_INFO replace the ACPI_REPORT_*
      macros.
      
      Implemented the acpi_cpu_flags type to simplify host OS
      integration of the Acquire/Release Lock OSL interfaces.
      Suggested by Steven Rostedt and Andrew Morton.
      
      Fixed a problem where Alias ASL operators are sometimes
      not correctly resolved. causing AE_AML_INTERNAL
      http://bugzilla.kernel.org/show_bug.cgi?id=5189
      http://bugzilla.kernel.org/show_bug.cgi?id=5674
      
      Fixed several problems with the implementation of the
      ConcatenateResTemplate ASL operator. As per the ACPI
      specification, zero length buffers are now treated as a
      single EndTag. One-length buffers always cause a fatal
      exception. Non-zero length buffers that do not end with
      a full 2-byte EndTag cause a fatal exception.
      
      Fixed a possible structure overwrite in the
      AcpiGetObjectInfo external interface. (With assistance
      from Thomas Renninger)
      Signed-off-by: default avatarBob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      b8e4d893