From: Andi Kleen <ak@suse.de>
To: Len Brown <len.brown@intel.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Luming Yu <luming.yu@intel.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Robert Moore <robert.moore@intel.com>,
Alex Williamson <alex.williamson@hp.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
ACPI Developers <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 06:58:58 +0200 [thread overview]
Message-ID: <20041029045858.GL11384@wotan.suse.de> (raw)
In-Reply-To: <1099025292.5402.200.camel@d845pe>
> [ It would be sort of neat if we could built the core ACPI support in
> some kind of modular way such that that we could have it at boot-time,
> if we need it, but optionally unload it at run-time if it turned out the
> target system didn't need it. ]
It would be possible with some Makefile hacks. Basically you would need
to objcopy the ACPI object files and rename .text*/.data* to
a different acpi specific name. Then you can give it an special
area in the vmlinux.lds and possibly free it.
I agree with you that it's better kept in the kernel.
> Static Kernel Size:
> text data bss dec hex filename
> 144533 5608 4920 155061 25db5 drivers/acpi/built-in.o
Hmm, this used to be smaller, no? Perhaps someone going over
bloat-o-meter[1] output to an older version would be useful.
There is probably some low hanging fruit.
-Andi
[1] ftp://ftp.firstfloor.org/pub/ak/perl/bloat-o-meter
next prev parent reply other threads:[~2004-10-29 5:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 4:04 Userspace ACPI interpreter ( was RE: [ACPI] [RFC] dev_acpi: support for userspace access to acpi) 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 [this message]
2004-10-28 15:18 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 2:40 Yu, Luming
2004-10-29 2:51 Yu, Luming
2004-10-31 21:29 ` Pavel Machek
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=20041029045858.GL11384@wotan.suse.de \
--to=ak@suse.de \
--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=luming.yu@intel.com \
--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