public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Matthew Wilcox <matthew@wil.cx>, Andrew Morton <akpm@osdl.org>,
	linux-arch@vger.kernel.org, Randolph Chung <randolph@tausq.org>
Subject: Re: no-arch-specific-mem_map-init
Date: Thu, 10 Mar 2005 07:58:38 -0800	[thread overview]
Message-ID: <1110470318.20958.18.camel@localhost> (raw)
In-Reply-To: <320030000.1110468381@[10.10.2.4]>

On Thu, 2005-03-10 at 07:26 -0800, Martin J. Bligh wrote:
> >         mem_map = zone_table[ZONE_DMA]->zone_mem_map;
> ...
> > Something that may not be intuitively obvious to someone with i386 biases
> > is that on PA-RISC (at least in the case of CONFIG_DISCONTIGMEM=n), all
> > memory is in ZONE_DMA.  Does that help divine what the right answer is
> > for parisc?
> 
> In which case, you should be fine, you should have
> 
> 	NODE_DATA(0)->node_mem_map == zone_table[ZONE_DMA]->zone_mem_map
> 
> I believe. In free_area_init_core(), we do:
> 
> 	zone->zone_mem_map = pfn_to_page(zone_start_pfn);
> 
> So as long as zone_start_pfn == node_start_pfn, they're equiv. As you say
> all your mem is in ZONE_DMA, that should be true.

Now that I look at it again, mem_init() happens way after
paging_init()->free_area_init_node()->alloc_node_mem_map().  So, mem_map
should already be initialized by the time mem_init() gets called.  It
should be safe to just remove the

	mem_map = zone_table[ZONE_DMA]->zone_mem_map;

line in mem_init().

Now that I have your attention, could you stick a printk in there, and
double check that I'm right?  

-- Dave

P.S.  I do a lot of ppc64 work, too, so I have a bias for that as
well. :)

  reply	other threads:[~2005-03-10 15:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  6:58 no-arch-specific-mem_map-init Andrew Morton
2005-03-10  7:38 ` no-arch-specific-mem_map-init Martin J. Bligh
2005-03-10  8:22 ` no-arch-specific-mem_map-init Paul Mackerras
2005-03-10 13:35 ` no-arch-specific-mem_map-init Paul Mundt
2005-03-10 14:18 ` no-arch-specific-mem_map-init Matthew Wilcox
2005-03-10 14:30   ` no-arch-specific-mem_map-init David Howells
2005-03-10 14:33     ` no-arch-specific-mem_map-init Matthew Wilcox
2005-03-10 15:24     ` no-arch-specific-mem_map-init Randolph Chung
2005-03-10 15:26   ` no-arch-specific-mem_map-init Martin J. Bligh
2005-03-10 15:58     ` Dave Hansen [this message]
2005-03-10 16:21       ` no-arch-specific-mem_map-init Matthew Wilcox
2005-03-10 22:54 ` no-arch-specific-mem_map-init Russell King
  -- strict thread matches above, loose matches on Subject: below --
2005-03-10 19:59 no-arch-specific-mem_map-init Luck, Tony

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=1110470318.20958.18.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mbligh@aracnet.com \
    --cc=randolph@tausq.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