From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [HELP] latest discontig
Date: Mon, 22 Sep 2003 20:31:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106426273427285@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106305453930076@msgid-missing>
On Mon, Sep 22, 2003 at 12:39:40PM -0700, David Mosberger wrote:
> You know, you'd greatly increase the chance of my applying the patch
> if the patch:
>
> - were broken up into reasonably small, self-contained pieces
Um.. I can try to break it up.
> - doesn't actually BREAK the existing ia64 platforms
Does it? We've tested it on quite a few...
> I'm sorry, but until some of these criteria are met, there is no way
> I'm going to apply this patch. As for the breakage: as far as I can
> see, the patch moves the bootmem initialization back to the old place,
> which means that drivers/acpi/tables.c will fail to allocate memory
> for the SDT again.
Len Brown already took the change to fix tables.c.
> Some other comments:
>
> - in acpi.c, it looks like there is no reason for min_hole_size anymore,
> yet the patch doesn't clean up this variable
Ok.
> - MAX_RSVD_REGIONS et al got moved to pgtable.h; why in the world would
> that be the right place? Just because "it compiled"??
I'll have to look at that again. I think I needed to move some of that
stuff to a header because I created contig.c to seperate things a
little.
> - why is there both vmem_map and mem_map in the NUMA case?
Because it compiled :/. I'll try to fix that up too.
Thanks,
Jesse
next prev parent reply other threads:[~2003-09-22 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 20:45 [HELP] latest discontig Jesse Barnes
2003-09-22 19:39 ` David Mosberger
2003-09-22 20:31 ` Jesse Barnes [this message]
2003-09-22 21:01 ` David Mosberger
2003-09-22 21:04 ` Jesse Barnes
2003-09-22 22:04 ` David Mosberger
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=marc-linux-ia64-106426273427285@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.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.