From: Andrew Jones <drjones@redhat.com> To: Marc Zyngier <marc.zyngier@arm.com> Cc: kvm@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Kristina Martsenko <kristina.martsenko@arm.com>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v6 25/26] arm64: KVM: Allow mapping of vectors outside of the RAM region Date: Thu, 15 Mar 2018 18:08:15 +0100 [thread overview] Message-ID: <20180315170815.vl53dw5hqr5agmuo@kamzik.brq.redhat.com> (raw) In-Reply-To: <941a937f-6466-4c8f-6952-d26c3142102d@arm.com> On Thu, Mar 15, 2018 at 04:17:53PM +0000, Marc Zyngier wrote: > On 15/03/18 15:54, Andrew Jones wrote: > > On Wed, Mar 14, 2018 at 04:50:48PM +0000, Marc Zyngier wrote: > >> static inline void *kvm_get_hyp_vector(void) > >> { > >> struct bp_hardening_data *data = arm64_get_bp_hardening_data(); > >> - void *vect = kvm_ksym_ref(__kvm_hyp_vector); > >> + void *vect = kern_hyp_va(kvm_ksym_ref(__kvm_hyp_vector)); > >> + int slot = -1; > >> > >> - if (data->fn) { > >> - vect = __bp_harden_hyp_vecs_start + > >> - data->hyp_vectors_slot * SZ_2K; > >> + if (cpus_have_const_cap(ARM64_HARDEN_BRANCH_PREDICTOR) && data->fn) { > > > > Now that I'm trying to consider heterogeneous systems, I'm wondering why > > harden BP isn't checked with this_cpu_has_cap() like harden EL2 vectors. > > I'm also wondering if it's even possible for CPUs to come up without all > > of them having harden EL2 vectors if the boot CPU has it. Won't > > verify_local_cpu_errata_workarounds() require it? I'm probably just > > getting lost in all the capability stuff... > > Checking harden BP on this particular CPU will only tell you if this CPU > is affected, but won't give you any additional information (i.e. you'd > still need to check obtain the stuff pointed to by data). > > Checking for *all* CPUs in one go has some advantages: it is a static > key, which means that unaffected platforms will fly (this is a hot path > on VHE), and you can check data if you're affected. Is there a problem with using the static key to check ARM64_HARDEN_EL2_VECTORS below? (Sorry, I'm still confused why we're not using the same functions for both.) If we can't use the static key below, then should we swap the check with !has_vhe() to ensure the compiler will avoid emitting the this_cpu_has_cap() call on VHE's fast path? I also noticed that calling this_cpu_has_cap() puts a constraint on kvm_get_hyp_vector() that it must never be called without preemption disabled. It's not, but it's one more thing to think about. If there's no reason not to use the static key with cpus_have_const_cap() then maybe we should? > > > > >> + vect = __bp_harden_hyp_vecs_start; > >> + slot = data->hyp_vectors_slot; > >> + } > >> > >> - if (!has_vhe()) > >> - vect = lm_alias(vect); > >> + if (this_cpu_has_cap(ARM64_HARDEN_EL2_VECTORS) && !has_vhe()) { > >> + vect = __kvm_bp_vect_base; > >> + if (slot == -1) > >> + slot = __kvm_harden_el2_vector_slot; > >> } Thanks, drew
WARNING: multiple messages have this Message-ID (diff)
From: drjones@redhat.com (Andrew Jones) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v6 25/26] arm64: KVM: Allow mapping of vectors outside of the RAM region Date: Thu, 15 Mar 2018 18:08:15 +0100 [thread overview] Message-ID: <20180315170815.vl53dw5hqr5agmuo@kamzik.brq.redhat.com> (raw) In-Reply-To: <941a937f-6466-4c8f-6952-d26c3142102d@arm.com> On Thu, Mar 15, 2018 at 04:17:53PM +0000, Marc Zyngier wrote: > On 15/03/18 15:54, Andrew Jones wrote: > > On Wed, Mar 14, 2018 at 04:50:48PM +0000, Marc Zyngier wrote: > >> static inline void *kvm_get_hyp_vector(void) > >> { > >> struct bp_hardening_data *data = arm64_get_bp_hardening_data(); > >> - void *vect = kvm_ksym_ref(__kvm_hyp_vector); > >> + void *vect = kern_hyp_va(kvm_ksym_ref(__kvm_hyp_vector)); > >> + int slot = -1; > >> > >> - if (data->fn) { > >> - vect = __bp_harden_hyp_vecs_start + > >> - data->hyp_vectors_slot * SZ_2K; > >> + if (cpus_have_const_cap(ARM64_HARDEN_BRANCH_PREDICTOR) && data->fn) { > > > > Now that I'm trying to consider heterogeneous systems, I'm wondering why > > harden BP isn't checked with this_cpu_has_cap() like harden EL2 vectors. > > I'm also wondering if it's even possible for CPUs to come up without all > > of them having harden EL2 vectors if the boot CPU has it. Won't > > verify_local_cpu_errata_workarounds() require it? I'm probably just > > getting lost in all the capability stuff... > > Checking harden BP on this particular CPU will only tell you if this CPU > is affected, but won't give you any additional information (i.e. you'd > still need to check obtain the stuff pointed to by data). > > Checking for *all* CPUs in one go has some advantages: it is a static > key, which means that unaffected platforms will fly (this is a hot path > on VHE), and you can check data if you're affected. Is there a problem with using the static key to check ARM64_HARDEN_EL2_VECTORS below? (Sorry, I'm still confused why we're not using the same functions for both.) If we can't use the static key below, then should we swap the check with !has_vhe() to ensure the compiler will avoid emitting the this_cpu_has_cap() call on VHE's fast path? I also noticed that calling this_cpu_has_cap() puts a constraint on kvm_get_hyp_vector() that it must never be called without preemption disabled. It's not, but it's one more thing to think about. If there's no reason not to use the static key with cpus_have_const_cap() then maybe we should? > > > > >> + vect = __bp_harden_hyp_vecs_start; > >> + slot = data->hyp_vectors_slot; > >> + } > >> > >> - if (!has_vhe()) > >> - vect = lm_alias(vect); > >> + if (this_cpu_has_cap(ARM64_HARDEN_EL2_VECTORS) && !has_vhe()) { > >> + vect = __kvm_bp_vect_base; > >> + if (slot == -1) > >> + slot = __kvm_harden_el2_vector_slot; > >> } Thanks, drew
next prev parent reply other threads:[~2018-03-15 17:08 UTC|newest] Thread overview: 124+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-14 16:50 [PATCH v6 00/26] KVM/arm64: Randomise EL2 mappings (variant 3a mitigation) Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 01/26] arm64: alternatives: Add dynamic patching feature Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 02/26] arm64: insn: Add N immediate encoding Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 03/26] arm64: insn: Add encoder for bitwise operations using literals Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 04/26] arm64: KVM: Dynamically patch the kernel/hyp VA mask Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 19:15 ` James Morse 2018-03-15 19:15 ` James Morse 2018-03-16 8:52 ` Marc Zyngier 2018-03-16 8:52 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 05/26] arm64: cpufeatures: Drop the ARM64_HYP_OFFSET_LOW feature flag Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 06/26] KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 19:16 ` James Morse 2018-03-15 19:16 ` James Morse 2018-03-16 9:31 ` Marc Zyngier 2018-03-16 9:31 ` Marc Zyngier 2018-03-16 11:35 ` Andrew Jones 2018-03-16 11:35 ` Andrew Jones 2018-03-16 11:38 ` Ard Biesheuvel 2018-03-16 11:38 ` Ard Biesheuvel 2018-03-16 11:51 ` Marc Zyngier 2018-03-16 11:51 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 07/26] KVM: arm/arm64: Demote HYP VA range display to being a debug feature Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 08/26] KVM: arm/arm64: Move ioremap calls to create_hyp_io_mappings Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 09/26] KVM: arm/arm64: Keep GICv2 HYP VAs in kvm_vgic_global_state Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 10/26] KVM: arm/arm64: Fix idmap size and alignment Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 19:15 ` James Morse 2018-03-15 19:15 ` James Morse 2018-03-16 8:55 ` Marc Zyngier 2018-03-16 8:55 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 11/26] KVM: arm64: Fix HYP idmap unmap when using 52bit PA Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-16 16:07 ` Catalin Marinas 2018-03-16 16:07 ` Catalin Marinas 2018-03-16 16:47 ` Suzuki K Poulose 2018-03-16 16:47 ` Suzuki K Poulose 2018-03-14 16:50 ` [PATCH v6 12/26] KVM: arm/arm64: Move HYP IO VAs to the "idmap" range Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 19:09 ` James Morse 2018-03-15 19:09 ` James Morse 2018-03-16 8:44 ` Marc Zyngier 2018-03-16 8:44 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 13/26] arm64; insn: Add encoder for the EXTR instruction Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 14/26] arm64: insn: Allow ADD/SUB (immediate) with LSL #12 Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 15/26] arm64: KVM: Dynamically compute the HYP VA mask Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 16/26] arm64: KVM: Introduce EL2 VA randomisation Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 17/26] arm64: Update the KVM memory map documentation Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 18/26] arm64: KVM: Move vector offsetting from hyp-init.S to kvm_get_hyp_vector Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 19/26] arm64: KVM: Move stashing of x0/x1 into the vector code itself Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 14:39 ` Andrew Jones 2018-03-15 14:39 ` Andrew Jones 2018-03-16 16:22 ` Catalin Marinas 2018-03-16 16:22 ` Catalin Marinas 2018-03-16 16:37 ` Marc Zyngier 2018-03-16 16:37 ` Marc Zyngier 2018-03-16 16:38 ` Marc Zyngier 2018-03-16 16:38 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 20/26] arm64: KVM: Move BP hardening vectors into .hyp.text section Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 14:42 ` Andrew Jones 2018-03-15 14:42 ` Andrew Jones 2018-03-16 16:24 ` Catalin Marinas 2018-03-16 16:24 ` Catalin Marinas 2018-03-14 16:50 ` [PATCH v6 21/26] arm64: KVM: Reserve 4 additional instructions in the BPI template Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 14:46 ` Andrew Jones 2018-03-15 14:46 ` Andrew Jones 2018-03-16 16:30 ` Catalin Marinas 2018-03-16 16:30 ` Catalin Marinas 2018-03-14 16:50 ` [PATCH v6 22/26] arm64: KVM: Allow far branches from vector slots to the main vectors Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 23/26] arm/arm64: KVM: Introduce EL2-specific executable mappings Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 15:03 ` Andrew Jones 2018-03-15 15:03 ` Andrew Jones 2018-03-15 15:53 ` Marc Zyngier 2018-03-15 15:53 ` Marc Zyngier 2018-03-14 16:50 ` [PATCH v6 24/26] arm64: Make BP hardening slot counter available Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 15:05 ` Andrew Jones 2018-03-15 15:05 ` Andrew Jones 2018-03-14 16:50 ` [PATCH v6 25/26] arm64: KVM: Allow mapping of vectors outside of the RAM region Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 15:54 ` Andrew Jones 2018-03-15 15:54 ` Andrew Jones 2018-03-15 16:17 ` Marc Zyngier 2018-03-15 16:17 ` Marc Zyngier 2018-03-15 17:08 ` Andrew Jones [this message] 2018-03-15 17:08 ` Andrew Jones 2018-03-15 18:47 ` Marc Zyngier 2018-03-15 18:47 ` Marc Zyngier 2018-03-16 12:33 ` Andrew Jones 2018-03-16 12:33 ` Andrew Jones 2018-03-14 16:50 ` [PATCH v6 26/26] arm64: Enable ARM64_HARDEN_EL2_VECTORS on Cortex-A57 and A72 Marc Zyngier 2018-03-14 16:50 ` Marc Zyngier 2018-03-15 15:57 ` [PATCH v6 00/26] KVM/arm64: Randomise EL2 mappings (variant 3a mitigation) Andrew Jones 2018-03-15 15:57 ` Andrew Jones 2018-03-15 16:19 ` Marc Zyngier 2018-03-15 16:19 ` Marc Zyngier 2018-03-15 16:40 ` Andrew Jones 2018-03-15 16:40 ` Andrew Jones 2018-03-15 16:52 ` Marc Zyngier 2018-03-15 16:52 ` Marc Zyngier 2018-03-16 17:46 ` Catalin Marinas 2018-03-16 17:46 ` Catalin Marinas 2018-03-16 18:05 ` Marc Zyngier 2018-03-16 18:05 ` 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=20180315170815.vl53dw5hqr5agmuo@kamzik.brq.redhat.com \ --to=drjones@redhat.com \ --cc=catalin.marinas@arm.com \ --cc=kristina.martsenko@arm.com \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=marc.zyngier@arm.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.