From: C Michael Sundius <Michael.sundius@sciatl.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, linux-mips@linux-mips.org,
jfraser@broadcom.com, Andy Whitcroft <apw@shadowen.org>
Subject: Re: sparsemem support for mips with highmem
Date: Thu, 14 Aug 2008 16:16:28 -0700 [thread overview]
Message-ID: <48A4BCCC.6090001@sciatl.com> (raw)
In-Reply-To: <1218753308.23641.56.camel@nimitz>
>> + if (boot_mem_map.map[i].type != BOOT_MEM_RAM)
>> + continue;
>> +
>> + start = PFN_UP(boot_mem_map.map[i].addr);
>> + end = PFN_DOWN(boot_mem_map.map[i].addr
>> + + boot_mem_map.map[i].size);
>> +
>> + memory_present(0, start, end);
>> + }
>> }
>>
>
> Is that aligning really necessary? I'm just curious because if it is,
> it would probably be good to stick it inside memory_present().
>
>
yaknow, there are several loops in this file that look through this
boot_mem_ map structure.
they all have the same basic form (but of course are slightly
different). Anyhow, I just
cut and pasted. I'm wondering if the MIPS folks have comment on how best
to make
this change and possibly clean up this file. I'm happy to do it, but
think I'd like some
guidance on this... anyone?
I'll fix and resubmit. sorry for posting this to the two lists, but I
wasn't sure if I should
put it on the linux-mm list or the linux-mips list... I'll keep the
distribution unless I
her complaints.
mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-08-14 23:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 22:05 sparsemem support for mips with highmem C Michael Sundius
2008-08-14 22:35 ` Dave Hansen
2008-08-14 23:16 ` C Michael Sundius [this message]
2008-08-14 23:52 ` C Michael Sundius
2008-08-15 0:02 ` Dave Hansen
2008-08-15 8:03 ` Thomas Bogendoerfer
2008-08-15 15:48 ` Dave Hansen
2008-08-15 16:12 ` C Michael Sundius
2008-08-15 16:20 ` Dave Hansen
2008-08-15 16:33 ` Thomas Bogendoerfer
2008-08-15 17:16 ` C Michael Sundius
2008-08-15 17:37 ` Dave Hansen
2008-08-15 18:17 ` C Michael Sundius
2008-08-15 18:23 ` Dave Hansen
2008-08-16 20:07 ` Thomas Bogendoerfer
2008-08-18 16:44 ` Randy Dunlap
2008-08-18 21:24 ` Christoph Lameter
2008-08-18 21:27 ` Dave Hansen
2008-08-18 21:33 ` Christoph Lameter
2009-01-16 21:46 ` Michael Sundius
2009-01-21 14:39 ` Christoph Lameter
2008-08-18 21:57 ` David VomLehn
2008-08-19 13:06 ` Christoph Lameter
2008-08-19 23:38 ` David VomLehn
2008-08-19 23:53 ` Jon Fraser
2008-08-20 13:58 ` Christoph Lameter
2008-08-20 19:28 ` David VomLehn
2008-08-20 20:51 ` Christoph Lameter
2008-08-15 16:30 ` Thomas Bogendoerfer
2008-08-26 9:09 ` Andy Whitcroft
2008-10-06 20:15 ` Have ever checked in your mips sparsemem code into mips-linux tree? C Michael Sundius
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=48A4BCCC.6090001@sciatl.com \
--to=michael.sundius@sciatl.com \
--cc=apw@shadowen.org \
--cc=dave@linux.vnet.ibm.com \
--cc=jfraser@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).