From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Martin Subject: Re: [RFC PATCH 00/16] KVM: arm64: Initial support for SVE guests Date: Fri, 6 Jul 2018 10:05:36 +0100 Message-ID: <20180706090534.GD26019@e103592.cambridge.arm.com> References: <1529593060-542-1-git-send-email-Dave.Martin@arm.com> <87h8lc93jc.fsf@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id B63D449F8C for ; Fri, 6 Jul 2018 04:53:09 -0400 (EDT) Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ijn7e0-ZjoP2 for ; Fri, 6 Jul 2018 04:53:08 -0400 (EDT) Received: from foss.arm.com (foss.arm.com [217.140.101.70]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 86AAE408B1 for ; Fri, 6 Jul 2018 04:53:08 -0400 (EDT) Content-Disposition: inline In-Reply-To: <87h8lc93jc.fsf@linaro.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu To: Alex =?iso-8859-1?Q?Benn=E9e?= Cc: Okamoto Takayuki , Christoffer Dall , Ard Biesheuvel , Marc Zyngier , Catalin Marinas , Will Deacon , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org List-Id: kvmarm@lists.cs.columbia.edu On Fri, Jul 06, 2018 at 09:22:47AM +0100, Alex Benn=E9e wrote: > = > Dave Martin writes: > = > > > > > This series is somewhat tested on Arm Juno r0 and the Arm Fast Model > > (with/without SVE support). arch/arm builds, but I've not booted > > it -- only some trivial refactoring in this series affects arch/arm. > = > Now that QEMU linux-user SVE support is pretty much complete we've also > got preliminary patches for system emulation mode. However we currently > don't have VHE implemented so I guess we need to do that first before we > can test under QEMU. Qemu can use this as a KVM client without invasive changes, right? For kvmtool, it's just a question of checking/setting a feature flag in KVM_ARM_PREFERRED_TARGET and KVM_ARM_VCPU_INIT, and (eventually) doing at ioctl() to set the set of permitted vector lengths (not yet, this will come in a follow-up series). Cheers ---Dave