Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: archiemorningstar88 at gmail.com
To: spdk@lists.01.org
Subject: [SPDK] Re: Using cmb_copy in QEMU environment
Date: Mon, 20 Apr 2020 18:07:46 +0000	[thread overview]
Message-ID: <20200420180746.2799.35202@ml01.vlan13.01.org> (raw)
In-Reply-To: BN7PR11MB2739C8123B31D700D50220C8EED40@BN7PR11MB2739.namprd11.prod.outlook.com

[-- Attachment #1: Type: text/plain, Size: 2509 bytes --]

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 <archiemorningstar88(a)gmail.com&gt;
> > 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 allocate
> > a CMB buffer. The identify (examples/nvme/identify) reports the two emulated
> > SSD's I created have 128MB of CMB. I'm running QEMU v4.2.0 with the guest 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 physical address
> > g_vtophys_pci_devices list is empty when trying to register the CMB memory
> > 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=kvm,kernel-irqchip=split \
> > -smp 8 \
> > -m 32768 \
> > -enable-kvm \
> > -drive if=virtio,file=test1.qcow2,cache=none \
> > -vnc :1 \
> > -device e1000,netdev=net0 \
> > -netdev user,id=net0,hostfwd=tcp::5555-:22 \
> > -drive file=nvme0.img,if=none,id=D22,format=raw \
> > -device nvme,drive=D22,serial=1234,cmb_size_mb=128 \
> > -drive file=nvme1.img,if=none,id=D23,format=raw \
> > -device nvme,drive=D23,serial=5678,cmb_size_mb=128 \
> > -device intel-iommu,intremap=on \
> > 
> > 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

             reply	other threads:[~2020-04-20 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 18:07 archiemorningstar88 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-20 18:24 [SPDK] Re: Using cmb_copy in QEMU environment archiemorningstar88
2020-04-20 15:46 Harris, James R
2020-04-20 15:35 Stephen Bates
2020-04-20  5:38 Liu, Changpeng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200420180746.2799.35202@ml01.vlan13.01.org \
    --to=spdk@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox