mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Therien, Guy" <guy.therien@intel.com>
To: "Grover, Andrew" <andrew.grover@intel.com>,
	"'lwn@lwn.net'" <lwn@lwn.net>
Cc: "Acpi-linux (E-mail)" <acpi-devel@lists.sourceforge.net>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: [ACPI] ACPI mentioned on lwn.net/kernel
Date: Thu, 24 Jan 2002 18:15:36 -0800	[thread overview]
Message-ID: <D9223EB959A5D511A98F00508B68C20C048758BC@ORSMSX108> (raw)

I'll add that contrary to your statement, EVERY other OS with ACPI support
has it in their kernel. 
Since Linux APM support calls the APM BIOS, which is not easily changed, and
ACPI calls AML that you can capture and change to fix any problems
discovered using available tools, I'd say you were off with the statement
about "an interpreter that can run arbitrary, closed source code" also. You
can't "configure and dump" if you want runtime configuration and power
management. If you need more info ask on or off the list.
Regards,
ACPIGuy

-----Original Message-----
From: Grover, Andrew [mailto:andrew.grover@intel.com]
Sent: Thursday, January 24, 2002 5:30 PM
To: 'lwn@lwn.net'
Cc: Acpi-linux (E-mail); 'linux-kernel@vger.kernel.org'
Subject: [ACPI] ACPI mentioned on lwn.net/kernel


Hi Jonathan,

As longtime subscribers to acpi-devel know, this seems to come up every few
months, but the criticisms mentioned in this week's lwn.net kernel
development summary (http://lwn.net/2002/0124/kernel.php3) prompt me to
respond, lest my silence be taken for capitulation. ;-)

The concerns seem to be summed up when the article says, "ACPI brings
substantial amounts of kernel bloat, reliability worries, and security
concerns." Let me respond to each of those in reverse order:

1) Security concerns
- I think you mistook some kernel developers' off the cuff comments about
this as being real concerns, rather than trolling me (which is apparently
frightfully easy ;-). ACPI is only concerned with power management and
configuration. It has nothing to do with digital rights management, and that
phrase does not appear anywhere in the 481 page ACPI 2.0 specification. The
word "security" appears only twice.

2) Reliability
- One of ACPI's design goals was actually to reduce the OS's susceptibility
to bad BIOSs, compared to APM. OSs using APM suffer because they must call
into the BIOS -- relinquish control completely -- to perform power
management. Under ACPI this is not the case. For example, to get the current
battery status, the steps the OS must perform are defined by the BIOS.
However, since they are performed by the OS, the OS in fact gains visibility
into the process, and does not ever relinquish control to the BIOS.

3) Bloat
- Optimizing for size (or the various unloading schemes) should wait until
the codebase stabilizes. We're still adding major pieces of functionality.
- 100K really isn't that much, compared to other kernel modules (determined
via "size *.o"), or compared to memory installed on most machines these
days.
- Bloat is compiler-dependent. Compiling the interpreter with MSVC instead
of GCC resulted in a ~40% size decrease.

Anyway, looking towards the future...

Our next release will have preliminary support for PCI IRQ routing via ACPI
(which should solve Jes's problem), along with a complete rewrite of the
ancillary drivers to adopt the new Linux 2.5 driver model. When it is ready
(target: Jan 31st) I'll post on both acpi-devel and linux-kernel. My hope
is, the more people gain familiarity of Linux's ACPI code by testing and
helping in its development, the more we all can accept it on its merits, and
start improving Linux's PnP and power management by using the improved
functionality ACPI provides.

Regards -- Andy


----------------------------
Andrew Grover
Intel/MPG/Mobile Arch Lab
andrew.grover@intel.com


_______________________________________________
Acpi-devel mailing list
Acpi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-devel

             reply	other threads:[~2002-01-25  2:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  2:15 Therien, Guy [this message]
2002-01-25 15:42 Moore, Robert
2002-01-25 15:50 ` Horst von Brand
2002-01-25 16:02   ` Ryan Cumming
2002-01-25 16:15     ` Andreas Schwab
2002-01-25 20:05       ` Ryan Cumming
2002-01-26  1:00       ` Linus Torvalds
2002-01-26  3:41         ` Jamie Lokier
2002-01-26 16:39           ` Martin Eriksson
2002-01-26 16:47             ` Jeff Garzik
2002-01-26 17:48               ` Jamie Lokier
2002-01-26 18:25                 ` Martin Eriksson
2002-01-26 21:42             ` Linus Torvalds
2002-01-30  9:22               ` Andrey Panin
     [not found]                 ` <Pine.LNX.4.33.0201291412590.18804-100000@coffee.psychology.mcmaster.ca>
2002-01-30  8:00                   ` Andrey Panin
2002-01-26 17:33         ` Felix von Leitner
2002-01-26 19:40           ` Florian Weimer
2002-01-27 13:56         ` Martin Dalecki
     [not found] <fa.juevf8v.1u7ubb8@ifi.uio.no>
     [not found] ` <fa.h3u09pv.1v2k3bm@ifi.uio.no>
2002-01-26  2:12   ` Dan Maas
2002-01-26  3:45     ` Jamie Lokier
2002-01-26  4:33       ` Alexander Viro
2002-01-26  4:38         ` Andrew Pimlott
2002-01-26  4:59           ` Jamie Lokier
2002-01-26  5:11         ` Jamie Lokier
     [not found] <200201251550.g0PFoIPa002738@tigger.cs.uni-dortmund.de.suse.lists.linux.kernel>
     [not found] ` <200201250802.32508.bodnar42@phalynx.dhs.org.suse.lists.linux.kernel>
     [not found]   ` <jeelkes8y5.fsf@sykes.suse.de.suse.lists.linux.kernel>
     [not found]     ` <a2sv2s$ge3$1@penguin.transmeta.com.suse.lists.linux.kernel>
     [not found]       ` <20020126034106.F5730@kushida.apsleyroad.org.suse.lists.linux.kernel>
     [not found]         ` <012d01c1a687$faa11120$0201a8c0@HOMER.suse.lists.linux.kernel>
2002-01-26 22:43           ` Andi Kleen
2002-01-27 23:58 Dieter Nützel

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=D9223EB959A5D511A98F00508B68C20C048758BC@ORSMSX108 \
    --to=guy.therien@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    /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®