[dpdk-users] Segmentation fault at rte_cpu_get_flag_enabled

[vikram T]

Hi Stephen,
Thanks for the response.
As far as I know the value given to CONFIG_RTE_MACHINE may be any of these:
( supported in DPDK)

armv7a  default  dpaa2  ivb     nhm        power8      snb       thunderx2
 xgene1
armv8a  dpaa     hsw    native  octeontx2  silvermont  thunderx  wsm

How do I find/determine the minimum CPU type from the above supported
machines?
Additionally our product runs on multiple machines and hence would like to
select the most minimum CPU set to avoid this issue.
Regards
Vikram

On Mon, Apr 20, 2020 at 8:37 PM Stephen Hemminger <
stephen at networkplumber.org> wrote:

> On Mon, 20 Apr 2020 12:39:02 +0530
> vikram T <vikramet at gmail.com> wrote:
>
> > Hi,
> > I have been seeing the application crashes( DPDK v19.08) with
> segmentation
> > fault as below:
> > (gdb) bt
> > #0  0x000000000054fda9 in rte_cpu_get_flag_enabled ()
> > #1  0x00000000004f5d5e in rte_hash_crc_init_alg ()
> > #2  0x000000000084cf7d in __libc_csu_init ()
> > #3  0x00007ffff4df9425 in __libc_start_main () from /lib64/libc.so.6
> > #4  0x00000000005048df in _start ()
> > (gdb) q
> >
> > Here the DPDK is built and linked on the machine different from the
> target
> > machine.
> > Hence used the flag - "CONFIG_RTE_MACHINE = default"  but no success.
> >
> > Is there anything that needs to be followed to overcome this blocking
> issue?
> >
> > Regards
> > Vikram
>
> You need to to set CONFIG_RTE_MACHINE to the minimum cpu type that your
> product needs to run on. That value sets the compiler flags which determine
> which extended CPU instructions will be used.
>