All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: linux-acpi@vger.kernel.org, len.brown@intel.com
Cc: Natalie.Protasevich@unisys.com
Subject: Freeing ACPI tables after parsing
Date: Mon, 21 Aug 2006 11:46:53 +0200	[thread overview]
Message-ID: <200608211146.53379.ak@suse.de> (raw)

[repost, this time with correct cc list]

AFAIK ACPI saves all information found in ACPI tables in memory
somewhere else (please correct me if I'm wrong on that)

I also found this comment in e820.h:

#define E820_ACPI       3 /* usable as RAM once ACPI tables have been read */

Currently I don't see any code that would free the ACPI tables after they
are read. During SLES10 testing we had some problems with the ACPI
tables on some Unisys systems being in a area where the kexec kernel
wanted to be loaded too. Also on other systems the ACPI tables are not
exactly at the end but in the middle of the memory map and for some applications
it might be better to have a lot of physical continuous memory.

So are there any plans to free the BIOS supplied ACPI tables after parsing
or is there some obstacle to that that I'm missing?

Thanks,
-Andi
 

             reply	other threads:[~2006-08-21  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21  9:46 Andi Kleen [this message]
2006-08-21 16:59 ` Freeing ACPI tables after parsing Alexey Starikovskiy
2006-08-21 20:03   ` Andi Kleen
2006-08-21 21:52 ` Len Brown
2006-08-21 22:06   ` Andi Kleen
2006-08-21 22:22     ` Len Brown
2006-08-21 22:26       ` Andi Kleen
2006-08-22 10:00       ` Alexey Starikovskiy
  -- strict thread matches above, loose matches on Subject: below --
2006-08-22 20:28 Moore, Robert
2006-08-23  8:18 ` Andi Kleen

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=200608211146.53379.ak@suse.de \
    --to=ak@suse.de \
    --cc=Natalie.Protasevich@unisys.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.