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=-14.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 AF2B5C433DB for ; Tue, 9 Mar 2021 14:27:05 +0000 (UTC) Received: from desiato.infradead.org (desiato.infradead.org [90.155.92.199]) (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 2D057651B2 for ; Tue, 9 Mar 2021 14:27:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2D057651B2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org 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=desiato.20200630; h=Sender:Content-Transfer-Encoding :Content-Type:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To:Subject:Cc:To: From:Message-ID:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=GxMd0vyKLYBZpeDEm7TZPF0YbYXj2cjGDg0K7NiszV4=; b=G4DDhUe/9bJdKOZ2ec6i7FtBu nGlHCeqVgwkzG3H2nRampN0sBjv3JFEk4N2IvF6Hzm/hRBV+boCeWW8rqfOXUfWzJy+YfULODkZBF 7LeiI+cGzPn6BRl2bzp0n752LFeQ/Z6Kzugz+CCmnMPApDsrtR4kaOU5k1L7CwqPaOD7FQYlK/OlP ysiZnDYVR2fvLUoA7pmx45RyiBbg3na3ARHG3dtjkL9hmTUngbAO8I4MohkW0gdOBht1+l5Z/tgJp 0IDgSHLP2O8Da9POdC1OeVFvhFZ5A1xPSQR/HszXo/s1Fsh96L1Rn8j+pRvPccW9X6TTDaBZnrMo7 9DLeskUOA==; Received: from localhost ([::1] helo=desiato.infradead.org) by desiato.infradead.org with esmtp (Exim 4.94 #2 (Red Hat Linux)) id 1lJdIQ-004plY-Pq; Tue, 09 Mar 2021 14:25:15 +0000 Received: from mail.kernel.org ([198.145.29.99]) by desiato.infradead.org with esmtps (Exim 4.94 #2 (Red Hat Linux)) id 1lJdIK-004pkq-B1 for linux-arm-kernel@lists.infradead.org; Tue, 09 Mar 2021 14:25:10 +0000 Received: from disco-boy.misterjones.org (disco-boy.misterjones.org [51.254.78.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 71E15651B2; Tue, 9 Mar 2021 14:25:06 +0000 (UTC) Received: from 78.163-31-62.static.virginmediabusiness.co.uk ([62.31.163.78] helo=why.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1lJdIG-000ZGV-Bc; Tue, 09 Mar 2021 14:25:04 +0000 Date: Tue, 09 Mar 2021 14:25:03 +0000 Message-ID: <87lfawxv40.wl-maz@kernel.org> From: Marc Zyngier To: Suzuki Poulose Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, James Morse , Julien Thierry , Alexandru Elisei , kernel-team@android.com Subject: Re: [PATCH] KVM: arm64: Cap default IPA size to the host's own size In-Reply-To: References: <20210308174643.761100-1-maz@kernel.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") X-SA-Exim-Connect-IP: 62.31.163.78 X-SA-Exim-Rcpt-To: suzuki.poulose@arm.com, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, james.morse@arm.com, julien.thierry.kdev@gmail.com, alexandru.elisei@arm.com, kernel-team@android.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210309_142508_745051_BA12E97F X-CRM114-Status: GOOD ( 33.79 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 Hi Suzuki, On Tue, 09 Mar 2021 11:09:48 +0000, Suzuki Poulose wrote: > > > > > On 8 Mar 2021, at 17:46, Marc Zyngier wrote: > > > > KVM/arm64 has forever used a 40bit default IPA space, partially > > due to its 32bit heritage (where the only choice is 40bit). > > > > However, there are implementations in the wild that have a *cough* > > much smaller *cough* IPA space, which leads to a misprogramming of > > VTCR_EL2, and a guest that is stuck on its first memory access > > if userspace dares to ask for the default IPA setting (which most > > VMMs do). > > > > Instead, cap the default IPA size to what the host can actually > > do, and spit out a one-off message on the console. The boot warning > > is turned into a more meaningfull message, and the new behaviour > > is also documented. > > > > Although this is a userspace ABI change, it doesn't really change > > much for userspace: > > > > - the guest couldn't run before this change, while it now has > > a chance to if the memory range fits the reduced IPA space > > > > - a memory slot that was accepted because it did fit the default > > IPA space but didn't fit the HW constraints is now properly > > rejected > > > > The other thing that's left doing is to convince userspace to > > actually use the IPA space setting instead of relying on the > > antiquated default. > > > > Signed-off-by: Marc Zyngier > > --- > > Reviewed-by: Suzuki K Poulose Thanks for that. Whilst I have your attention and given that you are responsible for most of the variable IPA stuff... ;-) I think we have another issue around the handling of our IPA size. Let's say I create a VM with a 32bit IPA space. If I register a 2GB memslot at 0x8000000, I'm getting an error, which I think is bogus. I came to the conclusion that kvm_arch_prepare_memory_region() is a bit overzealous when rejecting the memslot, and I used the following patchlet to address it. Does this seem sensible to you? M. diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c index 77cb2d28f2a4..8711894db8c2 100644 --- a/arch/arm64/kvm/mmu.c +++ b/arch/arm64/kvm/mmu.c @@ -1312,8 +1312,7 @@ int kvm_arch_prepare_memory_region(struct kvm *kvm, * Prevent userspace from creating a memory region outside of the IPA * space addressable by the KVM guest IPA space. */ - if (memslot->base_gfn + memslot->npages >= - (kvm_phys_size(kvm) >> PAGE_SHIFT)) + if ((memslot->base_gfn + memslot->npages) > (kvm_phys_size(kvm) >> PAGE_SHIFT)) return -EFAULT; mmap_read_lock(current->mm); -- Without deviation from the norm, progress is not possible. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel