From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>
Cc: stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/sve: Use correct size when reinitialising SVE state
Date: Thu, 16 Sep 2021 18:08:33 +0100 [thread overview]
Message-ID: <163181210192.884883.4596115964596843618.b4-ty@arm.com> (raw)
In-Reply-To: <20210909165356.10675-1-broonie@kernel.org>
On Thu, 9 Sep 2021 17:53:56 +0100, Mark Brown wrote:
> When we need a buffer for SVE register state we call sve_alloc() to make
> sure that one is there. In order to avoid repeated allocations and frees
> we keep the buffer around unless we change vector length and just memset()
> it to ensure a clean register state. The function that deals with this
> takes the task to operate on as an argument, however in the case where we
> do a memset() we initialise using the SVE state size for the current task
> rather than the task passed as an argument.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/sve: Use correct size when reinitialising SVE state
https://git.kernel.org/arm64/c/e35ac9d0b56e
--
Catalin
_______________________________________________
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: Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>
Cc: stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/sve: Use correct size when reinitialising SVE state
Date: Thu, 16 Sep 2021 18:08:33 +0100 [thread overview]
Message-ID: <163181210192.884883.4596115964596843618.b4-ty@arm.com> (raw)
In-Reply-To: <20210909165356.10675-1-broonie@kernel.org>
On Thu, 9 Sep 2021 17:53:56 +0100, Mark Brown wrote:
> When we need a buffer for SVE register state we call sve_alloc() to make
> sure that one is there. In order to avoid repeated allocations and frees
> we keep the buffer around unless we change vector length and just memset()
> it to ensure a clean register state. The function that deals with this
> takes the task to operate on as an argument, however in the case where we
> do a memset() we initialise using the SVE state size for the current task
> rather than the task passed as an argument.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/sve: Use correct size when reinitialising SVE state
https://git.kernel.org/arm64/c/e35ac9d0b56e
--
Catalin
next prev parent reply other threads:[~2021-09-16 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 16:53 [PATCH] arm64/sve: Use correct size when reinitialising SVE state Mark Brown
2021-09-09 16:53 ` Mark Brown
2021-09-16 17:08 ` Catalin Marinas [this message]
2021-09-16 17:08 ` 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=163181210192.884883.4596115964596843618.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=stable@vger.kernel.org \
--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.