> Can't the parsing be done in userland (like we do for shutdown), and > just hand over the information to the kernel?
Really, this is my idea. As this way, we can avoid the dirty addressing currently used, and solve this task with a hurdish approach. El lun., 20 abr. 2020 a las 10:25, Samuel Thibault (<samuel.thiba...@gnu.org>) escribió: > Damien Zammit, le lun. 20 avril 2020 12:56:55 +1000, a ecrit: > > On 20/4/20 5:39 am, Almudena Garcia wrote: > > > Yes, I know. But, if I want to start the cpu explorating using ACPI > translator, I think that the best way is to create other translator, > instead call to this directly from gnumach. > > > Another problem can be share the reference to lapic with gnumach, once > this have been found in ACPI tables, but this will be a next question. > > > > Almudena, I think you are a little confused between userspace and > gnumach. > > Translators run in userspace. > > I believe the kernel is standalone and if you need access to ACPI in > there, > > you need to include ACPI code in gnumach directly. > > Userland can call the kernel to pass it some information. > > > I have a feeling we are going to need all of acpica incorporated into > gnumach eventually, > > because you need a full ACPI parser for learning the PCI interrupts and > proper shutdown mechanism. > > Can't the parsing be done in userland (like we do for shutdown), and > just hand over the information to the kernel? > > Samuel > >
