https://bugzilla.kernel.org/show_bug.cgi?id=97141
--- Comment #12 from Rafael J. Wysocki <[email protected]> --- (In reply to Lv Zheng from comment #8) > I'm OK with BGRT which is a data table, but for TAD which comes from a > definition block table, I do have concerns... > > At this early boot time, PCI configuration space may not be accessible. > Thus some module level code in the ACPI definition block table is also not > executable. > Invoking acpi_load_tables() so early causes a very strange software scheme > in ACPICA. > ACPICA interpreter has to execute only special AML code and ignore all > module level code in this early stage and at a late stage, re-execute the > module level code. This makes ACPICA interpreter implementation very dirty. I'm not sure I understand your point correctly. Do you have any specific examples of what may go wrong as a result of this? -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
