Enable s390x Support for mstflint (CentOS Stream 9/10, RHEL 9 )

[ashokpariya0]

We are running real ConnectX-6 Lx cards on IBM Z

[root@b314lp37 ~]# uname -m
s390x

# lspci
00f9:00:00.0 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function
00fa:00:00.0 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function
0108:00:00.0 Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
0109:00:00.1 Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6 Lx]

There are no RPMs at all:

yum install mstflint
# → Error: Unable to find a match: mstflint

So we follow the official README instructions exactly:

## Installation
    a) Build the mstflint utility. This package is built using a standard
       autotools method.

       NOTE: if you are trying to build from the GitHub repository, need to run ./autogen.sh first.

       Example:
       > ./autogen.sh
       > mkdir build
       > cd build
       > ../configure
       > make
       > make install

Request

1)Provide official s390x RPMs for CentOS Stream 9/10.
Add s390x architecture support to the build system,

Direct upstream impact:
The SR-IOV Network Operator cannot build its sriov-network-config-daemon image on s390x because it depends on mstflint for Mellanox card configuration:
https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/master/Dockerfile.sriov-network-config-daemon

We have real ConnectX-6 Lx cards on IBM Z and are ready to test patches immediately.

[ashokpariya0]

cc @ahmadawwad

[ogalbxela]

Thank you for your interest in our product.
Unfortunately, the core team maintaining this product doesn't have the bandwidth to work with distributions. We provide a code base to be built on the target machine. If you are interested in building a package, creation of deb/rpm is also supported (see README or release notes for references). Please be note that we don't verify/officially support cross compilation.

Although, you may have noticed occurences of mstflint package for some distributions (like Debian/Ubuntu/SUSE) - those are fully driven by community and not a core team.
If you think the product may benefit from adding it to a distribution under questions and you believe any changes in the product codebase are required to achieve that - please go ahead and submit a pull request with those changes for us to consider. In case if it won't be a breaking change for any existing use case - it may become a part of our codebase.