From: Mark Brown <broonie@kernel.org>
To: Dave Martin <Dave.Martin@arm.com>
Cc: Julien Grall <julien@xen.com>, Julien Grall <julien@xen.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Zhang Lei <zhang.lei@jp.fujitsu.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Daniel Kiss <Daniel.Kiss@arm.com>
Subject: Re: [PATCH v7 1/2] arm64/sve: Split TIF_SVE into separate execute and register state flags
Date: Mon, 1 Feb 2021 15:45:43 +0000 [thread overview]
Message-ID: <20210201154543.GC5960@sirena.org.uk> (raw)
In-Reply-To: <20210201153550.GE13952@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 324 bytes --]
On Mon, Feb 01, 2021 at 03:35:53PM +0000, Dave Martin wrote:
> While I'm trying to get my head around this, can you sketch out the
> mapping between the old flag combinations (including Julien's
> TIF_SVE_NEEDS_FLUSH) and yours?
TIF_SVE => TIF_SVE_EXEC+TIF_SVE_FULL_REGS
TIF_SVE_NEEDS_FLUSH => TIF_SVE_EXEC
more or less.
[-- 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:[~2021-02-01 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 12:28 [PATCH v7 0/2] arm64/sve: Improve performance when handling SVE access traps Mark Brown
2021-02-01 12:29 ` [PATCH v7 1/2] arm64/sve: Split TIF_SVE into separate execute and register state flags Mark Brown
2021-02-01 15:35 ` Dave Martin
2021-02-01 15:45 ` Mark Brown [this message]
2021-02-09 17:59 ` Dave Martin
2021-02-09 22:16 ` Mark Brown
2021-02-10 19:52 ` Mark Brown
2021-02-10 10:56 ` Dave Martin
2021-02-10 14:54 ` Mark Brown
2021-02-10 15:42 ` Dave Martin
2021-02-10 17:14 ` Mark Brown
2021-02-10 18:15 ` Dave Martin
2021-02-01 12:29 ` [PATCH v7 2/2] arm64/sve: Rework SVE trap access to minimise memory access Mark Brown
2021-02-10 11:09 ` Dave Martin
2021-02-10 17:54 ` Mark Brown
2021-02-08 17:26 ` [PATCH v7 0/2] arm64/sve: Improve performance when handling SVE access traps Dave Martin
2021-02-09 18:22 ` Mark Brown
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=20210201154543.GC5960@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Daniel.Kiss@arm.com \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=julien@xen.com \
--cc=julien@xen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.org \
--cc=zhang.lei@jp.fujitsu.com \
/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.