Bug 5650 - evalutate Processor._INI after hot-add operation
Summary: evalutate Processor._INI after hot-add operation
Status: REJECTED DOCUMENTED
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Hotplug (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: ykzhao
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-23 11:53 UTC by Len Brown
Modified: 2008-03-03 19:14 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Len Brown 2005-11-23 11:53:03 UTC
Linux to date does not evaluate the Processor._INI
method when a processor is added to a system.
Firmware on future systems will require that it does
for the operation to be successful.
Comment 1 Fu Michael 2007-11-13 23:57:04 UTC
yakui to add this...
Comment 2 ykzhao 2007-12-04 22:13:31 UTC
According to ACPI spec the control method is run only when OSPM load a dscription table.  If the device becomes present after the table has already been loaded, OSPM won't evaluate the _INI method , nor examine the children for _INI method. 
Is it necessary to execute the Processor._INI method when a processor is added to a system if the _INI method is evaluated when the table is loaded dynamically? 
(_INI method is executed in the ACPICA after completing the load of static DSDT/SSDT.)
Comment 3 ykzhao 2008-03-03 19:14:52 UTC
    According to the ACPI spec, the _INI method is only executed only when OSPM loads a decription table. If the device becomes present after the table has already been loaded, OSPM will not evaluate the _INI method, nor examine the children for _INI methods. 
    Based on the above description it seems unnecessary to evaluate the processor._INI after hot-add operation. So the bug will be rejected.
   
    Thanks.
    
    
    

Note You need to log in before you can comment on or make changes to this bug.