https://bugzilla.kernel.org/show_bug.cgi?id=97141
--- Comment #9 from Lee, Chun-Yi <[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. > > Thanks > -Lv I fully agree your point. But if TAD could not access earlier before timekeeping_init(), then kernel can not use TAD to set system clock. That causes kernel accessing another RTC interface, like: EFI time service. Unfortunately the EFI time service is unreliable at run time so we avoid using it. Using EFI time service to get the offset in EFI stub maybe works, that need time to implement and check. -- 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
