linux-kernel - Re: [PATCH 13/13] memblock, x86: Replace memblock_x86_reserve/free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 14 Jul 2011 13:23:28 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Tejun Heo <tj@...nel.org>
CC:	mingo@...hat.com, tglx@...utronix.de, benh@...nel.crashing.org,
	yinghai@...nel.org, davem@...emloft.net,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	x86@...nel.org
Subject: Re: [PATCH 13/13] memblock, x86: Replace memblock_x86_reserve/free_range()
 with generic ones

On 07/14/2011 01:20 PM, Tejun Heo wrote:
> 
> Hmm... looking at the boot log, not really. [ ) ranges are more
> common. memblock code is one of notable exceptions and I actually was
> thinking about converting it. [ ) ranges are easier to recognize and
> most of code we have can't deal with the full range (and it shouldn't
> need to - chopping off one top and bottom is much saner approach
> anyway).
> 

Sorry I don't follow.  We display resources as [...] ranges, and in
particular when there are those kinds of brackets they tend to be
inclusive ranges.

For the internal representation, of course, [ ) ranges or (base, length)
are the only sensible options.

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/