02edbfab1e
Currently, if dev_configure is not called or fails to be called, users can still call dev_start successfully. So it is necessary to have a flag which indicates whether the device is configured, to control whether dev_start can be called and eliminate dependency on user invocation order. The flag stored in "struct rte_eth_dev_data" is more reasonable than "enum rte_eth_dev_state". "enum rte_eth_dev_state" is private to the primary and secondary processes, and can be independently controlled. However, the secondary process does not make resource allocations and does not call dev_configure(). These are done by the primary process and can be obtained or used by the secondary process. So this patch adds a "dev_configured" flag in "rte_eth_dev_data", like "dev_started". Signed-off-by: Huisong Li <lihuisong@huawei.com> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> libabigail raised a warning on this change. This change is fine wrt ABI as far as we understand, but we can't express an exception rule (see libabigail bug #28060) to waive the changes only in this part of the rte_eth_dev_data struct. The solution for now is to globally waive any change on the rte_eth_dev_data structure. Signed-off-by: David Marchand <david.marchand@redhat.com>
55 lines
1.8 KiB
Plaintext
55 lines
1.8 KiB
Plaintext
[suppress_function]
|
|
symbol_version = EXPERIMENTAL
|
|
[suppress_variable]
|
|
symbol_version = EXPERIMENTAL
|
|
|
|
[suppress_function]
|
|
symbol_version = INTERNAL
|
|
[suppress_variable]
|
|
symbol_version = INTERNAL
|
|
|
|
; Ignore generated PMD information strings
|
|
[suppress_variable]
|
|
name_regexp = _pmd_info$
|
|
|
|
; Explicit ignore for driver-only ABI
|
|
[suppress_function]
|
|
name_regexp = rte_vdev_(|un)register
|
|
|
|
; Ignore fields inserted in cacheline boundary of rte_cryptodev
|
|
[suppress_type]
|
|
name = rte_cryptodev
|
|
has_data_member_inserted_between = {offset_after(attached), end}
|
|
|
|
; Ignore fields inserted in union boundary of rte_cryptodev_symmetric_capability
|
|
[suppress_type]
|
|
name = rte_cryptodev_symmetric_capability
|
|
has_data_member_inserted_between = {offset_after(cipher.iv_size), end}
|
|
|
|
; Ignore fields inserted in middle padding of rte_crypto_cipher_xform
|
|
[suppress_type]
|
|
name = rte_crypto_cipher_xform
|
|
has_data_member_inserted_between = {offset_after(key), offset_of(iv)}
|
|
|
|
; Ignore fields inserted in place of reserved fields of rte_eventdev
|
|
[suppress_type]
|
|
name = rte_eventdev
|
|
has_data_member_inserted_between = {offset_after(attached), end}
|
|
|
|
; Ignore fields inserted in alignment hole of rte_eth_rxq_info
|
|
[suppress_type]
|
|
name = rte_eth_rxq_info
|
|
has_data_member_inserted_at = offset_after(scattered_rx)
|
|
|
|
; Ignore fields inserted in cacheline boundary of rte_eth_txq_info
|
|
[suppress_type]
|
|
name = rte_eth_txq_info
|
|
has_data_member_inserted_between = {offset_after(nb_desc), end}
|
|
|
|
; Ignore all changes to rte_eth_dev_data
|
|
; Note: we only cared about dev_configured bit addition, but libabigail
|
|
; seems to wrongly compute bitfields offset.
|
|
; https://sourceware.org/bugzilla/show_bug.cgi?id=28060
|
|
[suppress_type]
|
|
name = rte_eth_dev_data
|