All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Natalie.Protasevich@unisys.com
Subject: Re: Freeing ACPI tables after parsing
Date: Wed, 23 Aug 2006 10:18:42 +0200	[thread overview]
Message-ID: <200608231018.42285.ak@suse.de> (raw)
In-Reply-To: <B28E9812BAF6E2498B7EC5C427F293A4CE6F9E@orsmsx415.amr.corp.intel.com>

On Tuesday 22 August 2006 22:28, Moore, Robert wrote:
> > Actually FACS table has a global_lock in it (which the BIOS writes
> too),
> > so it is not movable,
> > and as all tables are laid contiguously in physical memory, moving
> some
> > and
> > leaving FACS is not an option.
> 
> This is a very good point. The Global_Lock field of the FACS is not a
> pointer to the global lock, it is the actual memory location of the
> lock. Therefore, the FACS can only be mapped, it cannot be copied.

Ok.  I will fix the e820.h comments then because they're wrong.

-Andi

  reply	other threads:[~2006-08-23  8:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 20:28 Freeing ACPI tables after parsing Moore, Robert
2006-08-23  8:18 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-21  9:46 Andi Kleen
2006-08-21 16:59 ` 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

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=200608231018.42285.ak@suse.de \
    --to=ak@suse.de \
    --cc=Natalie.Protasevich@unisys.com \
    --cc=alexey_y_starikovskiy@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=robert.moore@intel.com \
    /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.