Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Oza Oza <oza.oza at broadcom.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] invalid usermode virtual address 0xffff8f600000
Date: Mon, 08 May 2017 19:49:30 +0530	[thread overview]
Message-ID: <e2c7466a533b7f67462f551611782dd2@mail.gmail.com> (raw)
In-Reply-To: 7E9FE09D-D334-43C0-9834-F62D7D51C08F@intel.com

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

Yes. armv8 has 48 bit physical address and give 256 TB of memory map to user
space. so with that it is fine now.

Once our development/porting is done, we will consider up-streaming the
patches, though it might take little time.
Sorry about that.

Regards,
Oza.
-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Harris, James R
Sent: Thursday, April 27, 2017 11:23 PM
To: Storage Performance Development Kit
Subject: Re: [SPDK] invalid usermode virtual address 0xffff8f600000

Hi Oza,

> 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 architecture.

>
> commit effea17dadbc28d201a4ec793e1d7c169e2faac6
> 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
>     else).
>
>     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
>     execution).
>
>     Change-Id: I855763d7d827fb8cf00a775c7bc2ccb579db8d0f
>     Signed-off-by: Daniel Verkamp <daniel.verkamp(a)intel.com>
>
> From: Oza Oza [mailto:oza.oza(a)broadcom.com]
> Sent: Thursday, April 27, 2017 12:03 PM
> To: 'Storage Performance Development Kit'
> Subject: invalid usermode virtual address 0xffff8f600000
>
> Hi,
>
> 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.
>
> Regards,
> Oza.
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

             reply	other threads:[~2017-05-08 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 14:19 Oza Oza [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-27 19:41 [SPDK] invalid usermode virtual address 0xffff8f600000 Verkamp, Daniel
2017-04-27 17:52 Harris, James R
2017-04-27  7:04 Oza Oza
2017-04-27  6:33 Oza Oza

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=e2c7466a533b7f67462f551611782dd2@mail.gmail.com \
    --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