public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
	Luming Yu <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>,
	Robert Moore
	<robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>,
	linux-kernel
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Userspace ACPI interpreter ( was RE: [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



-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/

  reply	other threads:[~2004-10-29  4:58 UTC|newest]

Thread overview: 8+ 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
     [not found]   ` <418085B0.30208-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2004-10-28 15:24     ` Userspace ACPI interpreter ( was " Theodore Ts'o
2004-10-29  4:48       ` Userspace ACPI interpreter ( was RE: [ACPI] " Len Brown
2004-10-29  4:58         ` Andi Kleen [this message]
2004-10-28 15:18 ` Userspace ACPI interpreter ( was " 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

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-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=alex.williamson-VXdhtT5mjnY@public.gmane.org \
    --cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=tytso-3s7WtUTddSA@public.gmane.org \
    /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