From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1501] rte_cpu_get_flag_enabled() segmentation fault
Date: Fri, 26 Jul 2024 07:24:51 +0000 [thread overview]
Message-ID: <bug-1501-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1501
Bug ID: 1501
Summary: rte_cpu_get_flag_enabled() segmentation fault
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: seyhmus.kartal@karel.com.tr
Target Milestone: ---
I create a rte_fib struct for routing purposes and I free it and recreate it
periodically to update the routes. rte_fib_create() uses
rte_cpu_get_flag_enabled() to check if my cpu has AVX512F or not and selects
lookup function according to it. My cpu does not have AVX512F so
rte_cpu_get_flag_enabled() returns 0 as expected and rte_fib_create() selects
scalar lookup function. However, after a point rte_cpu_get_flag_enabled()
causes a segmentation fault with SIGILL although it runs without any problem
until that moment.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2950 bytes --]
reply other threads:[~2024-07-26 7:24 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=bug-1501-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.