From: "Jan Beulich" <JBeulich@novell.com>
To: <yinghai@kernel.org>, <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH] relax free_area() for compatibility with free_bootmem()
Date: Fri, 26 Mar 2010 16:30:49 +0000 [thread overview]
Message-ID: <4BACEF490200007800037346@vpn.id2.novell.com> (raw)
To be compatible with the traditional free_bootmem() (which is just a
wrapper around free_earl() under CONFIG_NO_BOOTMEM), free_area()
should allow freeing not only exact ranges, but also proper subsets.
This is still different from free_early_partial() in that the latter
also handles an input range spanning multiple reserved ranges,
possibly even with holes between them (not that I think permitting
this is a good idea).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
---
kernel/early_res.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.34-rc2/kernel/early_res.c 2010-03-25 15:23:45.000000000 +0100
+++ 2.6.34-rc2-free_early-subrange/kernel/early_res.c 2010-03-26 14:49:41.000000000 +0100
@@ -321,11 +321,11 @@ void __init free_early(u64 start, u64 en
i = find_overlapped_early(start, end);
r = &early_res[i];
- if (i >= max_early_res || r->end != end || r->start != start)
+ if (i >= max_early_res || r->end < end || r->start > start)
panic("free_early on not reserved area: %llx-%llx!",
start, end - 1);
- drop_range(i);
+ drop_range_partial(i, start, end);
}
void __init free_early_partial(u64 start, u64 end)
reply other threads:[~2010-03-26 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BACEF490200007800037346@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®