Messages in this thread | | | Date | Thu, 14 Jul 2011 13:38:49 -0700 | From | "H. Peter Anvin" <> | Subject | Re: [PATCH 13/13] memblock, x86: Replace memblock_x86_reserve/free_range() with generic ones |
| |
On 07/14/2011 01:32 PM, Tejun Heo wrote: > Hello, > > On Thu, Jul 14, 2011 at 10:23 PM, H. Peter Anvin <hpa@zytor.com> wrote: >> On 07/14/2011 01:20 PM, Tejun Heo wrote: >> 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. > > [ ) ranges: e820, init_memory_mapping, NUMA nodes, Zone PFN ranges, PM > nosave memory > > [ ] ranges: MTRR, NODE_DATA, early_node_map, [mm]io ranges > > Hmm... I was only looking at the early boot messages which didn't > include the io ranges. It ultimately is a cosmetic issue so my > opinions aren't very strong but I think we can leave [mm]io ranges > alone and converge the rest into [ ) ranges sans the brackets? >
Agreed it's a cosmetic issue... this discussion has already been had, though, and the consensus is to move the kernel to the standardized resource format.
-hpa
| |