From: alex.bennee@linaro.org (Alex Bennée)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] KVM: arm64: Avoid mistaken attempts to save SVE state for vcpus
Date: Fri, 15 Jun 2018 09:50:54 +0100 [thread overview]
Message-ID: <87po0szb4h.fsf@linaro.org> (raw)
In-Reply-To: <1528976546-25999-4-git-send-email-Dave.Martin@arm.com>
Dave Martin <Dave.Martin@arm.com> writes:
> This patch ensures this my delaying restoration of current's
> TIF_SVE until after the call to fpsimd_save().
this *by* delaying
--
Alex Benn?e
next prev parent reply other threads:[~2018-06-15 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 11:33 [PATCH 0/4] KVM: arm64: FPSIMD/SVE fixes for 4.17 Dave Martin
2018-06-14 11:42 ` [PATCH 1/4] arm64: introduce sysreg_clear_set() Dave Martin
2018-06-14 11:42 ` [PATCH 2/4] KVM: arm64: Don't mask softirq with IRQs disabled in vcpu_put() Dave Martin
2018-06-14 12:50 ` Marc Zyngier
2018-06-14 12:57 ` Dave Martin
2018-06-14 11:42 ` [PATCH 3/4] KVM: arm64/sve: Fix SVE trap restoration for non-current tasks Dave Martin
2018-06-14 11:42 ` [PATCH 4/4] KVM: arm64: Avoid mistaken attempts to save SVE state for vcpus Dave Martin
2018-06-15 8:50 ` Alex Bennée [this message]
2018-06-15 9:27 ` Dave Martin
2018-06-14 12:45 ` [PATCH 0/4] KVM: arm64: FPSIMD/SVE fixes for 4.17 Dave Martin
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=87po0szb4h.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).