From: "christoph.paasch@uclouvain.be" <christoph.paasch@uclouvain.be>
To: "Brown, Aaron F" <aaron.f.brown@intel.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Wyborny, Carolyn" <carolyn.wyborny@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH net] igb: Unset IGB_FLAG_HAS_MSIX-flag when falling back to msi-only
Date: Mon, 10 Mar 2014 19:50:09 +0100 [thread overview]
Message-ID: <20140310185009.GB8001@cpaasch-mac> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B73157E74@ORSMSX101.amr.corp.intel.com>
Hello Aaron,
On 19/02/14 - 00:05:30, Brown, Aaron F wrote:
> On Wed, 2014-02-19 at 00:36 +0100, Christoph Paasch wrote:
> > rior to cd14ef54d25 (igb: Change to use statically allocated array for
> > MSIx entries), having msix_entries different from NULL was an
> > indicator
> > that MSIX is enabled.
> > In igb_set_interrupt_capabiliy we may fall back to MSI-only. Prior to
> > the above patch msix_entries was set to NULL by
> > igb_reset_interrupt_capability.
> >
> > However, now we are checking the flag for IGB_FLAG_HAS_MSIX and so the
> > stack gets completly confused:
> >
> > [ 42.659791] ------------[ cut here ]------------
> > <snip>
>
> > [ 47.892146] handlers:
> > [ 47.919301] [<ffffffff812fbd7d>] igb_intr
> >
> > So, this patch unsets the flag to indicate that we are not using MSIX.
> > This patch does exactly this: Unsetting the flag when falling back to
> > MSI.
> >
> > Fixes: cd14ef54d25b (igb: Change to use statically allocated array for
> > MSIx entries)
> > Cc: Carolyn Wyborny <carolyn.wyborny@intel.com>
> > Signed-off-by: Christoph Paasch <christoph.paasch@uclouvain.be>
> > ---
> > drivers/net/ethernet/intel/igb/igb_main.c | 1 +
> > 1 file changed, 1 insertion(+)
>
> Thanks Christoph, I have added this to our Jeff's internal queue as
> well.
are the patches in Jeff's queue?
Because, in his last pull request they were not part of it.
I think these patches should make it into 3.14, because my machines are not
booting because of these issues.
Cheers,
Christoph
prev parent reply other threads:[~2014-03-10 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 23:36 [PATCH net] igb: Unset IGB_FLAG_HAS_MSIX-flag when falling back to msi-only Christoph Paasch
2014-02-18 23:55 ` Wyborny, Carolyn
2014-02-19 0:05 ` Brown, Aaron F
2014-03-10 18:50 ` christoph.paasch [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=20140310185009.GB8001@cpaasch-mac \
--to=christoph.paasch@uclouvain.be \
--cc=aaron.f.brown@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
/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