DPDK patches and discussions
 help / color / mirror / Atom feed
From: sunyuechi@iscas.ac.cn
To: dev@dpdk.org
Cc: "Stanisław Kardach" <stanislaw.kardach@gmail.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>
Subject: Re: Re: [PATCH] config/riscv: add rv64gcv cross compilation target
Date: Mon, 27 Oct 2025 09:53:16 +0800 (GMT+08:00)	[thread overview]
Message-ID: <65e3478c.507d1.19a235ea501.Coremail.sunyuechi@iscas.ac.cn> (raw)
In-Reply-To: <224af7e6.115d8.199b98c0ff2.Coremail.sunyuechi@iscas.ac.cn>

Ping


&gt; -----原始邮件-----
&gt; 发件人: sunyuechi@iscas.ac.cn
&gt; 发送时间: 2025-10-06 20:43:08 (星期一)
&gt; 收件人: dev@dpdk.org
&gt; 抄送: "Stanisław Kardach" <stanislaw.kardach@gmail.com>, "Bruce Richardson" <bruce.richardson@intel.com>
&gt; 主题: Re: [PATCH] config/riscv: add rv64gcv cross compilation target
&gt; 
&gt; Hi, how is this patch?
&gt; 
&gt; 
&gt; &gt; -----原始邮件-----
&gt; &gt; 发件人: sunyuechi@iscas.ac.cn
&gt; &gt; 发送时间: 2025-09-23 23:07:34 (星期二)
&gt; &gt; 收件人: dev@dpdk.org
&gt; &gt; 抄送: "Sun Yuechi" <sunyuechi@iscas.ac.cn>, "Stanisław Kardach" <stanislaw.kardach@gmail.com>, "Bruce Richardson" <bruce.richardson@intel.com>
&gt; &gt; 主题: [PATCH] config/riscv: add rv64gcv cross compilation target
&gt; &gt; 
&gt; &gt; From: Sun Yuechi <sunyuechi@iscas.ac.cn>
&gt; &gt; 
&gt; &gt; Add a cross file for rv64gcv, enable it in devtools/test-meson-builds.sh,
&gt; &gt; and update the RISC-V cross-build guide to support the vector extension.
&gt; &gt; 
&gt; &gt; Signed-off-by: Sun Yuechi <sunyuechi@iscas.ac.cn>
&gt; &gt; ---
&gt; &gt;  config/riscv/meson.build                        |  3 ++-
&gt; &gt;  config/riscv/riscv64_rv64gcv_linux_gcc          | 17 +++++++++++++++++
&gt; &gt;  devtools/test-meson-builds.sh                   |  4 ++++
&gt; &gt;  .../linux_gsg/cross_build_dpdk_for_riscv.rst    |  2 ++
&gt; &gt;  4 files changed, 25 insertions(+), 1 deletion(-)
&gt; &gt;  create mode 100644 config/riscv/riscv64_rv64gcv_linux_gcc
&gt; &gt; 
&gt; &gt; diff --git a/config/riscv/meson.build b/config/riscv/meson.build
&gt; &gt; index f3daea0c0e..a06429a1e2 100644
&gt; &gt; --- a/config/riscv/meson.build
&gt; &gt; +++ b/config/riscv/meson.build
&gt; &gt; @@ -43,7 +43,8 @@ vendor_generic = {
&gt; &gt;          ['RTE_MAX_NUMA_NODES', 2]
&gt; &gt;      ],
&gt; &gt;      'arch_config': {
&gt; &gt; -        'generic': {'machine_args': ['-march=rv64gc']}
&gt; &gt; +        'generic': {'machine_args': ['-march=rv64gc']},
&gt; &gt; +        'rv64gcv': {'machine_args': ['-march=rv64gcv']},
&gt; &gt;      }
&gt; &gt;  }
&gt; &gt;  
&gt; &gt; diff --git a/config/riscv/riscv64_rv64gcv_linux_gcc b/config/riscv/riscv64_rv64gcv_linux_gcc
&gt; &gt; new file mode 100644
&gt; &gt; index 0000000000..ccc5115dec
&gt; &gt; --- /dev/null
&gt; &gt; +++ b/config/riscv/riscv64_rv64gcv_linux_gcc
&gt; &gt; @@ -0,0 +1,17 @@
&gt; &gt; +[binaries]
&gt; &gt; +c = ['ccache', 'riscv64-linux-gnu-gcc']
&gt; &gt; +cpp = ['ccache', 'riscv64-linux-gnu-g++']
&gt; &gt; +ar = 'riscv64-linux-gnu-ar'
&gt; &gt; +strip = 'riscv64-linux-gnu-strip'
&gt; &gt; +pcap-config = ''
&gt; &gt; +
&gt; &gt; +[host_machine]
&gt; &gt; +system = 'linux'
&gt; &gt; +cpu_family = 'riscv64'
&gt; &gt; +cpu = 'rv64gcv'
&gt; &gt; +endian = 'little'
&gt; &gt; +
&gt; &gt; +[properties]
&gt; &gt; +vendor_id = 'generic'
&gt; &gt; +arch_id = 'rv64gcv'
&gt; &gt; +pkg_config_libdir = '/usr/lib/riscv64-linux-gnu/pkgconfig'
&gt; &gt; diff --git a/devtools/test-meson-builds.sh b/devtools/test-meson-builds.sh
&gt; &gt; index 4fff1f7177..4f07f84eb0 100755
&gt; &gt; --- a/devtools/test-meson-builds.sh
&gt; &gt; +++ b/devtools/test-meson-builds.sh
&gt; &gt; @@ -290,6 +290,10 @@ build build-ppc64-power8-gcc $f ABI $use_shared
&gt; &gt;  f=$srcdir/config/riscv/riscv64_linux_gcc
&gt; &gt;  build build-riscv64-generic-gcc $f ABI $use_shared
&gt; &gt;  
&gt; &gt; +# RISC-V vector (rv64gcv)
&gt; &gt; +f=$srcdir/config/riscv/riscv64_rv64gcv_linux_gcc
&gt; &gt; +build build-riscv64_rv64gcv_gcc $f ABI $use_shared
&gt; &gt; +
&gt; &gt;  # Test installation of the x86-generic target, to be used for checking
&gt; &gt;  # the sample apps build using the pkg-config file for cflags and libs
&gt; &gt;  load_env cc
&gt; &gt; diff --git a/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst b/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst
&gt; &gt; index 7d7f7ac72b..bcba12a604 100644
&gt; &gt; --- a/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst
&gt; &gt; +++ b/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst
&gt; &gt; @@ -108,6 +108,8 @@ Currently the following targets are supported:
&gt; &gt;  
&gt; &gt;  * Generic rv64gc ISA: ``config/riscv/riscv64_linux_gcc``
&gt; &gt;  
&gt; &gt; +* RV64GCV ISA: ``config/riscv/riscv64_rv64gcv_linux_gcc``
&gt; &gt; +
&gt; &gt;  * SiFive U740 SoC: ``config/riscv/riscv64_sifive_u740_linux_gcc``
&gt; &gt;  
&gt; &gt;  To add a new target support, ``config/riscv/meson.build`` has to be modified by
&gt; &gt; -- 
&gt; &gt; 2.51.0
&gt; </sunyuechi@iscas.ac.cn></sunyuechi@iscas.ac.cn></bruce.richardson@intel.com></stanislaw.kardach@gmail.com></sunyuechi@iscas.ac.cn>
</bruce.richardson@intel.com></stanislaw.kardach@gmail.com>

      reply	other threads:[~2025-10-27  1:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 15:07 sunyuechi
2025-10-06 12:43 ` sunyuechi
2025-10-27  1:53   ` sunyuechi [this message]

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=65e3478c.507d1.19a235ea501.Coremail.sunyuechi@iscas.ac.cn \
    --to=sunyuechi@iscas.ac.cn \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stanislaw.kardach@gmail.com \
    /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).