From: SPDK [mailto:firstname.lastname@example.org] On Behalf Of Harris, James R
Sent: Thursday, April 27, 2017 10:53 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] invalid usermode virtual address 0xffff8f600000
> On Apr 27, 2017, at 12:04 AM, Oza Oza <oza.oza(a)broadcom.com> wrote:
> 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
In addition to what Jim mentioned, the vtophys.c address translation code (which is where
the "invalid usermode virtual address" message is coming from) assumes the Linux
x86-64 userspace memory layout; this means that all valid usermode addresses must be in
the low 47 bits of the address space, and they must be canonical (high bits are all the
same and must be 0 for userspace addresses).
If the memory layout on your platform is different, you will need to adapt vtophys for