From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 558E0C55178 for ; Wed, 21 Oct 2020 14:39:42 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D3BBE2224E for ; Wed, 21 Oct 2020 14:39:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="wDs/YFKn" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D3BBE2224E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=K/16Iv6RJJSA9QEaOXtgHwQUwCpzXkjSUT+KrJdOLcs=; b=wDs/YFKnyUEMHHoSl9YcJhH25 zsMPuhP+gO5n0h/eTBAAgEE7vQRZxvMQmlgjFUoJz6DHIs1n8H2mmOrzZvTqi36q/AJA9HqHXmOY1 q6ysF34/kHAEnFKdoZDYRZofo4ahcJmQ+I73WATCmpDL346NxagJeYnAETY+bcwmWsXKtrcyY6YnZ N+/rPtojOufgy8Y/I1g92jTMv9A6wYPW7oZcj5/l4Te0D+bkQ++WGLXlRrfpVL8WWLL2vBwBAizEG ki95XZuVN9C8509ptbdfAtNMumPAcXx1erlji9xC3jnaACbcva6QznBpcQ6qOWYY8b3qwIuv1b9En hBafGnQ/w==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kVFFt-0006EH-OP; Wed, 21 Oct 2020 14:38:21 +0000 Received: from foss.arm.com ([217.140.110.172]) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kVFFr-0006D8-3s for linux-arm-kernel@lists.infradead.org; Wed, 21 Oct 2020 14:38:20 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 25481D6E; Wed, 21 Oct 2020 07:38:18 -0700 (PDT) Received: from e107158-lin (e107158-lin.cambridge.arm.com [10.1.194.78]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C94013F66B; Wed, 21 Oct 2020 07:38:16 -0700 (PDT) Date: Wed, 21 Oct 2020 15:38:14 +0100 From: Qais Yousef To: Marc Zyngier Subject: Re: [RFC PATCH v2 1/4] arm64: kvm: Handle Asymmetric AArch32 systems Message-ID: <20201021143814.vpad2dfg7gplvghy@e107158-lin> References: <20201021104611.2744565-1-qais.yousef@arm.com> <20201021104611.2744565-2-qais.yousef@arm.com> <4035e634eb2bfce4b88a159b2ec2f267@kernel.org> <20201021133543.zeyghjzujivnds2d@e107158-lin> <87587dbfb7bee53eca4d1b837fd8194a@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <87587dbfb7bee53eca4d1b837fd8194a@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201021_103819_252969_9503E063 X-CRM114-Status: GOOD ( 30.89 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arch@vger.kernel.org, Will Deacon , "Peter Zijlstra \(Intel\)" , Catalin Marinas , James Morse , Greg Kroah-Hartman , Linus Torvalds , Morten Rasmussen , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 10/21/20 14:51, Marc Zyngier wrote: > On 2020-10-21 14:35, Qais Yousef wrote: > > On 10/21/20 13:02, Marc Zyngier wrote: > > > On 2020-10-21 11:46, Qais Yousef wrote: > > > > On a system without uniform support for AArch32 at EL0, it is possible > > > > for the guest to force run AArch32 at EL0 and potentially cause an > > > > illegal exception if running on the wrong core. > > > > > > s/the wrong core/a core without AArch32/ > > > > > > > > > > > Add an extra check to catch if the guest ever does that and prevent it > > > > > > Not "if the guest ever does that". Rather "let's hope we are lucky > > > enough > > > to catch the guest doing that". > > > > > > > from running again by resetting vcpu->arch.target and return > > > > ARM_EXCEPTION_IL. > > > > > > > > We try to catch this misbehavior as early as possible and not rely on > > > > PSTATE.IL to occur. > > > > > > > > Tested on Juno by instrumenting the host to: > > > > > > > > * Fake asym aarch32. > > > > * Instrument KVM to make the asymmetry visible to the guest. > > > > > > > > Any attempt to run 32bit app in the guest will produce such error on > > > > qemu: > > > > > > Not *any* attempt. Only the ones where the guest exits whilst in > > > AArch32 EL0. It is perfectly possible for the guest to use AArch32 > > > undetected for quite a while. > > > > Thanks Marc! I'll change them all. > > > > > > > > > > # ./test > > > > error: kvm run failed Invalid argument > > > > PC=ffff800010945080 X00=ffff800016a45014 X01=ffff800010945058 > > > > X02=ffff800016917190 X03=0000000000000000 X04=0000000000000000 > > > > X05=00000000fffffffb X06=0000000000000000 X07=ffff80001000bab0 > > > > X08=0000000000000000 X09=0000000092ec5193 X10=0000000000000000 > > > > X11=ffff80001608ff40 X12=ffff000075fcde86 X13=ffff000075fcde88 > > > > X14=ffffffffffffffff X15=ffff00007b2105a8 X16=ffff00007b006d50 > > > > X17=0000000000000000 X18=0000000000000000 X19=ffff00007a82b000 > > > > X20=0000000000000000 X21=ffff800015ccd158 X22=ffff00007a82b040 > > > > X23=ffff00007a82b008 X24=0000000000000000 X25=ffff800015d169b0 > > > > X26=ffff8000126d05bc X27=0000000000000000 X28=0000000000000000 > > > > X29=ffff80001000ba90 X30=ffff80001093f3dc SP=ffff80001000ba90 > > > > PSTATE=60000005 -ZC- EL1h > > > > qemu-system-aarch64: Failed to get KVM_REG_ARM_TIMER_CNT > > > > > > It'd be worth working out: > > > - why does this show an AArch64 mode it we caught the vcpu in AArch32? > > > - why does QEMU shout about the timer register? > > > > /me puts a monocular on > > > > Which bit is the AArch64? > > It clearly spits out "EL1h", and PSTATE.M is 5, also consistent with EL1h. > > > It did surprise me that it is shouting about the timer. My guess was > > that > > a timer interrupt at the guest between exit/reentry caused the state > > change and > > the failure to read the timer register? Since the target is no longer > > valid it > > falls over, hopefully as expected. I could have been naive of course. > > That > > explanation made sense to my mind so I didn't dig further. > > Userspace is never involved with the timer interrupt, unless you've elected > to have the interrupt controller in userspace, which I seriously doubt. > > As we are introducing a change to the userspace ABI, it'd be interesting > to find out what is happening here. Sure. Let me educate myself more about this and find a way to interrogate qemu and KVM. Thanks -- Qais Yousef _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel