mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yu, Luming" <luming.yu@intel.com>
To: "Theodore Ts'o" <tytso@mit.edu>, "Brown, Len" <len.brown@intel.com>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>,
	"Moore, Robert" <robert.moore@intel.com>,
	"Alex Williamson" <alex.williamson@hp.com>,
	"linux-kernel" <linux-kernel@vger.kernel.org>,
	<acpi-devel@lists.sourceforge.net>
Subject: RE: Userspace ACPI interpreter ( was RE: [ACPI] [RFC] dev_acpi: support for userspace access to acpi)
Date: Fri, 29 Oct 2004 10:40:58 +0800	[thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F84041ABFFF@pdsmsx403> (raw)

>
>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?

One reason for kernel-mode interpreter is to live in unpageable memory.

User-mode ACPI interpreter advantages:

1. Without losing platform functionality, user-mode interpreter
can make kernel less complex, thus more stronger.

2. Kernel can release from AML issues.
...

Thanks,
Luming

             reply	other threads:[~2004-10-29  2:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29  2:40 Yu, Luming [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-29  2:51 Yu, Luming
2004-10-31 21:29 ` Pavel Machek
2004-10-28  4:04 Yu, Luming
2004-10-28  5:37 ` Len Brown
2004-10-28 15:24   ` Theodore Ts'o
2004-10-29  4:48     ` Len Brown
2004-10-29  4:58       ` Andi Kleen
2004-10-28 15:18 ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ACA40606221794F80A5670F0AF15F84041ABFFF@pdsmsx403 \
    --to=luming.yu@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=alex.williamson@hp.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.moore@intel.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®