All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Dave Martin <Dave.Martin@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] arm64/ptrace: Use saved floating point state type to determine SVE layout
Date: Wed,  3 Apr 2024 16:06:38 +0100	[thread overview]
Message-ID: <171215679415.2136188.8838449707596683303.b4-ty@arm.com> (raw)
In-Reply-To: <20240325-arm64-ptrace-fp-type-v1-1-8dc846caf11f@kernel.org>

On Mon, 25 Mar 2024 16:35:21 +0000, Mark Brown wrote:
> The SVE register sets have two different formats, one of which is a wrapped
> version of the standard FPSIMD register set and another with actual SVE
> register data. At present we check TIF_SVE to see if full SVE register
> state should be provided when reading the SVE regset but if we were in a
> syscall we may have saved only floating point registers even though that is
> set.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64/ptrace: Use saved floating point state type to determine SVE layout
      https://git.kernel.org/arm64/c/b017a0cea627

-- 
Catalin


WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Dave Martin <Dave.Martin@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] arm64/ptrace: Use saved floating point state type to determine SVE layout
Date: Wed,  3 Apr 2024 16:06:38 +0100	[thread overview]
Message-ID: <171215679415.2136188.8838449707596683303.b4-ty@arm.com> (raw)
In-Reply-To: <20240325-arm64-ptrace-fp-type-v1-1-8dc846caf11f@kernel.org>

On Mon, 25 Mar 2024 16:35:21 +0000, Mark Brown wrote:
> The SVE register sets have two different formats, one of which is a wrapped
> version of the standard FPSIMD register set and another with actual SVE
> register data. At present we check TIF_SVE to see if full SVE register
> state should be provided when reading the SVE regset but if we were in a
> syscall we may have saved only floating point registers even though that is
> set.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64/ptrace: Use saved floating point state type to determine SVE layout
      https://git.kernel.org/arm64/c/b017a0cea627

-- 
Catalin


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

  reply	other threads:[~2024-04-03 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 16:35 [PATCH] arm64/ptrace: Use saved floating point state type to determine SVE layout Mark Brown
2024-03-25 16:35 ` Mark Brown
2024-04-03 15:06 ` Catalin Marinas [this message]
2024-04-03 15:06   ` 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=171215679415.2136188.8838449707596683303.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Dave.Martin@arm.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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.