On Apr 27, 2017, at 12:04 AM, Oza Oza <oza.oza(a)broadcom.com>
Latest SPDK stopped working on armv8 port for us.
I would suggest working to upstream your armv8 patches. Without understanding the changes
made to enable SPDK on armv8, it is difficult for the community to keep from breaking a
set of out-of-tree patches.
More details around “stopped working” would also help understanding the issues. For
example, are you testing NVMe PCI devices, NVMe-oF, etc.
When I checked in back to this commit it starts working.
Could you double check your git bisect? I do not see how this commit (or the one before
or after it) could affect anything related to a difference in CPU architecture.
Author: Daniel Verkamp <daniel.verkamp(a)intel.com>
Date: Wed Feb 22 15:06:31 2017 -0700
nvmf: make invalid rdma_req case into an assert
The wr_id should never be NULL - it will always correspond to a request
we previously posted. Convert the check to an assert() so we notice if
this ever happens (which would indicate a programming error somewhere
While we're here, add a more robust check to make sure the request is
actually in the correct array of requests for the connection being
polled (also in an assert, since this should never fail in normal
Signed-off-by: Daniel Verkamp <daniel.verkamp(a)intel.com>
From: Oza Oza [mailto:firstname.lastname@example.org]
Sent: Thursday, April 27, 2017 12:03 PM
To: 'Storage Performance Development Kit'
Subject: invalid usermode virtual address 0xffff8f600000
Why do I get invalid user mode virtual address when I enabled DEBUG in SPDK/DPDK ?
invalid usermode virtual address 0xffff8f600000
invalid usermode virtual address 0xffff0f800000
invalid usermode virtual address 0xffff0f400000
vtophys.c fails any translation operation on a virtual address > (1ULL << 47).
Looks like on armv8 the limit should be at least (1ULL << 48).
this is armv8.
SPDK mailing list