public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Akihiko Odaki <akihiko.odaki@daynix.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 14:12:21 +0100	[thread overview]
Message-ID: <Y4C/NZEDxH00z/hT@boxer> (raw)
In-Reply-To: <1434bd67-1707-7e43-96b6-d2294ff7f04d@daynix.com>

On Fri, Nov 25, 2022 at 06:50:45PM +0900, Akihiko Odaki wrote:
> On 2022/11/25 18:48, Akihiko Odaki wrote:
> > 
> > 
> > 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/
> 
> Sorry, the URL was wrong. The correct URL is:
> https://lore.kernel.org/netdev/be5617fe-d332-447a-b836-bec9a6c6d42d@daynix.com/

Please change the subject to:
[PATCH net v4] igb: Allocate MSI-X vector when testing

and add n the body
Fixes: 4eefa8f01314 ("igb: add single vector msi-x testing to interrupt test")

Also, it is a good practice to include changes between revisions even if
it is only a rewrite of a commit message.

> 
> Regards,
> Akihiko Odaki
> 
> > 
> > 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));

Should these registers be cleared at the end of igb_intr_test?

> > > >       } else if (adapter->flags & IGB_FLAG_HAS_MSI) {
> > > >           shared_int = false;
> > > >           if (request_irq(irq,
> > > > -- 
> > > > 2.38.1
> > > > 

      reply	other threads:[~2022-11-25 13:12 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
2022-11-25  9:50     ` Akihiko Odaki
2022-11-25 13:12       ` Maciej Fijalkowski [this message]

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=Y4C/NZEDxH00z/hT@boxer \
    --to=maciej.fijalkowski@intel.com \
    --cc=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=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