From: Marc Zyngier <marc.zyngier@arm.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Andrey Konovalov <andreyknvl@google.com>,
Stephen Hines <srhines@google.com>,
Greg Hackmann <ghackmann@google.com>,
christoffer.dall@linaro.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, LKML <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sami Tolvanen <samitolvanen@google.com>,
takahiro.akashi@linaro.org
Subject: Re: arm64 kvm built with clang doesn't boot
Date: Fri, 16 Mar 2018 17:18:13 +0000 [thread overview]
Message-ID: <38b3c636-38cd-2cc5-79d0-8ccf234e2b26@arm.com> (raw)
In-Reply-To: <CAKwvOd=-TeLJn9=V_Dmj-X+qcRBcfH8tcktbm33xAx671VCYUw@mail.gmail.com>
On 16/03/18 16:52, Nick Desaulniers wrote:
[dropping kernel-dynamic-tools@google.com which keeps bouncing]
> Is this in regards to: commit "arm64: Add ARM_SMCCC_ARCH_WORKAROUND_1 BP
> hardening support"? Has anyone tried to upstream a fix for this? We
> probably want to be very explicit with register widths here.
What do you mean? The current code is as strict as it gets, and
explicitly tells the compiler to use the right register width, based on
the SMC call parameter types.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-03-16 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 13:49 arm64 kvm built with clang doesn't boot Andrey Konovalov
2018-03-16 14:13 ` Mark Rutland
2018-03-16 14:31 ` Mark Rutland
2018-03-16 14:55 ` Andrey Konovalov
2018-04-12 17:35 ` Andrey Konovalov
2018-03-16 14:50 ` Andrey Konovalov
2018-03-16 14:13 ` Marc Zyngier
2018-03-16 14:53 ` Andrey Konovalov
2018-03-16 15:00 ` Marc Zyngier
2018-03-16 16:52 ` Nick Desaulniers
2018-03-16 17:13 ` Mark Rutland
2018-03-17 10:19 ` Ard Biesheuvel
2018-03-16 17:18 ` Marc Zyngier [this message]
2018-03-19 17:42 ` Nick Desaulniers
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=38b3c636-38cd-2cc5-79d0-8ccf234e2b26@arm.com \
--to=marc.zyngier@arm.com \
--cc=andreyknvl@google.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=ghackmann@google.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=srhines@google.com \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.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 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).