From: Juan Quintela <quintela@mandrakesoft.com>
To: Andrew Clausen <clausen@melbourne.sgi.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: weirdness in bootmem_init(), arch/mips64/kernel/setup.c
Date: Tue, 18 Feb 2003 11:27:23 +0100 [thread overview]
Message-ID: <86ptpplw8k.fsf@trasno.mitica> (raw)
In-Reply-To: <20030218065427.GA915@pureza.melbourne.sgi.com> (Andrew Clausen's message of "Tue, 18 Feb 2003 17:54:27 +1100")
>>>>> "andrew" == Andrew Clausen <clausen@melbourne.sgi.com> writes:
andrew> Hi all,
andrew> This code isn't really relevant to what I'm working on (it isn't compiled
andrew> in to kernels for the ip27), but I just noticed it, and it looks broken:
andrew> /* Find the highest page frame number we have available. */
andrew> max_pfn = 0;
andrew> for (i = 0; i < boot_mem_map.nr_map; i++) {
andrew> unsigned long start, end;
andrew> if (boot_mem_map.map[i].type != BOOT_MEM_RAM)
andrew> continue;
andrew> ***** start = PFN_UP(boot_mem_map.map[i].addr);
andrew> ***** end = PFN_DOWN(boot_mem_map.map[i].addr
andrew> + boot_mem_map.map[i].size);
andrew> ***** if (start >= end)
andrew> continue;
andrew> if (end > max_pfn)
andrew> max_pfn = end;
andrew> }
andrew> That test looks like it will always succeed... and it looks like the
andrew> author wanted it to be a sanity check.
andrew> Why all this business with PFN_UP and PFN_DOWN? (They are bit
andrew> shifts... PFN_UP shifts left, PFN_DOWN shifts right)
Not completely sure, but I think that it is related with the weird
discontig memory that Origins (and I think other MIPS machines) have.
(Just having put the file where that thing are, will have saved me a
grep :)
1st- Looking at the code, both of them shift right:
#define PFN_UP(x) (((x) + PAGE_SIZE - 1) >> PAGE_SHIFT)
#define PFN_DOWN(x) ((x) >> PAGE_SHIFT)
PFN_UP -> page frame of next page
PFN_DOWN -> page frame of this page
2nd - if the region is empty (size = 0), start will be == end, which
means that we don't considerd that area for checking what memory
are available.
Standard disclaimer: That is my reading/things that I remind about
that, any resemblance with reality can be pure coincidence :p I am
not an expert in SGI machines lowlevel details but any mean.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-02-18 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 6:54 weirdness in bootmem_init(), arch/mips64/kernel/setup.c Andrew Clausen
2003-02-18 10:27 ` Juan Quintela [this message]
2003-02-18 10:33 ` Ralf Baechle
2003-02-18 10:42 ` Ralf Baechle
2003-02-18 22:29 ` Andrew Clausen
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=86ptpplw8k.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=clausen@melbourne.sgi.com \
--cc=linux-mips@linux-mips.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.