From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [HELP] latest discontig
Date: Mon, 22 Sep 2003 19:39:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106425978523413@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106305453930076@msgid-missing>
Jesse> Here's the latest discontig patch. It seems to be working
Jesse> for everybody, but could always use more testing.
Jesse> Unfortunately, I haven't been able to come up with a good way
Jesse> to make the functions reentrant wrt the new cdata structure.
Jesse> Everything I come up with is much uglier than what's there,
Jesse> and even more obtuse, so I'd really appreciate suggestions.
Jesse> Personally, I'd like to see David merge this patch to make an
Jesse> intrusive cleanup of the memory initialization code easier
Jesse> :).
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
- doesn't actually BREAK the existing ia64 platforms
- looks like the author(s) actually cared about they were doing
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.
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
- MAX_RSVD_REGIONS et al got moved to pgtable.h; why in the world would
that be the right place? Just because "it compiled"??
- why is there both vmem_map and mem_map in the NUMA case?
--david
next prev parent reply other threads:[~2003-09-22 19:39 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 [this message]
2003-09-22 20:31 ` Jesse Barnes
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-106425978523413@msgid-missing \
--to=davidm@napali.hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox