All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Cc: kernel-team@android.com,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH 2/5] arm64: vdso: Remove redundant calls to flush_dcache_page()
Date: Thu, 18 Mar 2021 18:05:06 +0000	[thread overview]
Message-ID: <4f7bc394-f4b1-bcee-29ef-f34af4803102@arm.com> (raw)
In-Reply-To: <20210318170738.7756-3-will@kernel.org>

On 3/18/21 5:07 PM, Will Deacon wrote:
> flush_dcache_page() ensures that the 'PG_dcache_clean' flag for its
> 'page' argument is clear so that cache maintenance will be performed
> if the page is mapped into userspace with execute permissions.
> 
> Newly allocated pages have this flag clear, so there is no need to call
> flush_dcache_page() for the compat vdso or signal pages. Remove the
> redundant calls.
> 
> Signed-off-by: Will Deacon <will@kernel.org>

Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com>

> ---
>  arch/arm64/kernel/vdso.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/arch/arm64/kernel/vdso.c b/arch/arm64/kernel/vdso.c
> index 2d057a4dc787..421411981dc3 100644
> --- a/arch/arm64/kernel/vdso.c
> +++ b/arch/arm64/kernel/vdso.c
> @@ -306,7 +306,6 @@ static int aarch32_alloc_kuser_vdso_page(void)
>  	memcpy((void *)(vdso_page + 0x1000 - kuser_sz), __kuser_helper_start,
>  	       kuser_sz);
>  	aarch32_vectors_page = virt_to_page(vdso_page);
> -	flush_dcache_page(aarch32_vectors_page);
>  	return 0;
>  }
>  
> @@ -322,7 +321,6 @@ static int aarch32_alloc_sigpage(void)
>  
>  	memcpy((void *)sigpage, __aarch32_sigret_code_start, sigret_sz);
>  	aarch32_sig_page = virt_to_page(sigpage);
> -	flush_dcache_page(aarch32_sig_page);
>  	return 0;
>  }
>  
> 

-- 
Regards,
Vincenzo

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-03-18 18:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 17:07 [PATCH 0/5] Minor improvements to the compat vdso and sigpage Will Deacon
2021-03-18 17:07 ` [PATCH 1/5] arm64: vdso: Use GFP_KERNEL for allocating compat vdso and signal pages Will Deacon
2021-03-18 18:03   ` Vincenzo Frascino
2021-03-24 17:28     ` Catalin Marinas
2021-03-18 17:07 ` [PATCH 2/5] arm64: vdso: Remove redundant calls to flush_dcache_page() Will Deacon
2021-03-18 18:05   ` Vincenzo Frascino [this message]
2021-03-18 17:07 ` [PATCH 3/5] arm64: compat: Allow signal page to be remapped Will Deacon
2021-03-18 18:06   ` Vincenzo Frascino
2021-03-18 17:07 ` [PATCH 4/5] arm64: vdso: Avoid ISB after reading from cntvct_el0 Will Deacon
2021-03-18 18:08   ` Vincenzo Frascino
2021-03-18 17:07 ` [PATCH 5/5] arm64: compat: Poison the compat sigpage Will Deacon
2021-03-18 18:13   ` Vincenzo Frascino
2021-03-24 16:58 ` [PATCH 0/5] Minor improvements to the compat vdso and sigpage Catalin Marinas

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=4f7bc394-f4b1-bcee-29ef-f34af4803102@arm.com \
    --to=vincenzo.frascino@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.