linux-kernel - Re: [PATCH v2 29/76] ARC: Boot #1: low-level, setup

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:	Fri, 18 Jan 2013 14:45:38 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 29/76] ARC: Boot #1: low-level, setup_arch(), /proc/cpuinfo, mem init

On Friday 18 January 2013, Vineet Gupta wrote:
> +       /* setup bootmem allocator */
> +       bootmap_sz = init_bootmem_node(NODE_DATA(0),
> +                                      first_free_pfn,/* bitmap start */
> +                                      min_low_pfn,   /* First pg to track */
> +                                      max_low_pfn);  /* Last pg to track */
> +
> +       /*
> +        * init_bootmem above marks all tracked Page-frames as inuse "allocated"
> +        * This includes pages occupied by kernel's elf segments.
> +        * Beyond that, excluding bootmem bitmap itself, mark the rest of
> +        * free-mem as "allocatable"
> +        */
> +       alloc_start = kernel_img_end + bootmap_sz;
> +       free_bootmem(alloc_start, end_mem - alloc_start);
> +
> +       memset(zones_size, 0, sizeof(zones_size));
> +       zones_size[ZONE_NORMAL] = num_physpages;
> +

IIRC, the bootmem allocator is no longer recommended for new architecture.
You should use the "memblock" interface instead, as arm64 and tile do.

I just saw that this is still listed as TODO for openrisc, sorry if I
put you on the wrong track there by recommending to copy from openrisc.

	Arnd
--
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/