1. 07 Nov, 2008 2 commits
    • Myron Stowe's avatar
      ACPI: Behave uniquely based on processor declaration definition type · b26e9286
      Myron Stowe authored
      Associating a Local SAPIC with a processor object is dependent upon the
      processor object's definition type.  CPUs declared as "Processor" should
      use the Local SAPIC's 'processor_id', and CPUs declared as "Device"
      should use the 'uid'.  Note that for "Processor" declarations, even if a
      '_UID' child object exists, it has no bearing with respect to mapping
      Local SAPICs (see section 5.2.11.13 - Local SAPIC Structure; "Advanced
      Configuration and Power Interface Specification", Revision 3.0b).
      
      This patch changes the lsapic mapping logic to rely on the distinction of
      how the processor object was declared - the mapping can't just try both
      types of matches regardless of declaration type and rely on one failing
      as is currently being done.
      Signed-off-by: default avatarMyron Stowe <myron.stowe@hp.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      b26e9286
    • Myron Stowe's avatar
      ACPI: Disambiguate processor declaration type · ad93a765
      Myron Stowe authored
      Declaring processors in ACPI namespace can be done using either a
      "Processor" definition or a "Device" definition (see section 8.4 -
      Declaring Processors; "Advanced Configuration and Power Interface
      Specification", Revision 3.0b).  Currently the two processor
      declaration types are conflated.
      
      This patch disambiguates the processor declaration's definition type
      enabling subsequent code to behave uniquely based explicitly on the
      declaration's type.
      Signed-off-by: default avatarMyron Stowe <myron.stowe@hp.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      ad93a765
  2. 03 Nov, 2008 19 commits
  3. 02 Nov, 2008 19 commits