public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Masayoshi Mizuma <msys.mizuma@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/4] x86/mm/KASLR: Adjust the padding size for the direct  mapping.
Date: Thu, 14 Nov 2019 16:16:38 +0800	[thread overview]
Message-ID: <20191114081638.GH30906@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20191112204707.jyruwkb4pbdj3jvv@gabell>

On 11/12/19 at 03:47pm, Masayoshi Mizuma wrote:
> Your suggesion makes it simpler, thanks!
> So I'll modify calc_direct_mapping_size() as following.
> Does it make sense?

Yeah, it looks good to me. Thanks.

> 
> static inline unsigned long calc_direct_mapping_size(void)
> {
>        unsigned long size_tb, memory_tb;
> 
>        memory_tb = DIV_ROUND_UP(max_pfn << PAGE_SHIFT, 1UL << TB_SHIFT) +
>                CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING;
> 
> #ifdef CONFIG_MEMORY_HOTPLUG
>        if (boot_params.max_addr) {
>                unsigned long maximum_tb;
> 
>                maximum_tb = DIV_ROUND_UP(boot_params.max_addr,
>                                1UL << TB_SHIFT);
> 
>                if (maximum_tb > memory_tb)
>                        memory_tb = maximum_tb;
>        }
> #endif
>        size_tb = 1 << (MAX_PHYSMEM_BITS - TB_SHIFT);
> 
>        /*
>         * Adapt physical memory region size based on available memory
>         */
>        if (memory_tb < size_tb)
>                size_tb = memory_tb;
> 
>        return size_tb;
> }


      reply	other threads:[~2019-11-14  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02  1:09 [PATCH v4 0/4] Adjust the padding size for KASLR Masayoshi Mizuma
2019-11-02  1:09 ` [PATCH v4 1/4] x86/boot: Wrap up the SRAT traversing code into subtable_parse() Masayoshi Mizuma
2019-11-02  1:09 ` [PATCH v4 2/4] x86/boot: Add max_addr field in struct boot_params Masayoshi Mizuma
2019-11-02  1:09 ` [PATCH v4 3/4] x86/boot: Get the max address from SRAT Masayoshi Mizuma
2019-11-04  0:33   ` Baoquan He
2019-11-02  1:09 ` [PATCH v4 4/4] x86/mm/KASLR: Adjust the padding size for the direct mapping Masayoshi Mizuma
2019-11-04  0:48   ` Baoquan He
2019-11-12 20:47     ` Masayoshi Mizuma
2019-11-14  8:16       ` Baoquan He [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191114081638.GH30906@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.mizuma@jp.fujitsu.com \
    --cc=mingo@redhat.com \
    --cc=msys.mizuma@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox