public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-xtensa@linux-xtensa.org, Chris Zankel <chris@zankel.net>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] xtensa: use MEMBLOCK_ALLOC_ANYWHERE for KASAN shadow map
Date: Thu, 14 Nov 2019 09:11:28 +0100	[thread overview]
Message-ID: <20191114081127.GB13537@linux.ibm.com> (raw)
In-Reply-To: <20191114010824.29540-1-jcmvbkbc@gmail.com>

On Wed, Nov 13, 2019 at 05:08:24PM -0800, Max Filippov wrote:
> KASAN shadow map doesn't need to be accessible through the linear kernel
> mapping, allocate its pages with MEMBLOCK_ALLOC_ANYWHERE so that high
> memory can be used. This frees up to ~100MB of low memory on xtensa
> configurations with KASAN and high memory.
> 
> Cc: stable@vger.kernel.org # v5.1+
> Fixes: f240ec09bb8a ("memblock: replace memblock_alloc_base(ANYWHERE)
> 		     with memblock_phys_alloc")
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>

Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>

> ---
>  arch/xtensa/mm/kasan_init.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/xtensa/mm/kasan_init.c b/arch/xtensa/mm/kasan_init.c
> index 9c957791bb33..e3baa21ff24c 100644
> --- a/arch/xtensa/mm/kasan_init.c
> +++ b/arch/xtensa/mm/kasan_init.c
> @@ -60,7 +60,9 @@ static void __init populate(void *start, void *end)
>  
>  		for (k = 0; k < PTRS_PER_PTE; ++k, ++j) {
>  			phys_addr_t phys =
> -				memblock_phys_alloc(PAGE_SIZE, PAGE_SIZE);
> +				memblock_phys_alloc_range(PAGE_SIZE, PAGE_SIZE,
> +							  0,
> +							  MEMBLOCK_ALLOC_ANYWHERE);
>  
>  			if (!phys)
>  				panic("Failed to allocate page table page\n");
> -- 
> 2.20.1
> 

-- 
Sincerely yours,
Mike.


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14  1:08 [PATCH] xtensa: use MEMBLOCK_ALLOC_ANYWHERE for KASAN shadow map Max Filippov
2019-11-14  8:11 ` Mike Rapoport [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=20191114081127.GB13537@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=chris@zankel.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=stable@vger.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