DPDK usage discussions
 help / color / mirror / Atom feed
From: 孙向鹏 <sunxiangpeng@kuaishou.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Failed to load t3.o ebpf example
Date: Thu, 4 Feb 2021 04:19:27 +0000	[thread overview]
Message-ID: <92346103-8041-4EEF-B79F-178197BBFFCC@kuaishou.com> (raw)

Hi DPDK Experts,

I try to run ebpf example provided by dpdk source. However, it seems like dpdk cannot validate the t3.o and gives me the following error

testpmd> bpf-load rx 0 0 JM t3.o
validate: invalid src-reg field at pc: 10
rte_bpf_elf_load(fname="t3.o", sname=".text") failed, error code: 22
-22:Invalid argument

Seems like the call pc 10 is invalid to the validate code. My testbed is based on dpdk-stable-18.11.2 / clang version 7.0.1 (tags/RELEASE_701/final)  / Linux localhost.localdomain 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux.

Yours,
Xiangpeng Sun

                 reply	other threads:[~2021-02-07  9:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=92346103-8041-4EEF-B79F-178197BBFFCC@kuaishou.com \
    --to=sunxiangpeng@kuaishou.com \
    --cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).