From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
intel-wired-lan@lists.osuosl.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Yan Vugenfirer <yan@daynix.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>
Subject: Re: [PATCH v3] igb: Allocate MSI-X vector when testing
Date: Fri, 25 Nov 2022 18:48:38 +0900 [thread overview]
Message-ID: <4a2d4e3e-5b15-2c58-dc49-92908ab80ad0@daynix.com> (raw)
In-Reply-To: <Y34/LDxCnYd6VGJ2@boxer>
On 2022/11/24 0:41, Maciej Fijalkowski wrote:
> On Wed, Nov 23, 2022 at 10:09:26AM +0900, Akihiko Odaki wrote:
>> Without this change, the interrupt test fail with MSI-X environment:
>>
>> $ sudo ethtool -t enp0s2 offline
>> [ 43.921783] igb 0000:00:02.0: offline testing starting
>> [ 44.855824] igb 0000:00:02.0 enp0s2: igb: enp0s2 NIC Link is Down
>> [ 44.961249] igb 0000:00:02.0 enp0s2: igb: enp0s2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
>> [ 51.272202] igb 0000:00:02.0: testing shared interrupt
>> [ 56.996975] igb 0000:00:02.0 enp0s2: igb: enp0s2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
>> The test result is FAIL
>> The test extra info:
>> Register test (offline) 0
>> Eeprom test (offline) 0
>> Interrupt test (offline) 4
>> Loopback test (offline) 0
>> Link test (on/offline) 0
>>
>> Here, "4" means an expected interrupt was not delivered.
>>
>> To fix this, route IRQs correctly to the first MSI-X vector by setting
>> IVAR_MISC. Also, set bit 0 of EIMS so that the vector will not be
>> masked. The interrupt test now runs properly with this change:
>
> Much better!
>
>>
>> $ sudo ethtool -t enp0s2 offline
>> [ 42.762985] igb 0000:00:02.0: offline testing starting
>> [ 50.141967] igb 0000:00:02.0: testing shared interrupt
>> [ 56.163957] igb 0000:00:02.0 enp0s2: igb: enp0s2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
>> The test result is PASS
>> The test extra info:
>> Register test (offline) 0
>> Eeprom test (offline) 0
>> Interrupt test (offline) 0
>> Loopback test (offline) 0
>> Link test (on/offline) 0
>>
>> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>
> Same comment as on other patch - justify why there is no fixes tag and
> specify the tree in subject.
I couldn't identify what commit introduced the problem. Please see:
https://lore.kernel.org/netdev/f2457229-865a-57a0-94a1-c5c63b2f30a5@daynix.com/
Regards,
Akihiko Odaki
>
>> ---
>> drivers/net/ethernet/intel/igb/igb_ethtool.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/net/ethernet/intel/igb/igb_ethtool.c b/drivers/net/ethernet/intel/igb/igb_ethtool.c
>> index e5f3e7680dc6..ff911af16a4b 100644
>> --- a/drivers/net/ethernet/intel/igb/igb_ethtool.c
>> +++ b/drivers/net/ethernet/intel/igb/igb_ethtool.c
>> @@ -1413,6 +1413,8 @@ static int igb_intr_test(struct igb_adapter *adapter, u64 *data)
>> *data = 1;
>> return -1;
>> }
>> + wr32(E1000_IVAR_MISC, E1000_IVAR_VALID << 8);
>> + wr32(E1000_EIMS, BIT(0));
>> } else if (adapter->flags & IGB_FLAG_HAS_MSI) {
>> shared_int = false;
>> if (request_irq(irq,
>> --
>> 2.38.1
>>
next prev parent reply other threads:[~2022-11-25 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 1:09 [PATCH v3] igb: Allocate MSI-X vector when testing Akihiko Odaki
2022-11-23 15:41 ` Maciej Fijalkowski
2022-11-25 9:48 ` Akihiko Odaki [this message]
2022-11-25 9:50 ` Akihiko Odaki
2022-11-25 13:12 ` Maciej Fijalkowski
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=4a2d4e3e-5b15-2c58-dc49-92908ab80ad0@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.com \
/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