From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============0196941463367001335==" MIME-Version: 1.0 From: archiemorningstar88 at gmail.com Subject: [SPDK] Re: Using cmb_copy in QEMU environment Date: Mon, 20 Apr 2020 18:24:56 +0000 Message-ID: <20200420182456.2799.31946@ml01.vlan13.01.org> In-Reply-To: 25A54994-6A58-4491-88EA-205F5899D98A@intel.com List-ID: To: spdk@lists.01.org --===============0196941463367001335== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Jim, I see similar error with 3429f97. Archie > On 4/20/20, 8:38 AM, "Stephen Bates" = > Hi All > = > = > Can you point me to the issue when created. I added the cmb_copy exam= ple a while back > and it was working in QEMU at that time. I suspect this is a memory alloc= ation regression > and would like to track the issue. Note the Linux kernel equivalent (p2p= dma) *does* still > work inside QEMUwith fake NVMe SSDs. So this seems to be an SPDK specific= thing... > = > Hi Archie and Changpeng, > = > Could you also try commit 3429f97? This commit is just before some CMB-r= elated patches > that were recently merged. > = > -Jim > = > = > Cheers > = > Stephen = > = > = > = > = > _______________________________________________ > SPDK mailing list -- spdk(a)lists.01.org > To unsubscribe send an email to spdk-leave(a)lists.01.org --===============0196941463367001335==--