Re: [SPDK] Compiling error on different types of Intel CPU

Re: [SPDK] Compiling error on different types of Intel CPU

[Kulasek, TomaszX]

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

Hi,

I suppose you have gcc < 4.9 installed with no -march=ivybridge supported. DPDK recommends gcc 4.9 or higher, so you can upgrade it or try for older gcc versions:

-march=core-avx-i

for both SPDK as well as DPDK.

Tomek

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Bob Chen
Sent: Tuesday, May 22, 2018 09:09
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Compiling error on different types of Intel CPU



2018-05-21 23:25 GMT+08:00 Harris, James R <james.r.harris(a)intel.com<mailto:james.r.harris(a)intel.com>>:
Hi Bob,

DPDK builds by default with –march=native.  This means when the app is compiled on the E5v4 (Broadwell Xeon) it may use instructions available on the E5v4 which are not available on the E5v2 (Ivy Bridge Xeon).

Looks like I will have to withdraw my assumption. Neither of these methods could work.

1. make DPDK_CFLAGS=-march=ivybridge install T=x86_64-native-linuxapp-gcc
Compilation passed, but still got the same error on E5v2. Probably this added flag was not effectively working.

2. change CONFIG_RTE_MACHINE to “ivybridge”
Compilation failed,

== Build lib/librte_eal/linuxapp
cc1: error: bad value (ivybridge) for -march= switch
== Build lib/librte_eal/linuxapp/eal
== Build lib/librte_eal/linuxapp/igb_uio
cc1: error: bad value (ivybridge) for -march= switch



Could you try “make clean” followed by “make DPDK_CFLAGS=-march=ivybridge”?

Alternatively, you can modify dpdk/config/defconfig_spdk-linuxapp-gcc – change CONFIG_RTE_MACHINE to “ivybridge”.  Then “make clean” and rebuild.

-Jim


From: SPDK <spdk-bounces(a)lists.01.org<mailto:spdk-bounces(a)lists.01.org>> on behalf of Nathan Marushak <nathan.marushak(a)intel.com<mailto:nathan.marushak(a)intel.com>>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>>
Date: Monday, May 21, 2018 at 6:31 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>>
Subject: Re: [SPDK] Compiling error on different types of Intel CPU

I know Jim will answer this better. We had a similar discussion someplace else. I want to say that this has something to do with how you constructed your VM. I think it was the VM was built with some incorrect expectations for CPU emulation.

Jim?
Thanks,
Nate

On May 21, 2018, at 5:21 AM, Luse, Paul E <paul.e.luse(a)intel.com<mailto:paul.e.luse(a)intel.com>> wrote:
Hi,

I’m not the vhost expert but invalid CPU opcode seems unlikely.  If you can send some more information, like log outputs, backtrace from gdb or something that would be helpful.  This is likely an opcode used somewhere along the way and has to do with a vhost or scsi opcode or something.

Thx
Paul

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Bob Chen
Sent: Monday, May 21, 2018 1:12 AM
To: spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>
Subject: [SPDK] Compiling error on different types of Intel CPU

Hi,

I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz.

The app would immediately crash, with below kernel message:

traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0 error:0 in spdk_vhost[400000+a7000]

Incompatible CPU instruction set, I guess?


-Bob
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
https://lists.01.org/mailman/listinfo/spdk

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


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 56483 bytes --]

Re: [SPDK] Compiling error on different types of Intel CPU

[E.W.Z.]

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

Agree, it is not possible as it is written now.
Opened an issue, see here https://github.com/spdk/spdk/issues/711


Sent from Mail for Windows 10

From: Harris, James R
Sent: Monday, March 11, 2019 17:23
To: Storage Performance Development Kit
Subject: Re: [SPDK] Compiling error on different types of Intel CPU


On 3/11/19, 5:49 AM, "SPDK on behalf of Ernest Zed" <spdk-bounces(a)lists.01.org on behalf of kreuzerkrieg(a)gmail.com> wrote:

    Hi,
    In continuation to this issue from May 2018, I dont see anything changed in
    make file, SPDK is being built with the same `-march=native` which hit us
    hard two days ago when we upgraded our build machine to the latest Xeon
    which supports AVX512. Our test machines does not have this extension so
    binaries built on newer machine wont run on older ones. Meanwhile I gonna
    change the `-march=native` to something like `-march=core-avx-i`. But is it
    possible to change the `configure` script to pass additional compilation
    flags to the `make`?

