From: Catalin Marinas <catalin.marinas@arm.com>
To: Steve Capper <steve.capper@arm.com>
Cc: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
will.deacon@arm.com, jcm@redhat.com, ard.biesheuvel@linaro.org
Subject: Re: [PATCH V3 2/5] arm64: mm: Introduce DEFAULT_MAP_WINDOW
Date: Tue, 27 Nov 2018 17:09:32 +0000 [thread overview]
Message-ID: <20181127170931.GC3563@arrakis.emea.arm.com> (raw)
In-Reply-To: <20181114133920.7134-3-steve.capper@arm.com>
Hi Steve,
On Wed, Nov 14, 2018 at 01:39:17PM +0000, Steve Capper wrote:
> diff --git a/arch/arm64/include/asm/processor.h b/arch/arm64/include/asm/processor.h
> index 3e2091708b8e..da41a2655b69 100644
> --- a/arch/arm64/include/asm/processor.h
> +++ b/arch/arm64/include/asm/processor.h
> @@ -25,6 +25,9 @@
> #define USER_DS (TASK_SIZE_64 - 1)
>
> #ifndef __ASSEMBLY__
> +
> +#define DEFAULT_MAP_WINDOW_64 (UL(1) << VA_BITS)
> +
> #ifdef __KERNEL__
That's a strange place to place DEFAULT_MAP_WINDOW_64. Did you have any
#include dependency issues? If yes, we could look at cleaning them up,
maybe moving these definitions into a separate file.
(also, if you do a clean-up I don't think we need __KERNEL__ anymore)
>
> #include <linux/build_bug.h>
> @@ -51,13 +54,16 @@
> TASK_SIZE_32 : TASK_SIZE_64)
> #define TASK_SIZE_OF(tsk) (test_tsk_thread_flag(tsk, TIF_32BIT) ? \
> TASK_SIZE_32 : TASK_SIZE_64)
> +#define DEFAULT_MAP_WINDOW (test_thread_flag(TIF_32BIT) ? \
> + TASK_SIZE_32 : DEFAULT_MAP_WINDOW_64)
> #else
> #define TASK_SIZE TASK_SIZE_64
> +#define DEFAULT_MAP_WINDOW DEFAULT_MAP_WINDOW_64
> #endif /* CONFIG_COMPAT */
>
> -#define TASK_UNMAPPED_BASE (PAGE_ALIGN(TASK_SIZE / 4))
> +#define TASK_UNMAPPED_BASE (PAGE_ALIGN(DEFAULT_MAP_WINDOW / 4))
> +#define STACK_TOP_MAX DEFAULT_MAP_WINDOW_64
>
> -#define STACK_TOP_MAX TASK_SIZE_64
> #ifdef CONFIG_COMPAT
> #define AARCH32_VECTORS_BASE 0xffff0000
> #define STACK_TOP (test_thread_flag(TIF_32BIT) ? \
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index 9d9582cac6c4..e5a1dc0beef9 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -609,7 +609,7 @@ void __init mem_init(void)
> * detected at build time already.
> */
> #ifdef CONFIG_COMPAT
> - BUILD_BUG_ON(TASK_SIZE_32 > TASK_SIZE_64);
> + BUILD_BUG_ON(TASK_SIZE_32 > DEFAULT_MAP_WINDOW_64);
> #endif
Since you are at this, can you please remove the useless white space (I
guess it was there before when we had more BUILD_BUG_ONs).
> diff --git a/drivers/firmware/efi/libstub/arm-stub.c b/drivers/firmware/efi/libstub/arm-stub.c
> index 30ac0c975f8a..d1ec7136e3e1 100644
> --- a/drivers/firmware/efi/libstub/arm-stub.c
> +++ b/drivers/firmware/efi/libstub/arm-stub.c
> @@ -33,7 +33,7 @@
> #define EFI_RT_VIRTUAL_SIZE SZ_512M
>
> #ifdef CONFIG_ARM64
> -# define EFI_RT_VIRTUAL_LIMIT TASK_SIZE_64
> +# define EFI_RT_VIRTUAL_LIMIT DEFAULT_MAP_WINDOW_64
> #else
> # define EFI_RT_VIRTUAL_LIMIT TASK_SIZE
> #endif
Just curious, would anything happen if we leave this to TASK_SIZE_64?
--
Catalin
next prev parent reply other threads:[~2018-11-27 17:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 13:39 [PATCH V3 0/5] 52-bit userspace VAs Steve Capper
2018-11-14 13:39 ` [PATCH V3 1/5] mm: mmap: Allow for "high" userspace addresses Steve Capper
2018-11-23 18:17 ` Catalin Marinas
2018-11-26 12:11 ` Steve Capper
2018-11-14 13:39 ` [PATCH V3 2/5] arm64: mm: Introduce DEFAULT_MAP_WINDOW Steve Capper
2018-11-27 17:09 ` Catalin Marinas [this message]
2018-11-27 17:15 ` Ard Biesheuvel
2018-11-28 16:31 ` Steve Capper
2018-11-14 13:39 ` [PATCH V3 3/5] arm64: mm: Define arch_get_mmap_end, arch_get_mmap_base Steve Capper
2018-11-27 17:10 ` Catalin Marinas
2018-11-28 16:31 ` Steve Capper
2018-11-14 13:39 ` [PATCH V3 4/5] arm64: mm: introduce 52-bit userspace support Steve Capper
2018-11-23 18:35 ` Catalin Marinas
2018-11-26 12:13 ` Steve Capper
2018-11-30 17:59 ` Catalin Marinas
2018-12-04 17:41 ` Steve Capper
2018-11-14 13:39 ` [PATCH V3 5/5] arm64: mm: Allow forcing all userspace addresses to 52-bit Steve Capper
2018-11-23 18:22 ` Catalin Marinas
2018-11-26 12:11 ` Steve Capper
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=20181127170931.GC3563@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=steve.capper@arm.com \
--cc=will.deacon@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).