From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1383884053412065087==" MIME-Version: 1.0 From: archiemorningstar88 at gmail.com Subject: [SPDK] Re: Using cmb_copy in QEMU environment Date: Mon, 20 Apr 2020 18:07:46 +0000 Message-ID: <20200420180746.2799.35202@ml01.vlan13.01.org> In-Reply-To: BN7PR11MB2739C8123B31D700D50220C8EED40@BN7PR11MB2739.namprd11.prod.outlook.com List-ID: To: spdk@lists.01.org --===============1383884053412065087== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Issue created: https://github.com/spdk/spdk/issues/1359 Archie > Hi Archie, > = > Thanks for reporting, could you submit a github issue? Thanks. > = > I used the latest SPDK code with the submission queue in the CMB, it also= got failure with > CMB, I will take a look for the issue. > = > = > > -----Original Message----- > > From: archiemorningstar88(a)gmail.com > Sent: Sunday, April 19, 2020 4:58 AM > > To: spdk(a)lists.01.org > > Subject: [SPDK] Using cmb_copy in QEMU environment > > = > > Hi, > > = > > I've been trying to get cmb_copy (examples/nvme/cmb_copy) to work using= an > > emulated SSD with CMB in a QEMU environment, but cmb_copy cannot alloca= te > > a CMB buffer. The identify (examples/nvme/identify) reports the two emu= lated > > SSD's I created have 128MB of CMB. I'm running QEMU v4.2.0 with the gue= st OS > > Ubuntu 18.04. I've also tried various revisions of SPDK (20.01.1, 19.10= .1, > 19.04.1, > > 18.04.1) with similar results. > > = > > I see these two errors print out which I believe couldn't register the = memory so > > the call to spdk_nvme_ctrlr_alloc_cmb_io_buffer() fails (pctrlr- > > >cmb_bar_virt_addr is NULL): > > could not get phys addr for 0x1088200000 > > nvme_pcie.c: 554:nvme_pcie_ctrlr_map_cmb: *ERROR*: spdk_mem_register() > > failed > > = > > I tried to trace the code and see that when it searches for the physica= l address > > g_vtophys_pci_devices list is empty when trying to register the CMB mem= ory > > space. It only gets later populated with the two SSDs when cleanup_pci_= devices() > > is called at the end of spdk_pci_device_attach(). > > = > > My qemu startup: > > x86_64-softmmu/qemu-system-x86_64 \ > > -cpu host \ > > -machine q35,accel=3Dkvm,kernel-irqchip=3Dsplit \ > > -smp 8 \ > > -m 32768 \ > > -enable-kvm \ > > -drive if=3Dvirtio,file=3Dtest1.qcow2,cache=3Dnone \ > > -vnc :1 \ > > -device e1000,netdev=3Dnet0 \ > > -netdev user,id=3Dnet0,hostfwd=3Dtcp::5555-:22 \ > > -drive file=3Dnvme0.img,if=3Dnone,id=3DD22,format=3Draw \ > > -device nvme,drive=3DD22,serial=3D1234,cmb_size_mb=3D128 \ > > -drive file=3Dnvme1.img,if=3Dnone,id=3DD23,format=3Draw \ > > -device nvme,drive=3DD23,serial=3D5678,cmb_size_mb=3D128 \ > > -device intel-iommu,intremap=3Don \ > > = > > If anyone has any suggestions it would be greatly appreciated. > > = > > Archie > > _______________________________________________ > > SPDK mailing list -- spdk(a)lists.01.org > > To unsubscribe send an email to spdk-leave(a)lists.01.org --===============1383884053412065087==--