Hi Ernest,

I don't think it's possible today.  There's a way to pass CFLAGS to configure, but if I'm reading the Makefile correctly, any arch definition you put there would get overridden by the march=native.  The DPDK and ISA-L submodules would also need plumbing to pass through the arch setting.  I think we'll want to create a separate variable specific for arch, rather than try to 'fix' the CFLAGS handling in the configure script.

This is a pretty reasonable request though - could you file an issue in the SPDK GitHub tracker for this?  Please also add in the issue if this is something you'd be interested in working on.

Thanks,

-Jim
    _______________________________________________
    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

Re: [SPDK] Compiling error on different types of Intel CPU

[Harris, James R]

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


On 3/11/19, 5:49 AM, "SPDK on behalf of Ernest Zed" <spdk-bounces(a)lists.01.org on behalf of kreuzerkrieg(a)gmail.com> wrote:

    Hi,
    In continuation to this issue from May 2018, I dont see anything changed in
    make file, SPDK is being built with the same `-march=native` which hit us
    hard two days ago when we upgraded our build machine to the latest Xeon
    which supports AVX512. Our test machines does not have this extension so
    binaries built on newer machine wont run on older ones. Meanwhile I gonna
    change the `-march=native` to something like `-march=core-avx-i`. But is it
    possible to change the `configure` script to pass additional compilation
    flags to the `make`?

Hi Ernest,

I don't think it's possible today.  There's a way to pass CFLAGS to configure, but if I'm reading the Makefile correctly, any arch definition you put there would get overridden by the march=native.  The DPDK and ISA-L submodules would also need plumbing to pass through the arch setting.  I think we'll want to create a separate variable specific for arch, rather than try to 'fix' the CFLAGS handling in the configure script.

This is a pretty reasonable request though - could you file an issue in the SPDK GitHub tracker for this?  Please also add in the issue if this is something you'd be interested in working on.

Thanks,

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

[SPDK] Compiling error on different types of Intel CPU

[Ernest Zed]

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

Hi,
In continuation to this issue from May 2018, I dont see anything changed in
make file, SPDK is being built with the same `-march=native` which hit us
hard two days ago when we upgraded our build machine to the latest Xeon
which supports AVX512. Our test machines does not have this extension so
binaries built on newer machine wont run on older ones. Meanwhile I gonna
change the `-march=native` to something like `-march=core-avx-i`. But is it
possible to change the `configure` script to pass additional compilation
flags to the `make`?

Re: [SPDK] Compiling error on different types of Intel CPU

[Bob Chen]

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

2018-05-21 23:25 GMT+08:00 Harris, James R <james.r.harris(a)intel.com>:

> Hi Bob,
>
>
>
> DPDK builds by default with –march=native.  This means when the app is
> compiled on the E5v4 (Broadwell Xeon) it may use instructions available on
> the E5v4 which are not available on the E5v2 (Ivy Bridge Xeon).
>

Looks like I will have to withdraw my assumption. Neither of these methods
could work.

1. make DPDK_CFLAGS=-march=ivybridge install T=x86_64-native-linuxapp-gcc
Compilation passed, but still got the same error on E5v2. Probably this
added flag was not effectively working.

2. change CONFIG_RTE_MACHINE to “ivybridge”
Compilation failed,

== Build lib/librte_eal/linuxapp
cc1: error: bad value (ivybridge) for -march= switch
== Build lib/librte_eal/linuxapp/eal
== Build lib/librte_eal/linuxapp/igb_uio
cc1: error: bad value (ivybridge) for -march= switch



