linux-kernel - Re: [PATCH -v2 13/13] x86, 64bit: Map first 1M ram early before memblock_x86

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] [day] [month] [year] [list]

Message-ID: <CAE9FiQVVKnEnFrxm1KDJeq5xgt3BXymhYF4w20qB3Kr2Sn5zUw@mail.gmail.com>
Date:	Mon, 3 Sep 2012 19:48:15 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, Jacob Shin <jacob.shin@....com>,
	Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -v2 13/13] x86, 64bit: Map first 1M ram early before memblock_x86_fill()

On Mon, Sep 3, 2012 at 12:18 AM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Sun, Sep 2, 2012 at 11:26 PM, Pekka Enberg <penberg@...nel.org> wrote:
>>
>> Yup, or move the globals together with the comment to arch/x86/mm/init.c.
>>
>> That said, max_pfn_high_mapped really ought to be kept together with
>> the other "pfn_mapped" globals and the comment should be updated.
>
> max_pfn_high_mapped is only for 64bit, and it is in init_64.c
>
> maybe later could have another patch to move max_pfn_mapped,
> max_low_pfn_mapped from
> kernel/setup.c to mm/init.c
>
> Please check attached updated patch.

oh,  I'm wrong.

this patch is not needed, until some day we could not need to do low
kernel mapping in head_64.S

Thanks

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