From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] arm64/signal: Raise limit on stack frames
Date: Wed, 17 Aug 2022 16:24:42 +0100 [thread overview]
Message-ID: <Yv0IOpdf0PMCDvDW@sirena.org.uk> (raw)
In-Reply-To: <Yvz1eDOqXmUhvVgG@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 371 bytes --]
On Wed, Aug 17, 2022 at 03:04:40PM +0100, Catalin Marinas wrote:
> On Mon, Aug 15, 2022 at 02:28:31PM +0100, Mark Brown wrote:
> > -#define SIGFRAME_MAXSZ SZ_64K
> > +#define SIGFRAME_MAXSZ (SZ_64K * 4)
> Why not SZ_256K?
I think I'd initially picked a different number which didn't have a SZ_
macro then forgot to check if there was one when I dithered back to
256K.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-17 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 13:28 [PATCH v2 0/4] arm64/sme: SME related fixes Mark Brown
2022-08-15 13:28 ` [PATCH v2 1/4] arm64/signal: Raise limit on stack frames Mark Brown
2022-08-17 14:04 ` Catalin Marinas
2022-08-17 15:24 ` Mark Brown [this message]
2022-08-15 13:28 ` [PATCH v2 2/4] arm64/signal: Flush FPSIMD register state when disabling streaming mode Mark Brown
2022-08-17 14:09 ` Catalin Marinas
2022-08-15 13:28 ` [PATCH v2 3/4] arm64/sme: Don't flush SVE register state when allocating SME storage Mark Brown
2022-08-17 14:27 ` Catalin Marinas
2022-08-15 13:28 ` [PATCH v2 4/4] arm64/sme: Don't flush SVE register state when handling SME traps Mark Brown
2022-08-17 14:28 ` 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=Yv0IOpdf0PMCDvDW@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).