>
>
> Could you try “make clean” followed by “make DPDK_CFLAGS=-march=ivybridge”?
>
>
>
> Alternatively, you can modify dpdk/config/defconfig_spdk-linuxapp-gcc –
> change CONFIG_RTE_MACHINE to “ivybridge”.  Then “make clean” and rebuild.
>
>
>
> -Jim
>
>
>
>
>
> *From: *SPDK <spdk-bounces(a)lists.01.org> on behalf of Nathan Marushak <
> nathan.marushak(a)intel.com>
> *Reply-To: *Storage Performance Development Kit <spdk(a)lists.01.org>
> *Date: *Monday, May 21, 2018 at 6:31 AM
> *To: *Storage Performance Development Kit <spdk(a)lists.01.org>
> *Subject: *Re: [SPDK] Compiling error on different types of Intel CPU
>
>
>
> I know Jim will answer this better. We had a similar discussion someplace
> else. I want to say that this has something to do with how you constructed
> your VM. I think it was the VM was built with some incorrect expectations
> for CPU emulation.
>
>
>
> Jim?
>
> Thanks,
>
> Nate
>
>
> On May 21, 2018, at 5:21 AM, Luse, Paul E <paul.e.luse(a)intel.com> wrote:
>
> Hi,
>
>
>
> I’m not the vhost expert but invalid CPU opcode seems unlikely.  If you
> can send some more information, like log outputs, backtrace from gdb or
> something that would be helpful.  This is likely an opcode used somewhere
> along the way and has to do with a vhost or scsi opcode or something.
>
>
>
> Thx
> Paul
>
>
>
> *From:* SPDK [mailto:spdk-bounces(a)lists.01.org <spdk-bounces(a)lists.01.org>]
> *On Behalf Of *Bob Chen
> *Sent:* Monday, May 21, 2018 1:12 AM
> *To:* spdk(a)lists.01.org
> *Subject:* [SPDK] Compiling error on different types of Intel CPU
>
>
>
> Hi,
>
>
>
> I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @
> 2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU
> E5-2650 v2 @ 2.60GHz.
>
>
>
> The app would immediately crash, with below kernel message:
>
>
>
> traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0
> error:0 in spdk_vhost[400000+a7000]
>
>
>
> Incompatible CPU instruction set, I guess?
>
>
>
>
>
> -Bob
>
> _______________________________________________
> 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
>
>

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 10295 bytes --]

Re: [SPDK] Compiling error on different types of Intel CPU

[Harris, James R]

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



From: SPDK <spdk-bounces(a)lists.01.org> on behalf of Bob Chen <a175818323(a)gmail.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Monday, May 21, 2018 at 8:23 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Compiling error on different types of Intel CPU



2018-05-21 23:25 GMT+08:00 Harris, James R <james.r.harris(a)intel.com<mailto:james.r.harris(a)intel.com>>:
Hi Bob,

DPDK builds by default with –march=native.  This means when the app is compiled on the E5v4 (Broadwell Xeon) it may use instructions available on the E5v4 which are not available on the E5v2 (Ivy Bridge Xeon).

Could you try “make clean” followed by “make DPDK_CFLAGS=-march=ivybridge”?

Alternatively, you can modify dpdk/config/defconfig_spdk-linuxapp-gcc – change CONFIG_RTE_MACHINE to “ivybridge”.  Then “make clean” and rebuild.

I assume it could work, but I still need to prepare two packages for each type of servers.

Is there any possibility that I could build a compatible software and let it run on both of them?

And who knows what would happen when things come to the next Skylake platform...

The “ivybridge” packages would work on both the E5v2 (Ivy Bridge) and E5v4 (Haswell) systems, as well as Skylake and future microarchitectures.


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5845 bytes --]

Re: [SPDK] Compiling error on different types of Intel CPU

[Bob Chen]

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

2018-05-21 23:25 GMT+08:00 Harris, James R <james.r.harris(a)intel.com>:

> Hi Bob,
>
>
>
> DPDK builds by default with –march=native.  This means when the app is
> compiled on the E5v4 (Broadwell Xeon) it may use instructions available on
> the E5v4 which are not available on the E5v2 (Ivy Bridge Xeon).
>
>
>
> Could you try “make clean” followed by “make DPDK_CFLAGS=-march=ivybridge”?
>
>
>
> Alternatively, you can modify dpdk/config/defconfig_spdk-linuxapp-gcc –
> change CONFIG_RTE_MACHINE to “ivybridge”.  Then “make clean” and rebuild.
>

I assume it could work, but I still need to prepare two packages for each
type of servers.

Is there any possibility that I could build a compatible software and let
it run on both of them?

