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 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BD62BC352A1 for ; Wed, 30 Nov 2022 07:54:25 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p0Hun-0006iq-4Q; Wed, 30 Nov 2022 02:53:57 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0Hum-0006fJ-3p for qemu-devel@nongnu.org; Wed, 30 Nov 2022 02:53:56 -0500 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0Huk-0001oA-7y for qemu-devel@nongnu.org; Wed, 30 Nov 2022 02:53:55 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 73D2161A3E; Wed, 30 Nov 2022 07:53:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CDC1AC433D6; Wed, 30 Nov 2022 07:53:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669794830; bh=nQaIa5rNcdI8wQq61b67qHwGb3JB8fNnY2LxJv/L0Q4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=p3F4IP4wvMIxoYShZs4/HYG6UGGTv+cPDLhpMuHMThm9U4HgVHgxmWm3ZuAi/g+PU Zw/ZqMdOEKfTSGUKSgxpp3UeXFrbe24RqG0Vwpv7J0CqTSGUP8/w/fF7y6mW+A4XaV fPVHVsk4wyqa3vblAfKezVTdK4GC6bu7U7ILYOZ3oHsKQj6lcQKaE2utGltLQIy6dh vRCondyD9Y0FXcjA7KbTGvickC6eMWxnGF5N1/E11vedaF0j12+i1EVTftePxqZXoh 9r26ScKuITJgIaiE6sUnLlPoZ17Z4FzND38gX/gVi8GzzMtdJgY4VkI/Z5n0yacL89 Ltd/0nBxzyLyA== Received: from ip-185-104-136-29.ptr.icomera.net ([185.104.136.29] helo=wait-a-minute.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1p0Hue-009WlQ-Da; Wed, 30 Nov 2022 07:53:48 +0000 Date: Wed, 30 Nov 2022 07:53:42 +0000 Message-ID: <87r0xkubcp.wl-maz@kernel.org> From: Marc Zyngier To: "chenxiang (M)" Cc: , , , , chenxiang via , "linuxarm@huawei.com" Subject: Re: regression: insmod module failed in VM with nvdimm on In-Reply-To: References: 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") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.104.136.29 X-SA-Exim-Rcpt-To: chenxiang66@hisilicon.com, ardb@kernel.org, will@kernel.org, mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, qemu-devel@nongnu.org, linuxarm@huawei.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Received-SPF: pass client-ip=2604:1380:4641:c500::1; envelope-from=maz@kernel.org; helo=dfw.source.kernel.org X-Spam_score_int: -70 X-Spam_score: -7.1 X-Spam_bar: ------- X-Spam_report: (-7.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On Wed, 30 Nov 2022 02:52:35 +0000, "chenxiang (M)" wrote: > > Hi, > > We boot the VM using following commands (with nvdimm on) (qemu > version 6.1.50, kernel 6.0-r4): How relevant is the presence of the nvdimm? Do you observe the failure without this? > > qemu-system-aarch64 -machine > virt,kernel_irqchip=on,gic-version=3,nvdimm=on -kernel > /home/kernel/Image -initrd /home/mini-rootfs/rootfs.cpio.gz -bios > /root/QEMU_EFI.FD -cpu host -enable-kvm -net none -nographic -m > 2G,maxmem=64G,slots=3 -smp 4 -append 'rdinit=init console=ttyAMA0 > ealycon=pl0ll,0x90000000 pcie_ports=native pciehp.pciehp_debug=1' > -object memory-backend-ram,id=ram1,size=10G -device > nvdimm,id=dimm1,memdev=ram1 -device ioh3420,id=root_port1,chassis=1 > -device vfio-pci,host=7d:01.0,id=net0,bus=root_port1 > > Then in VM we insmod a module, vmalloc error occurs as follows (kernel > 5.19-rc4 is normal, and the issue is still on kernel 6.1-rc4): > > estuary:/$ insmod /lib/modules/$(uname -r)/hnae3.ko > [ 8.186563] vmap allocation for size 20480 failed: use > vmalloc= to increase size Have you tried increasing the vmalloc size to check that this is indeed the problem? [...] > We git bisect the code, and find the patch c5a89f75d2a ("arm64: kaslr: > defer initialization to initcall where permitted"). I guess you mean commit fc5a89f75d2a instead, right? > Do you have any idea about the issue? I sort of suspect that the nvdimm gets vmap-ed and consumes a large portion of the vmalloc space, but you give very little information that could help here... M. -- Without deviation from the norm, progress is not possible.