From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: kernel-team@android.com, kvm@vger.kernel.org,
Will Deacon <will@kernel.org>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 5/6] KVM: arm64: Stop mapping current thread_info at EL2
Date: Wed, 1 Dec 2021 13:29:58 +0000 [thread overview]
Message-ID: <Yad41lTBoUkt8lZi@sirena.org.uk> (raw)
In-Reply-To: <20211201120436.389756-6-maz@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 221 bytes --]
On Wed, Dec 01, 2021 at 12:04:35PM +0000, Marc Zyngier wrote:
> Now that we can track an equivalent of TIF_FOREIGN_FPSTATE, drop
> the mapping of current's thread_info at EL2.
Reviwed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2021-12-01 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 12:04 [PATCH v3 0/6] KVM: arm64: Rework FPSIMD/SVE tracking Marc Zyngier
2021-12-01 12:04 ` [PATCH v3 1/6] KVM: arm64: Reorder vcpu flag definitions Marc Zyngier
2021-12-01 12:04 ` [PATCH v3 2/6] KVM: arm64: Get rid of host SVE tracking/saving Marc Zyngier
2021-12-01 12:04 ` [PATCH v3 3/6] KVM: arm64: Remove unused __sve_save_state Marc Zyngier
2021-12-01 12:56 ` Mark Brown
2021-12-01 12:04 ` [PATCH v3 4/6] KVM: arm64: Introduce flag shadowing TIF_FOREIGN_FPSTATE Marc Zyngier
2021-12-01 12:04 ` [PATCH v3 5/6] KVM: arm64: Stop mapping current thread_info at EL2 Marc Zyngier
2021-12-01 13:29 ` Mark Brown [this message]
2021-12-01 12:04 ` [PATCH v3 6/6] arm64/fpsimd: Document the use of TIF_FOREIGN_FPSTATE by KVM Marc Zyngier
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=Yad41lTBoUkt8lZi@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@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 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).