From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64/mm: define ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT
Date: Wed, 2 May 2018 13:23:14 +0100 [thread overview]
Message-ID: <20180502122314.GB30246@arm.com> (raw)
In-Reply-To: <1525247602-1565-1-git-send-email-opensource.ganesh@gmail.com>
On Wed, May 02, 2018 at 03:53:21PM +0800, Ganesh Mahendran wrote:
> Set ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT for arm64. This
> enables Speculative Page Fault handler.
Are there are tests for this? I'm really nervous about enabling it...
Will
>
> Signed-off-by: Ganesh Mahendran <opensource.ganesh@gmail.com>
> ---
> This patch is on top of Laurent's v10 spf
> ---
> arch/arm64/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index eb2cf49..cd583a9 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -144,6 +144,7 @@ config ARM64
> select SPARSE_IRQ
> select SYSCTL_EXCEPTION_TRACE
> select THREAD_INFO_IN_TASK
> + select ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT if SMP
> help
> ARM 64-bit (AArch64) Linux support.
>
> --
> 1.9.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Ganesh Mahendran <opensource.ganesh@gmail.com>
Cc: ldufour@linux.vnet.ibm.com, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] arm64/mm: define ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT
Date: Wed, 2 May 2018 13:23:14 +0100 [thread overview]
Message-ID: <20180502122314.GB30246@arm.com> (raw)
In-Reply-To: <1525247602-1565-1-git-send-email-opensource.ganesh@gmail.com>
On Wed, May 02, 2018 at 03:53:21PM +0800, Ganesh Mahendran wrote:
> Set ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT for arm64. This
> enables Speculative Page Fault handler.
Are there are tests for this? I'm really nervous about enabling it...
Will
>
> Signed-off-by: Ganesh Mahendran <opensource.ganesh@gmail.com>
> ---
> This patch is on top of Laurent's v10 spf
> ---
> arch/arm64/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index eb2cf49..cd583a9 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -144,6 +144,7 @@ config ARM64
> select SPARSE_IRQ
> select SYSCTL_EXCEPTION_TRACE
> select THREAD_INFO_IN_TASK
> + select ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT if SMP
> help
> ARM 64-bit (AArch64) Linux support.
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2018-05-02 12:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 7:53 [PATCH 1/2] arm64/mm: define ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT Ganesh Mahendran
2018-05-02 7:53 ` Ganesh Mahendran
2018-05-02 12:23 ` Will Deacon [this message]
2018-05-02 12:23 ` Will Deacon
2018-05-04 6:05 ` Ganesh Mahendran
2018-05-04 6:05 ` Ganesh Mahendran
-- strict thread matches above, loose matches on Subject: below --
2018-05-02 7:54 Ganesh Mahendran
2018-05-02 7:54 ` Ganesh Mahendran
2018-05-02 9:00 ` Laurent Dufour
2018-05-02 9:00 ` Laurent Dufour
2018-05-02 11:05 ` Mark Rutland
2018-05-02 11:05 ` Mark Rutland
2018-05-03 8:48 ` Chintan Pandya
2018-05-03 8:48 ` Chintan Pandya
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=20180502122314.GB30246@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.