And who knows what would happen when things come to the next Skylake
platform...


>
>
> -Jim
>
>
>
>
>
> *From: *SPDK <spdk-bounces(a)lists.01.org> on behalf of Nathan Marushak <
> nathan.marushak(a)intel.com>
> *Reply-To: *Storage Performance Development Kit <spdk(a)lists.01.org>
> *Date: *Monday, May 21, 2018 at 6:31 AM
> *To: *Storage Performance Development Kit <spdk(a)lists.01.org>
> *Subject: *Re: [SPDK] Compiling error on different types of Intel CPU
>
>
>
> I know Jim will answer this better. We had a similar discussion someplace
> else. I want to say that this has something to do with how you constructed
> your VM. I think it was the VM was built with some incorrect expectations
> for CPU emulation.
>
>
>
> Jim?
>
> Thanks,
>
> Nate
>
>
> On May 21, 2018, at 5:21 AM, Luse, Paul E <paul.e.luse(a)intel.com> wrote:
>
> Hi,
>
>
>
> I’m not the vhost expert but invalid CPU opcode seems unlikely.  If you
> can send some more information, like log outputs, backtrace from gdb or
> something that would be helpful.  This is likely an opcode used somewhere
> along the way and has to do with a vhost or scsi opcode or something.
>
>
>
> Thx
> Paul
>
>
>
> *From:* SPDK [mailto:spdk-bounces(a)lists.01.org <spdk-bounces(a)lists.01.org>]
> *On Behalf Of *Bob Chen
> *Sent:* Monday, May 21, 2018 1:12 AM
> *To:* spdk(a)lists.01.org
> *Subject:* [SPDK] Compiling error on different types of Intel CPU
>
>
>
> Hi,
>
>
>
> I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @
> 2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU
> E5-2650 v2 @ 2.60GHz.
>
>
>
> The app would immediately crash, with below kernel message:
>
>
>
> traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0
> error:0 in spdk_vhost[400000+a7000]
>
>
>
> Incompatible CPU instruction set, I guess?
>
>
>
>
>
> -Bob
>
> _______________________________________________
> 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
>
>

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 8830 bytes --]

Re: [SPDK] Compiling error on different types of Intel CPU

[Harris, James R]

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

Hi Bob,

DPDK builds by default with –march=native.  This means when the app is compiled on the E5v4 (Broadwell Xeon) it may use instructions available on the E5v4 which are not available on the E5v2 (Ivy Bridge Xeon).

Could you try “make clean” followed by “make DPDK_CFLAGS=-march=ivybridge”?

Alternatively, you can modify dpdk/config/defconfig_spdk-linuxapp-gcc – change CONFIG_RTE_MACHINE to “ivybridge”.  Then “make clean” and rebuild.

-Jim


From: SPDK <spdk-bounces(a)lists.01.org> on behalf of Nathan Marushak <nathan.marushak(a)intel.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Monday, May 21, 2018 at 6:31 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Compiling error on different types of Intel CPU

I know Jim will answer this better. We had a similar discussion someplace else. I want to say that this has something to do with how you constructed your VM. I think it was the VM was built with some incorrect expectations for CPU emulation.

Jim?
Thanks,
Nate

On May 21, 2018, at 5:21 AM, Luse, Paul E <paul.e.luse(a)intel.com<mailto:paul.e.luse(a)intel.com>> wrote:
Hi,

I’m not the vhost expert but invalid CPU opcode seems unlikely.  If you can send some more information, like log outputs, backtrace from gdb or something that would be helpful.  This is likely an opcode used somewhere along the way and has to do with a vhost or scsi opcode or something.

Thx
Paul

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Bob Chen
Sent: Monday, May 21, 2018 1:12 AM
To: spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>
Subject: [SPDK] Compiling error on different types of Intel CPU

Hi,

I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz.

The app would immediately crash, with below kernel message:

traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0 error:0 in spdk_vhost[400000+a7000]

Incompatible CPU instruction set, I guess?


-Bob
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
https://lists.01.org/mailman/listinfo/spdk

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 8771 bytes --]

Re: [SPDK] Compiling error on different types of Intel CPU

[Verkamp, Daniel]

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

