linux-kernel - Re: [PATCH 2/5] x86: find_early_table_space based on memory ranges that are being mapped

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:	Sat, 11 Aug 2012 12:56:16 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Jacob Shin <jacob.shin@....com>
Cc:	X86-ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yinghai@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: [PATCH 2/5] x86: find_early_table_space based on memory ranges
 that are being mapped

Hello,

On Thu, Aug 09, 2012 at 04:23:06PM -0500, Jacob Shin wrote:
> Current logic finds enough space to cover number of tables from 0 to end.
> Instead, we only need to find enough space to cover from mr[0].start to
> mr[nr_range].end.
> 
> Signed-off-by: Jacob Shin <jacob.shin@....com>
> ---
>  arch/x86/mm/init.c |   57 +++++++++++++++++++++++++++-------------------------
>  1 file changed, 30 insertions(+), 27 deletions(-)
> 
> diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
> index e0e6990..d4e01a7 100644
> --- a/arch/x86/mm/init.c
> +++ b/arch/x86/mm/init.c
> @@ -35,40 +35,43 @@ struct map_range {
>  	unsigned page_size_mask;
>  };
>  
> -static void __init find_early_table_space(struct map_range *mr, unsigned long end,
> -					  int use_pse, int use_gbpages)
> +static void __init find_early_table_space(struct map_range *mr, int nr_range)
>  {
> -	unsigned long puds, pmds, ptes, tables, start = 0, good_end = end;
> +	int i;
> +	unsigned long puds = 0, pmds = 0, ptes = 0, tables;
> +	unsigned long start = 0, good_end;
>  	phys_addr_t base;
>  
> -	puds = (end + PUD_SIZE - 1) >> PUD_SHIFT;
> -	tables = roundup(puds * sizeof(pud_t), PAGE_SIZE);
> -
> -	if (use_gbpages) {
> -		unsigned long extra;
> +	for (i = 0; i < nr_range; i++) {
> +		unsigned long range, extra;
>  
> -		extra = end - ((end>>PUD_SHIFT) << PUD_SHIFT);
> -		pmds = (extra + PMD_SIZE - 1) >> PMD_SHIFT;
> -	} else
> -		pmds = (end + PMD_SIZE - 1) >> PMD_SHIFT;
> -
> -	tables += roundup(pmds * sizeof(pmd_t), PAGE_SIZE);
> +		range = mr[i].end - mr[i].start;
> +		puds += (range + PUD_SIZE - 1) >> PUD_SHIFT;
>  
> -	if (use_pse) {
> -		unsigned long extra;
> +		if (mr[i].page_size_mask & (1 << PG_LEVEL_1G)) {
> +			extra = range - ((range >> PUD_SHIFT) << PUD_SHIFT);
> +			pmds += (extra + PMD_SIZE - 1) >> PMD_SHIFT;
> +		} else {
> +			pmds += (range + PMD_SIZE - 1) >> PMD_SHIFT;
> +		}
>  
> -		extra = end - ((end>>PMD_SHIFT) << PMD_SHIFT);
> +		if (mr[i].page_size_mask & (1 << PG_LEVEL_2M)) {
> +			extra = range - ((range >> PMD_SHIFT) << PMD_SHIFT);
>  #ifdef CONFIG_X86_32
> -		extra += PMD_SIZE;
> +			extra += PMD_SIZE;
>  #endif
> -		/* The first 2/4M doesn't use large pages. */
> -		if (mr->start < PMD_SIZE)
> -			extra += mr->end - mr->start;
> -
> -		ptes = (extra + PAGE_SIZE - 1) >> PAGE_SHIFT;
> -	} else
> -		ptes = (end + PAGE_SIZE - 1) >> PAGE_SHIFT;
> +			/* The first 2/4M doesn't use large pages. */
> +			if (mr[i].start < PMD_SIZE)
> +				extra += range;
> +
> +			ptes += (extra + PAGE_SIZE - 1) >> PAGE_SHIFT;
> +		} else {
> +			ptes += (range + PAGE_SIZE - 1) >> PAGE_SHIFT;
> +		}
> +	}
>  
> +	tables = roundup(puds * sizeof(pud_t), PAGE_SIZE);
> +	tables += roundup(pmds * sizeof(pmd_t), PAGE_SIZE);

It would really be great if you can sprinkle some comments explaining
what the function is trying to do and how it does that.  Functions
like this can be pretty difficult to extract higher-level concept out
of.

Thanks.

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