From: Dave Martin <Dave.Martin@arm.com> To: Julien Thierry <julien.thierry@arm.com> Cc: Okamoto Takayuki <tokamoto@jp.fujitsu.com>, Christoffer Dall <cdall@kernel.org>, Ard Biesheuvel <ard.biesheuvel@linaro.org>, Marc Zyngier <marc.zyngier@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Zhang Lei <zhang.lei@jp.fujitsu.com>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v5 06/26] arm64/sve: Check SVE virtualisability Date: Fri, 1 Mar 2019 14:44:52 +0000 [thread overview] Message-ID: <20190301144452.GG3567@e103592.cambridge.arm.com> (raw) In-Reply-To: <d8d4d25d-13b7-be23-77bb-7cf498c8463a@arm.com> On Fri, Mar 01, 2019 at 12:39:52PM +0000, Julien Thierry wrote: > > > On 26/02/2019 12:06, Dave Martin wrote: > > On Wed, Feb 20, 2019 at 11:12:49AM +0000, Julien Thierry wrote: > >> Hi Dave, > >> > >> On 18/02/2019 19:52, Dave Martin wrote: [...] > >>> + /* > >>> + * Mismatches above sve_max_virtualisable_vl are fine, since > >>> + * no guest is allowed to configure ZCR_EL2.LEN to exceed this: > >>> + */ > >>> + if (sve_vl_from_vq(bit_to_vq(b)) <= sve_max_virtualisable_vl) { > >>> + pr_warn("SVE: cpu%d: Unsupported vector length(s) present\n", > >> > >> Nit: might be good to specify that the vector length is unsupported for > >> virtualisation. > >> > >> Also, since KVM is the one deciding what to do with the information, > >> should we have a warning here? But I can understand that knowing which > >> CPUs are introducing unsupported vector length, maybe using pr_devel() > >> instead of pr_warn() > > > > These warnings are really for consumption by SoC vendors, not users: > > my aim is to flag up systems that we consider broken (or at least, > > unsuitable for running KVM). > > > > So I prefer to make this noisy and limit the amount of "useful" > > information people might be tempted to programmatically scrape from > > dmesg. > > > > cpufeatures uses pr_warn("SANITY CHECK: [...]") here. Maybe I should > > stick "SANITY CHECK" in here too? I will also try to make the commit > > message more explicit and/or add comments to make the intent of the code > > clearer. > > > > It may also make sense to make this noise even if KVM isn't enabled > > (which is a rare case anyhow). > > > > Thoughts? > > As I explained later in the patch series, I missed the fact that this > function was for late secondary CPUs. I think things are fine like this > (just add the bit about the vector lenght not being supported for > virtualisation). I've now reworked all this a bit: I probe for the largest vector length than be offered to guests, and if this is less than the host's maximum vector length then I print a one-off warning saying what limit KVM is clamping guests' vector length to. Elsewhere, I now just use the probed value as the maximum vector length, rather than duplicating the bounds checking logic. This approach seems simpler, and is hoepfully a bit more self- explanatory -- so please take a look when I repost :) Cheers ---Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Martin <Dave.Martin@arm.com> To: Julien Thierry <julien.thierry@arm.com> Cc: Okamoto Takayuki <tokamoto@jp.fujitsu.com>, Christoffer Dall <cdall@kernel.org>, Ard Biesheuvel <ard.biesheuvel@linaro.org>, Marc Zyngier <marc.zyngier@arm.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will.deacon@arm.com>, Zhang Lei <zhang.lei@jp.fujitsu.com>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v5 06/26] arm64/sve: Check SVE virtualisability Date: Fri, 1 Mar 2019 14:44:52 +0000 [thread overview] Message-ID: <20190301144452.GG3567@e103592.cambridge.arm.com> (raw) In-Reply-To: <d8d4d25d-13b7-be23-77bb-7cf498c8463a@arm.com> On Fri, Mar 01, 2019 at 12:39:52PM +0000, Julien Thierry wrote: > > > On 26/02/2019 12:06, Dave Martin wrote: > > On Wed, Feb 20, 2019 at 11:12:49AM +0000, Julien Thierry wrote: > >> Hi Dave, > >> > >> On 18/02/2019 19:52, Dave Martin wrote: [...] > >>> + /* > >>> + * Mismatches above sve_max_virtualisable_vl are fine, since > >>> + * no guest is allowed to configure ZCR_EL2.LEN to exceed this: > >>> + */ > >>> + if (sve_vl_from_vq(bit_to_vq(b)) <= sve_max_virtualisable_vl) { > >>> + pr_warn("SVE: cpu%d: Unsupported vector length(s) present\n", > >> > >> Nit: might be good to specify that the vector length is unsupported for > >> virtualisation. > >> > >> Also, since KVM is the one deciding what to do with the information, > >> should we have a warning here? But I can understand that knowing which > >> CPUs are introducing unsupported vector length, maybe using pr_devel() > >> instead of pr_warn() > > > > These warnings are really for consumption by SoC vendors, not users: > > my aim is to flag up systems that we consider broken (or at least, > > unsuitable for running KVM). > > > > So I prefer to make this noisy and limit the amount of "useful" > > information people might be tempted to programmatically scrape from > > dmesg. > > > > cpufeatures uses pr_warn("SANITY CHECK: [...]") here. Maybe I should > > stick "SANITY CHECK" in here too? I will also try to make the commit > > message more explicit and/or add comments to make the intent of the code > > clearer. > > > > It may also make sense to make this noise even if KVM isn't enabled > > (which is a rare case anyhow). > > > > Thoughts? > > As I explained later in the patch series, I missed the fact that this > function was for late secondary CPUs. I think things are fine like this > (just add the bit about the vector lenght not being supported for > virtualisation). I've now reworked all this a bit: I probe for the largest vector length than be offered to guests, and if this is less than the host's maximum vector length then I print a one-off warning saying what limit KVM is clamping guests' vector length to. Elsewhere, I now just use the probed value as the maximum vector length, rather than duplicating the bounds checking logic. This approach seems simpler, and is hoepfully a bit more self- explanatory -- so please take a look when I repost :) Cheers ---Dave _______________________________________________ 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:[~2019-03-01 14:44 UTC|newest] Thread overview: 189+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-18 19:52 [PATCH v5 00/26] KVM: arm64: SVE guest support Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 01/26] KVM: Documentation: Document arm64 core registers in detail Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-21 11:48 ` Julien Grall 2019-02-21 11:48 ` Julien Grall 2019-02-26 12:05 ` Dave Martin 2019-02-26 12:05 ` Dave Martin 2019-02-21 11:57 ` Peter Maydell 2019-02-21 11:57 ` Peter Maydell 2019-02-18 19:52 ` [PATCH v5 02/26] arm64: fpsimd: Always set TIF_FOREIGN_FPSTATE on task state flush Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-21 12:39 ` Julien Grall 2019-02-26 12:06 ` Dave Martin 2019-02-26 12:06 ` Dave Martin 2019-02-26 12:35 ` Julien Grall 2019-02-26 12:35 ` Julien Grall 2019-02-18 19:52 ` [PATCH v5 03/26] KVM: arm64: Delete orphaned declaration for __fpsimd_enabled() Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 04/26] KVM: arm64: Refactor kvm_arm_num_regs() for easier maintenance Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 05/26] KVM: arm64: Add missing #include of <linux/bitmap.h> to kvm_host.h Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 15:23 ` Mark Rutland 2019-02-20 15:23 ` Mark Rutland 2019-02-26 12:06 ` Dave Martin 2019-02-26 12:06 ` Dave Martin 2019-02-26 12:31 ` Mark Rutland 2019-02-26 12:33 ` Dave Martin 2019-02-26 12:33 ` Dave Martin 2019-02-26 12:40 ` Mark Rutland 2019-02-26 12:40 ` Mark Rutland 2019-02-18 19:52 ` [PATCH v5 06/26] arm64/sve: Check SVE virtualisability Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 11:12 ` Julien Thierry 2019-02-20 11:12 ` Julien Thierry 2019-02-26 12:06 ` Dave Martin 2019-02-26 12:06 ` Dave Martin 2019-03-01 12:39 ` Julien Thierry 2019-03-01 12:39 ` Julien Thierry 2019-03-01 14:44 ` Dave Martin [this message] 2019-03-01 14:44 ` Dave Martin 2019-02-21 13:36 ` Julien Grall 2019-02-21 13:36 ` Julien Grall 2019-02-26 12:06 ` Dave Martin 2019-02-26 12:06 ` Dave Martin 2019-02-26 15:43 ` Julien Grall 2019-02-26 15:43 ` Julien Grall 2019-02-18 19:52 ` [PATCH v5 07/26] arm64/sve: Clarify role of the VQ map maintenance functions Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 11:43 ` Julien Thierry 2019-02-20 11:43 ` Julien Thierry 2019-02-26 12:06 ` Dave Martin 2019-02-26 12:06 ` Dave Martin 2019-02-21 13:46 ` Julien Grall 2019-02-21 13:46 ` Julien Grall 2019-02-26 12:07 ` Dave Martin 2019-02-26 12:07 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 08/26] arm64/sve: Enable SVE state tracking for non-task contexts Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-22 15:26 ` Julien Grall 2019-02-22 15:26 ` Julien Grall 2019-02-26 12:07 ` Dave Martin 2019-02-26 12:07 ` Dave Martin 2019-02-26 15:49 ` Julien Grall 2019-02-26 15:49 ` Julien Grall 2019-02-26 15:58 ` Dave Martin 2019-02-26 15:58 ` Dave Martin 2019-02-26 15:59 ` Julien Grall 2019-02-26 15:59 ` Julien Grall 2019-02-26 16:03 ` Dave Martin 2019-02-26 16:03 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 09/26] KVM: arm64: Add a vcpu flag to control SVE visibility for the guest Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 10/26] KVM: arm64: Propagate vcpu into read_id_reg() Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 11/26] KVM: arm64: Extend reset_unknown() to handle mixed RES0/UNKNOWN registers Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 13:33 ` Julien Thierry 2019-02-20 13:33 ` Julien Thierry 2019-02-26 12:07 ` Dave Martin 2019-02-26 12:07 ` Dave Martin 2019-02-22 16:04 ` Julien Grall 2019-02-22 16:04 ` Julien Grall 2019-02-18 19:52 ` [PATCH v5 12/26] KVM: arm64: Support runtime sysreg visibility filtering Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 14:33 ` Julien Thierry 2019-02-20 14:33 ` Julien Thierry 2019-02-26 12:07 ` Dave Martin 2019-02-26 12:07 ` Dave Martin 2019-02-20 15:37 ` Mark Rutland 2019-02-20 15:37 ` Mark Rutland 2019-02-26 12:12 ` Dave Martin 2019-02-26 12:12 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 13/26] KVM: arm64/sve: System register context switch and access support Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 16:48 ` Julien Thierry 2019-02-20 16:48 ` Julien Thierry 2019-02-26 16:32 ` Julien Grall 2019-02-26 16:32 ` Julien Grall 2019-02-26 17:01 ` Dave Martin 2019-02-26 17:01 ` Dave Martin 2019-02-27 12:02 ` Julien Grall 2019-02-27 12:02 ` Julien Grall 2019-02-27 13:50 ` Dave Martin 2019-02-27 13:50 ` Dave Martin 2019-02-27 14:17 ` Julien Grall 2019-02-27 14:17 ` Julien Grall 2019-02-27 14:38 ` Dave Martin 2019-02-27 14:38 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 14/26] KVM: arm64/sve: Context switch the SVE registers Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 16:19 ` Mark Rutland 2019-02-20 16:19 ` Mark Rutland 2019-02-26 12:13 ` Dave Martin 2019-02-26 12:13 ` Dave Martin 2019-02-20 16:46 ` Julien Thierry 2019-02-20 16:46 ` Julien Thierry 2019-02-26 12:13 ` Dave Martin 2019-02-26 12:13 ` Dave Martin 2019-02-26 16:56 ` Julien Grall 2019-02-26 16:56 ` Julien Grall 2019-02-27 13:37 ` Dave Martin 2019-02-27 13:37 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 15/26] KVM: Allow 2048-bit register access via ioctl interface Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 16/26] KVM: arm64: Add missing #include of <linux/string.h> in guest.c Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 17/26] KVM: arm64: Reject ioctl access to FPSIMD V-regs on SVE vcpus Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-21 12:06 ` Julien Thierry 2019-02-21 12:06 ` Julien Thierry 2019-02-26 12:13 ` Dave Martin 2019-02-26 12:13 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 18/26] KVM: arm64/sve: Add SVE support to register access ioctl interface Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-21 15:23 ` Julien Thierry 2019-02-21 15:23 ` Julien Thierry 2019-02-26 12:13 ` Dave Martin 2019-02-26 12:13 ` Dave Martin 2019-03-01 13:03 ` Julien Thierry 2019-03-01 13:03 ` Julien Thierry 2019-03-01 14:45 ` Dave Martin 2019-03-01 14:45 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 19/26] KVM: arm64: Enumerate SVE register indices for KVM_GET_REG_LIST Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-21 16:28 ` Julien Thierry 2019-02-21 16:28 ` Julien Thierry 2019-02-18 19:52 ` [PATCH v5 20/26] arm64/sve: In-kernel vector length availability query interface Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 21/26] KVM: arm/arm64: Add hook to finalize the vcpu configuration Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 22/26] KVM: arm64/sve: Add pseudo-register for the guest's vector lengths Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-21 17:48 ` Julien Thierry 2019-02-21 17:48 ` Julien Thierry 2019-02-26 12:13 ` Dave Martin 2019-02-26 12:13 ` Dave Martin 2019-03-01 13:28 ` Julien Thierry 2019-03-01 13:28 ` Julien Thierry 2019-03-01 14:55 ` Dave Martin 2019-03-01 14:55 ` Dave Martin 2019-03-07 13:47 ` Marc Zyngier 2019-03-07 13:47 ` Marc Zyngier 2019-03-07 15:30 ` Dave Martin 2019-03-07 15:30 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 23/26] KVM: arm64/sve: Allow userspace to enable SVE for vcpus Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-22 9:05 ` Julien Thierry 2019-02-22 9:05 ` Julien Thierry 2019-02-26 12:13 ` Dave Martin 2019-02-26 12:13 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 24/26] KVM: arm64: Add a capabillity to advertise SVE support Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-22 9:10 ` Julien Thierry 2019-02-22 9:10 ` Julien Thierry 2019-02-26 12:14 ` Dave Martin 2019-02-26 12:14 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 25/26] KVM: Document errors for KVM_GET_ONE_REG and KVM_SET_ONE_REG Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-18 19:52 ` [PATCH v5 26/26] KVM: arm64/sve: Document KVM API extensions for SVE Dave Martin 2019-02-18 19:52 ` Dave Martin 2019-02-20 15:47 ` [PATCH v5 00/26] KVM: arm64: SVE guest support Dave Martin 2019-02-20 15:47 ` Dave Martin 2019-03-03 2:40 ` Zhang, Lei 2019-03-05 9:47 ` Dave Martin 2019-03-05 9:47 ` Dave Martin 2019-03-08 7:06 ` Zhang, Lei 2019-03-08 7:06 ` Zhang, Lei
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=20190301144452.GG3567@e103592.cambridge.arm.com \ --to=dave.martin@arm.com \ --cc=ard.biesheuvel@linaro.org \ --cc=catalin.marinas@arm.com \ --cc=cdall@kernel.org \ --cc=julien.thierry@arm.com \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=marc.zyngier@arm.com \ --cc=tokamoto@jp.fujitsu.com \ --cc=will.deacon@arm.com \ --cc=zhang.lei@jp.fujitsu.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.