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 AE35CEDE98C for ; Tue, 10 Sep 2024 01:24:59 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1snpcQ-0000AF-2O; Mon, 09 Sep 2024 21:24:34 -0400 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 1snpcL-00006x-Ax; Mon, 09 Sep 2024 21:24:29 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1snpcI-0007xT-8r; Mon, 09 Sep 2024 21:24:28 -0400 Received: from mail.maildlp.com (unknown [172.19.88.234]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4X2mF403LBz2DbxW; Tue, 10 Sep 2024 09:23:52 +0800 (CST) Received: from kwepemd200012.china.huawei.com (unknown [7.221.188.145]) by mail.maildlp.com (Postfix) with ESMTPS id 88BB91401F0; Tue, 10 Sep 2024 09:24:19 +0800 (CST) Received: from [10.67.121.115] (10.67.121.115) by kwepemd200012.china.huawei.com (7.221.188.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.34; Tue, 10 Sep 2024 09:24:18 +0800 Message-ID: Date: Tue, 10 Sep 2024 09:24:18 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [Bug Report] smmuv3 event 0x10 report when running virtio-blk-pci Content-Language: en-US To: Peter Maydell CC: , , Shameer Kolothum , Eric Auger , Mostafa Saleh References: <447984db-8c52-c911-d7bd-6616edaaefa5@hisilicon.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.121.115] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To kwepemd200012.china.huawei.com (7.221.188.145) Received-SPF: pass client-ip=45.249.212.190; envelope-from=wangzhou1@hisilicon.com; helo=szxga04-in.huawei.com X-Spam_score_int: -75 X-Spam_score: -7.6 X-Spam_bar: ------- X-Spam_report: (-7.6 / 5.0 requ) BAYES_00=-1.9, NICE_REPLY_A=-3.396, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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: , Reply-to: Zhou Wang From: Zhou Wang via Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On 2024/9/9 22:31, Peter Maydell wrote: > On Mon, 9 Sept 2024 at 15:22, Zhou Wang via wrote: >> >> Hi All, >> >> When I tested mainline qemu(commit 7b87a25f49), it reports smmuv3 event 0x10 >> during kernel booting up. > > Does it still do this if you either: > (1) use the v9.1.0 release (commit fd1952d814da) > (2) use "-machine virt-9.1" instead of "-machine virt" I tested above two cases, the problem is still there. > > ? > > My suspicion is that this will have started happening now that > we expose an SMMU with two-stage translation support to the guest > in the "virt" machine type (which we do not if you either > use virt-9.1 or in the v9.1.0 release). > > I've cc'd Eric (smmuv3 maintainer) and Mostafa (author of > the two-stage support). > >> qemu command which I use is as below: >> >> qemu-system-aarch64 -machine virt,kernel_irqchip=on,gic-version=3,iommu=smmuv3 \ >> -kernel Image -initrd minifs.cpio.gz \ >> -enable-kvm -net none -nographic -m 3G -smp 6 -cpu host \ >> -append 'rdinit=init console=ttyAMA0 ealycon=pl0ll,0x90000000 maxcpus=3' \ >> -device pcie-root-port,port=0x8,chassis=0,id=pci.0,bus=pcie.0,multifunction=on,addr=0x2 \ >> -device pcie-root-port,port=0x9,chassis=1,id=pci.1,bus=pcie.0,addr=0x2.0x1 \ >> -device virtio-blk-pci,drive=drive0,id=virtblk0,num-queues=8,packed=on,bus=pci.1 \ >> -drive file=/home/boot.img,if=none,id=drive0,format=raw >> >> smmuv3 event 0x10 log: >> [...] >> [ 1.962656] virtio-pci 0000:02:00.0: Adding to iommu group 0 >> [ 1.963150] virtio-pci 0000:02:00.0: enabling device (0000 -> 0002) >> [ 1.964707] virtio_blk virtio0: 6/0/0 default/read/poll queues >> [ 1.965759] virtio_blk virtio0: [vda] 2097152 512-byte logical blocks (1.07 GB/1.00 GiB) >> [ 1.966934] arm-smmu-v3 9050000.smmuv3: event 0x10 received: >> [ 1.967442] input: gpio-keys as /devices/platform/gpio-keys/input/input0 >> [ 1.967478] arm-smmu-v3 9050000.smmuv3: 0x0000020000000010 >> [ 1.968381] clk: Disabling unused clocks >> [ 1.968677] arm-smmu-v3 9050000.smmuv3: 0x0000020000000000 >> [ 1.968990] PM: genpd: Disabling unused power domains >> [ 1.969424] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000 >> [ 1.969814] ALSA device list: >> [ 1.970240] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000 >> [ 1.970471] No soundcards found. >> [ 1.970902] arm-smmu-v3 9050000.smmuv3: event 0x10 received: >> [ 1.971600] arm-smmu-v3 9050000.smmuv3: 0x0000020000000010 >> [ 1.971601] arm-smmu-v3 9050000.smmuv3: 0x0000020000000000 >> [ 1.971601] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000 >> [ 1.971602] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000 >> [ 1.971606] arm-smmu-v3 9050000.smmuv3: event 0x10 received: >> [ 1.971607] arm-smmu-v3 9050000.smmuv3: 0x0000020000000010 >> [ 1.974202] arm-smmu-v3 9050000.smmuv3: 0x0000020000000000 >> [ 1.974634] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000 >> [ 1.975005] Freeing unused kernel memory: 10112K >> [ 1.975062] arm-smmu-v3 9050000.smmuv3: 0x0000000000000000 >> [ 1.975442] Run init as init process >> >> Another information is that if "maxcpus=3" is removed from the kernel command line, >> it will be OK. >> >> I am not sure if there is a bug about vsmmu. It will be very appreciated if anyone >> know this issue or can take a look at it. > > thanks > -- PMM > .