From: Roland Dreier <rdreier@cisco.com>
To: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH 1/7] mlx4: Added interrupts test support
Date: Mon, 05 Oct 2009 09:18:23 -0700 [thread overview]
Message-ID: <adar5tholv4.fsf@cisco.com> (raw)
In-Reply-To: <4AC9D59F.1090409@mellanox.co.il> (Yevgeny Petrilin's message of "Mon, 05 Oct 2009 13:16:47 +0200")
> > Have you actually seen cases where
> > the interrupt test during initialization works but then this test
> > catches a problem? (My experience has been that if any MSI-X interrupts
> > work from a device, then they'll all work)
> It also checks that all the EQs work properly. During initialization
> we only check the asynchronous EQ
Yes, I understand what the code does. My question was whether you have
ever actually observed a case where the async EQ works but another EQ
doesn't? In other words is this test useful in practice?
- R.
prev parent reply other threads:[~2009-10-05 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 14:32 [PATCH 1/7] mlx4: Added interrupts test support Yevgeny Petrilin
2009-10-02 3:32 ` Roland Dreier
2009-10-02 5:27 ` David Miller
2009-10-05 11:16 ` Yevgeny Petrilin
2009-10-05 16:18 ` Roland Dreier [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=adar5tholv4.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.co.il \
/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;
as well as URLs for NNTP newsgroup(s).