From: Paolo Abeni <pabeni@redhat.com>
To: mike.marciniszyn@gmail.com,
Alexander Duyck <alexanderduyck@fb.com>,
Jakub Kicinski <kuba@kernel.org>,
kernel-team@meta.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Jacob Keller <jacob.e.keller@intel.com>,
Mohsin Bashir <mohsin.bashr@gmail.com>,
Lee Trager <lee@trager.us>,
Dan Carpenter <dan.carpenter@linaro.org>,
Pei Xiao <xiaopei01@kylinos.cn>,
Stanislav Fomichev <sdf@fomichev.me>,
Kuniyuki Iwashima <kuniyu@google.com>,
Samiullah Khawaja <skhawaja@google.com>,
Ahmed Zaki <ahmed.zaki@intel.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v12 3/5] eth fbnic: Add msix self test
Date: Tue, 10 Feb 2026 16:06:23 +0100 [thread overview]
Message-ID: <e806861b-acd4-4615-aada-577e0275bb5d@redhat.com> (raw)
In-Reply-To: <20260206154246.814-4-mike.marciniszyn@gmail.com>
On 2/6/26 4:42 PM, mike.marciniszyn@gmail.com wrote:
> +/**
> + * fbnic_msix_test - Verify behavior of NIC interrupts
> + * @fbd: device to test
> + *
> + * This function is meant to test the global interrupt registers and the
> + * PCIe IP MSI-X functionality. It essentially goes through and tests
> + * test various combinations of the set, clear, and mask bits in order to
> + * verify the behavior is as we expect it to be from the driver.
> + *
> + * Return: non-zero on failure.
> + **/
> +int fbnic_msix_test(struct fbnic_dev *fbd)
> +{
> + struct pci_dev *pdev = to_pci_dev(fbd->dev);
> + struct fbnic_msix_test_data *test_data;
> + int result = 0;
> + u32 mask = 0;
> + int i;
> +
> + /* Allocate bitmap and IRQ vector table */
> + test_data = kzalloc(sizeof(*test_data), GFP_KERNEL);
> +
> + /* Result = 5 for memory allocation failure */
> + if (!test_data)
> + return 5;
Instead of magic numbers you could define some macros, or simply return
a boolean success/failures value (as the caller ignores the error code).
/P
next prev parent reply other threads:[~2026-02-10 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 15:42 [PATCH net-next v12 0/5] eth fbnic: Add fbnic self tests mike.marciniszyn
2026-02-06 15:42 ` [PATCH net-next v12 1/5] net: export netif_open for self_test usage mike.marciniszyn
2026-02-06 15:42 ` [PATCH net-next v12 2/5] eth fbnic: Add register self test mike.marciniszyn
2026-02-06 15:42 ` [PATCH net-next v12 3/5] eth fbnic: Add msix " mike.marciniszyn
2026-02-10 15:06 ` Paolo Abeni [this message]
2026-02-10 18:06 ` Mike Marciniszyn
2026-02-10 22:55 ` Keller, Jacob E
2026-02-06 15:42 ` [PATCH net-next v12 4/5] eth fbnic: TLV support for use by MBX " mike.marciniszyn
2026-02-06 15:42 ` [PATCH net-next v12 5/5] eth fbnic: Add mailbox " mike.marciniszyn
2026-02-06 15:48 ` [PATCH net-next v12 0/5] eth fbnic: Add fbnic self tests Mike Marciniszyn
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=e806861b-acd4-4615-aada-577e0275bb5d@redhat.com \
--to=pabeni@redhat.com \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=lee@trager.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mike.marciniszyn@gmail.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=skhawaja@google.com \
--cc=xiaopei01@kylinos.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox