From: Marc Zyngier <marc.zyngier@arm.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Stephen Hines <srhines@google.com>,
Greg Hackmann <ghackmann@google.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
kvmarm@lists.cs.columbia.edu, LKML <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
kernel-dynamic-tools <kernel-dynamic-tools@google.com>
Subject: Re: arm64 kvm built with clang doesn't boot
Date: Fri, 16 Mar 2018 15:00:38 +0000 [thread overview]
Message-ID: <2e84a842-96e8-aec4-8b85-9ee879bb323a@arm.com> (raw)
In-Reply-To: <CAAeHK+zq4-mw3pCNf3nob3gN-s+aWVq7vUy1p8yY4bU4QYNNMg@mail.gmail.com>
On 16/03/18 14:53, Andrey Konovalov wrote:
> On Fri, Mar 16, 2018 at 3:13 PM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> I wasn't aware of that discussion, but this is indeed quite annoying.
>> Note that you should be able to restrict this to arch/arm64/kvm/hyp/*
>> and virt/kvm/arm/hyp/*.
>
> That works as well (tried it, the kernel boots). I've also tried
> compiling without the flag for virt/kvm/arm/hyp/*, it boots as well.
That's just luck. Anything in a hyp/ directory has the potential to be
executed at EL2, and thus could be generating these jump tables. It
could blow up at a later time, once you start running VMs...
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-03-16 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 13:49 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 [this message]
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
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=2e84a842-96e8-aec4-8b85-9ee879bb323a@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=kernel-dynamic-tools@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=srhines@google.com \
--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
all inboxes | Powered by JetHome®