From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] arm64: smccc: Support SMCCC v1.3 SVE register saving hint
Date: Tue, 18 May 2021 14:01:06 +0100 [thread overview]
Message-ID: <20210518130106.GC4358@sirena.org.uk> (raw)
In-Reply-To: <87mtsstf15.wl-maz@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
On Tue, May 18, 2021 at 01:14:30PM +0100, Marc Zyngier wrote:
> Mark Brown <broonie@kernel.org> wrote:
> > I do see some ifdefery with __KVM_NVHE_HYPERVISOR__ elsewhere which
> > could be used to take care of that particular case either by
> > providing a __hyp mapping or just not trying to set the flag there
> > (the latter seems safer) but I'm guessing there's others. Do we
> > have a reliable way of identifying such contexts?
> __KVM_NVHE_HYPERVISOR__ usually is a good indication that we're
> compiling for the nVHE EL2 object. I guess that skipping the
> optimisation would be good enough for KVM, until we decide to provide
> a nVHE-specific helper that uses the private per-cpu information.
Yes, I think skipping it for now is going to be safest and it's
certainly easiest. I didn't *spot* any other affected cases, but eqally
I didn't spot this one first time around.
[-- 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-05-18 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 10:09 [PATCH v1 0/2] arm64: Implement SMCCC v1.3 SVE register saving hint Mark Brown
2021-05-18 10:09 ` [PATCH v1 1/2] arm64: asmlinkage: Enable use of BTI_C macro in SYM_CODE Mark Brown
2021-05-18 10:09 ` [PATCH v1 2/2] arm64: smccc: Support SMCCC v1.3 SVE register saving hint Mark Brown
2021-05-18 10:53 ` Marc Zyngier
2021-05-18 11:53 ` Mark Brown
2021-05-18 12:14 ` Marc Zyngier
2021-05-18 13:01 ` Mark Brown [this message]
2021-05-18 16:53 ` Ard Biesheuvel
2021-05-18 16:43 ` Sudeep Holla
2021-05-18 16:55 ` 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=20210518130106.GC4358@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=sudeep.holla@arm.com \
--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).