The default DPDK and SPDK compiler options include -march=native, which selects the instruction set for the build machine.

You can modify the options in mk/spdk.common.mk for SPDK (currently, there is no way to override this without modifying the source, since the user CFLAGS are added before the ones from mk/spdk.common.mk).  For DPDK, you can add an "EXTRA_CFLAGS=-march=generic" to dpdk/config/common_spdk.

Thanks
-- Daniel

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Marushak, Nathan
Sent: Monday, May 21, 2018 6:32 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Compiling error on different types of Intel CPU

I know Jim will answer this better. We had a similar discussion someplace else. I want to say that this has something to do with how you constructed your VM. I think it was the VM was built with some incorrect expectations for CPU emulation.

Jim?
Thanks,
Nate

On May 21, 2018, at 5:21 AM, Luse, Paul E <paul.e.luse(a)intel.com<mailto:paul.e.luse(a)intel.com>> wrote:
Hi,

I'm not the vhost expert but invalid CPU opcode seems unlikely.  If you can send some more information, like log outputs, backtrace from gdb or something that would be helpful.  This is likely an opcode used somewhere along the way and has to do with a vhost or scsi opcode or something.

Thx
Paul

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Bob Chen
Sent: Monday, May 21, 2018 1:12 AM
To: spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>
Subject: [SPDK] Compiling error on different types of Intel CPU

Hi,

I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz.

The app would immediately crash, with below kernel message:

traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0 error:0 in spdk_vhost[400000+a7000]

Incompatible CPU instruction set, I guess?


-Bob
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
https://lists.01.org/mailman/listinfo/spdk

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 8100 bytes --]

Re: [SPDK] Compiling error on different types of Intel CPU

[Marushak, Nathan]

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

I know Jim will answer this better. We had a similar discussion someplace else. I want to say that this has something to do with how you constructed your VM. I think it was the VM was built with some incorrect expectations for CPU emulation.

Jim?

Thanks,
Nate

On May 21, 2018, at 5:21 AM, Luse, Paul E <paul.e.luse(a)intel.com<mailto:paul.e.luse(a)intel.com>> wrote:

Hi,

I’m not the vhost expert but invalid CPU opcode seems unlikely.  If you can send some more information, like log outputs, backtrace from gdb or something that would be helpful.  This is likely an opcode used somewhere along the way and has to do with a vhost or scsi opcode or something.

Thx
Paul

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Bob Chen
Sent: Monday, May 21, 2018 1:12 AM
To: spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>
Subject: [SPDK] Compiling error on different types of Intel CPU

Hi,

I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz.

The app would immediately crash, with below kernel message:

traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0 error:0 in spdk_vhost[400000+a7000]

Incompatible CPU instruction set, I guess?


-Bob
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
https://lists.01.org/mailman/listinfo/spdk

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5081 bytes --]

Re: [SPDK] Compiling error on different types of Intel CPU

[Luse, Paul E]

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

Hi,

I’m not the vhost expert but invalid CPU opcode seems unlikely.  If you can send some more information, like log outputs, backtrace from gdb or something that would be helpful.  This is likely an opcode used somewhere along the way and has to do with a vhost or scsi opcode or something.

Thx
Paul

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Bob Chen
Sent: Monday, May 21, 2018 1:12 AM
To: spdk(a)lists.01.org
Subject: [SPDK] Compiling error on different types of Intel CPU

Hi,

I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz.

The app would immediately crash, with below kernel message:

traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0 error:0 in spdk_vhost[400000+a7000]

Incompatible CPU instruction set, I guess?


-Bob

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4468 bytes --]

[SPDK] Compiling error on different types of Intel CPU

[Bob Chen]

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

Hi,

I was compiling spdk vhost app on a Intel(R) Xeon(R) CPU E5-2650 v4 @
2.20GHz CPU server, and then running it on another of Intel(R) Xeon(R) CPU
E5-2650 v2 @ 2.60GHz.

The app would immediately crash, with below kernel message:

traps: spdk_vhost[35075] trap invalid opcode ip:468569 sp:7ffee17d0ad0
error:0 in spdk_vhost[400000+a7000]

Incompatible CPU instruction set, I guess?


-Bob

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 956 bytes --]