I've been working on the ACPI CA project for over 6 years, and trust me,
this has been tried before. There are significant reasons for having
the interpreter in the kernel.
You don't really want to page out the interpreter when you are using it
for things like suspend/resume, thermal control, and many other things.
I think we have a list around somewhere with many of the reasons, I will
look for it.
Bob
> -----Original Message-----
> From: Theodore Ts'o [mailto:[email protected]] On Behalf Of Theodore
Ts'o
> Sent: Thursday, October 28, 2004 8:24 AM
> To: Brown, Len
> Cc: Yu, Luming; Bjorn Helgaas; Moore, Robert; Alex Williamson; linux-
> kernel; [email protected]
> Subject: Re: Userspace ACPI interpreter ( was RE: [ACPI] [RFC]
dev_acpi:
> support for userspace access to acpi)
>
> On Thu, Oct 28, 2004 at 01:37:52AM -0400, Len Brown wrote:
> > One way to experiment with a user-mode ACPI interpreter would be to
> > continue to use the kernel-mode interpreter for boot up , and cut
over
> > to the user-mode interpreter at /sbin/init. The kernel-mode
interpreter
> > could be sent the way of free_initmem() which is called just before
> > /sbin/init is invoked.
>
> Is there a significant advantage to doing having a user-mode ACPI
> interpreter? The only advantage I can think of is that the ACPI
> interpreter could now live in pageable memory. Are there any others?
>
> - Ted