public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: Len Brown <lenb@kernel.org>, Jack Steiner <steiner@sgi.com>,
	"H. Peter Anvin" <hpa@zytor.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] - Mapping ACPI tables as CACHED
Date: Wed, 15 Dec 2010 00:17:44 -0600	[thread overview]
Message-ID: <acpi-map-cache-err@mdm.bga.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1012142317450.4878@x980>

On Tue, 14 Dec 2010 at about 23:35:28 -0500 (EST), Len Brown wrote:
> 
> [ 1.444475] LENB: free_initmem() NOT!
> is where free_initmem(); would have been called.
> 
> So the calls to acpi_os_map_memory() at 2.586160, kill the machine.
> 
> My guess is that they are related to the opregion stuff used by i915;
> but there is no reason that acpi_os_map_memory can't be called
> as a result of AML at run-time any-time later.
> 
> BTW. what, exactly does this notation do for us?
> 
> void __iomem *__init_refok acpi_os_map_memory(...) {

A function that returns a void pointer for dereference via iomem
accessors that is not init but may conditionally call init text.

__init_refok says that the code was audited to conditionally
use init vs non-init text and data.

> 
> Also, I see no calls within E820_RAM.
> 
> I see a call at 0.534537 which is not in E820_RAM, ACPI, or NVS,
> but is in a reserved region.
> 
> I'm not sure the concept of checking against E820
> is better than simply calling ioremap_cache() always.
> 
> thanks,

after digging back through the thread for the patch, it would seem
that both __acpi_map_table_permanent and e820_all_mapped would
need to be moved from init to normal text, as this is replacing
the non-init path.  I'll let the maintainers decide if that is the
right solution (vs unconditonally mapping cached, or something else).

milton

  parent reply	other threads:[~2010-12-15  6:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 22:09 [PATCH] - Mapping ACPI tables as CACHED Jack Steiner
2010-12-14 22:58 ` H. Peter Anvin
2010-12-14 23:22   ` Len Brown
2010-12-15  0:26     ` H. Peter Anvin
2010-12-15  2:27   ` Jack Steiner
2010-12-15  4:17     ` H. Peter Anvin
2010-12-15  0:04 ` Len Brown
2010-12-15  1:18   ` H. Peter Anvin
2010-12-15  2:40     ` Len Brown
2010-12-15  2:41   ` Jack Steiner
2010-12-15  4:03     ` Len Brown
2010-12-15  4:35       ` Len Brown
2010-12-15  6:17         ` H. Peter Anvin
2010-12-15  6:17         ` Milton Miller [this message]
2010-12-15  6:29           ` H. Peter Anvin
2010-12-15 16:46       ` Jack Steiner
2010-12-15 21:16         ` Len Brown
2010-12-15 22:18           ` H. Peter Anvin
2010-12-17  2:54           ` Len Brown
2010-12-17  8:08             ` [PATCH] ACPI: use ioremap_cache() Len Brown
2010-12-27 19:42               ` Tony Luck
2010-12-27 20:12                 ` H. Peter Anvin
2010-12-28  3:21               ` Shaohua Li
2010-12-28  3:35                 ` H. Peter Anvin
2010-12-28  5:02                   ` Shaohua Li
2010-12-28 20:12                     ` H. Peter Anvin

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=acpi-map-cache-err@mdm.bga.com \
    --to=miltonm@bga.com \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox