All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: mark.rutland@arm.com, ard.biesheuvel@linaro.org, maz@kernel.org,
	linux-kernel@vger.kernel.org, will@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/7] arm64: fpsimd: Make sure SVE setup is complete before SIMD is used
Date: Tue, 14 Jan 2020 11:56:14 +0000	[thread overview]
Message-ID: <20200114115613.GC2289@mbp> (raw)
In-Reply-To: <20200113233023.928028-3-suzuki.poulose@arm.com>

On Mon, Jan 13, 2020 at 11:30:18PM +0000, Suzuki K Poulose wrote:
> In-kernel users of NEON rely on may_use_simd() to check if the SIMD
> can be used. However, we must initialize the SVE before SIMD can
> be used. Add a sanity check to make sure that we have completed the
> SVE setup before anyone uses the SIMD.
> 
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>

Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, will@kernel.org, maz@kernel.org,
	ard.biesheuvel@linaro.org, mark.rutland@arm.com
Subject: Re: [PATCH v3 2/7] arm64: fpsimd: Make sure SVE setup is complete before SIMD is used
Date: Tue, 14 Jan 2020 11:56:14 +0000	[thread overview]
Message-ID: <20200114115613.GC2289@mbp> (raw)
In-Reply-To: <20200113233023.928028-3-suzuki.poulose@arm.com>

On Mon, Jan 13, 2020 at 11:30:18PM +0000, Suzuki K Poulose wrote:
> In-kernel users of NEON rely on may_use_simd() to check if the SIMD
> can be used. However, we must initialize the SVE before SIMD can
> be used. Add a sanity check to make sure that we have completed the
> SVE setup before anyone uses the SIMD.
> 
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>

Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>

  reply	other threads:[~2020-01-14 11:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 23:30 [PATCH v3 0/7] arm64: Fix support for no FP/SIMD Suzuki K Poulose
2020-01-13 23:30 ` Suzuki K Poulose
2020-01-13 23:30 ` [PATCH v3 1/7] arm64: Introduce system_capabilities_finalized() marker Suzuki K Poulose
2020-01-13 23:30   ` Suzuki K Poulose
2020-01-13 23:30 ` [PATCH v3 2/7] arm64: fpsimd: Make sure SVE setup is complete before SIMD is used Suzuki K Poulose
2020-01-13 23:30   ` Suzuki K Poulose
2020-01-14 11:56   ` Catalin Marinas [this message]
2020-01-14 11:56     ` Catalin Marinas
2020-01-13 23:30 ` [PATCH v3 3/7] arm64: cpufeature: Fix the type of no FP/SIMD capability Suzuki K Poulose
2020-01-13 23:30   ` Suzuki K Poulose
2020-01-13 23:30 ` [PATCH v3 4/7] arm64: cpufeature: Set the FP/SIMD compat HWCAP bits properly Suzuki K Poulose
2020-01-13 23:30   ` Suzuki K Poulose
2020-01-13 23:30 ` [PATCH v3 5/7] arm64: ptrace: nofpsimd: Fail FP/SIMD regset operations Suzuki K Poulose
2020-01-13 23:30   ` Suzuki K Poulose
2020-01-14 11:57   ` Catalin Marinas
2020-01-14 11:57     ` Catalin Marinas
2020-01-13 23:30 ` [PATCH v3 6/7] arm64: signal: nofpsimd: Handle fp/simd context for signal frames Suzuki K Poulose
2020-01-13 23:30   ` Suzuki K Poulose
2020-01-14 11:57   ` Catalin Marinas
2020-01-14 11:57     ` Catalin Marinas
2020-01-13 23:30 ` [PATCH v3 7/7] arm64: nofpsmid: Handle TIF_FOREIGN_FPSTATE flag cleanly Suzuki K Poulose
2020-01-13 23:30   ` Suzuki K Poulose
2020-01-14  8:30 ` [PATCH v3 0/7] arm64: Fix support for no FP/SIMD Ard Biesheuvel
2020-01-14  8:30   ` Ard Biesheuvel

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=20200114115613.GC2289@mbp \
    --to=catalin.marinas@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --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.