All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
	galak@codeaurora.org, netdev@vger.kernel.org,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH resend] Renesas Ethernet AVB driver
Date: Mon, 13 Apr 2015 23:08:04 +0000	[thread overview]
Message-ID: <1428966484.8341.52.camel@xylophone.i.decadent.org.uk> (raw)
In-Reply-To: <552C48F7.5030901@gmx.de>

On Tue, 2015-04-14 at 00:53 +0200, Lino Sanfilippo wrote:
> On 14.04.2015 00:31, Ben Hutchings wrote:
> 
> >> >> This driver looks somewhat similar to sh-eth, but lacks some of the
> >> >> recent bug fixes made to that.  At least commit 283e38db65e7 ("sh_eth:
> >> >> Fix serialisation of interrupt disable with interrupt & NAPI handler")
> >> >> appears to be applicable, but there are probably others.
> >> > 
> >> >     I suspect this issue applies to many drivers...
> >> >     I couldn't reproduce the bug that patch was fixing, so left this fix out 
> >> > for the time being. Others cases were fixed (if applicable).
> >> 
> >> Maybe its just harder to trigger but it indeed looks similar to what Ben
> >> has fixed for sh-eth. I wonder if that shutdown flag in the fix is
> >> really needed though. IMHO it should be save if we simply call
> >> napi_disable first, then disable irqs on hardware and finally
> >> synchronize_irq...
> > 
> > In sh_eth: if we call napi_disable() first, EESR_RX_CHECK can still be
> > set and nothing will clear it.  If only one CPU is online this can hard
> > hang the system.  Please trust that I did consider and rule out the
> > simpler approaches first.
> > 
> 
> The idea was to check the return value from napi_schedule_prep() and in
> case it returns "false" use this as an indication for a shutdown. In
> case of sh_eth this would be sh_eth_write(ndev, 0, EESIPR) for example.

Might work - but please give it a thorough test.

Ben.



WARNING: multiple messages have this Message-ID (diff)
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
	galak@codeaurora.org, netdev@vger.kernel.org,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH resend] Renesas Ethernet AVB driver
Date: Tue, 14 Apr 2015 00:08:04 +0100	[thread overview]
Message-ID: <1428966484.8341.52.camel@xylophone.i.decadent.org.uk> (raw)
In-Reply-To: <552C48F7.5030901@gmx.de>

On Tue, 2015-04-14 at 00:53 +0200, Lino Sanfilippo wrote:
> On 14.04.2015 00:31, Ben Hutchings wrote:
> 
> >> >> This driver looks somewhat similar to sh-eth, but lacks some of the
> >> >> recent bug fixes made to that.  At least commit 283e38db65e7 ("sh_eth:
> >> >> Fix serialisation of interrupt disable with interrupt & NAPI handler")
> >> >> appears to be applicable, but there are probably others.
> >> > 
> >> >     I suspect this issue applies to many drivers...
> >> >     I couldn't reproduce the bug that patch was fixing, so left this fix out 
> >> > for the time being. Others cases were fixed (if applicable).
> >> 
> >> Maybe its just harder to trigger but it indeed looks similar to what Ben
> >> has fixed for sh-eth. I wonder if that shutdown flag in the fix is
> >> really needed though. IMHO it should be save if we simply call
> >> napi_disable first, then disable irqs on hardware and finally
> >> synchronize_irq...
> > 
> > In sh_eth: if we call napi_disable() first, EESR_RX_CHECK can still be
> > set and nothing will clear it.  If only one CPU is online this can hard
> > hang the system.  Please trust that I did consider and rule out the
> > simpler approaches first.
> > 
> 
> The idea was to check the return value from napi_schedule_prep() and in
> case it returns "false" use this as an indication for a shutdown. In
> case of sh_eth this would be sh_eth_write(ndev, 0, EESIPR) for example.

Might work - but please give it a thorough test.

Ben.



  reply	other threads:[~2015-04-13 23:08 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 23:13 [PATCH resend] Renesas Ethernet AVB driver Sergei Shtylyov
2015-03-27 23:13 ` Sergei Shtylyov
2015-03-28  5:17 ` Lino Sanfilippo
2015-03-28  5:17   ` Lino Sanfilippo
2015-03-28  8:36   ` Richard Cochran
2015-03-28  8:36     ` Richard Cochran
2015-03-28 13:55   ` Sergei Shtylyov
2015-03-28 13:55     ` Sergei Shtylyov
2015-03-28  8:28 ` Richard Cochran
2015-03-28  8:28   ` Richard Cochran
2015-03-28 18:26   ` David Miller
2015-03-28 18:26     ` David Miller
2015-03-30 22:51   ` Sergei Shtylyov
2015-03-30 22:51     ` Sergei Shtylyov
2015-03-31  6:43     ` Richard Cochran
2015-03-31  6:43       ` Richard Cochran
2015-03-31  9:01       ` Richard Cochran
2015-03-31  9:01         ` Richard Cochran
2015-03-31 15:38       ` David Miller
2015-03-31 15:38         ` David Miller
2015-03-31 17:40         ` Sergei Shtylyov
2015-03-31 17:40           ` Sergei Shtylyov
2015-03-31 17:48           ` David Miller
2015-03-31 17:48             ` David Miller
2015-04-03  6:27             ` masaru.nagai.vx
2015-04-03  6:27               ` masaru.nagai.vx
2015-04-03  6:27               ` masaru.nagai.vx
2015-04-12 22:03               ` Sergei Shtylyov
2015-04-12 22:03                 ` Sergei Shtylyov
2015-04-09 13:11       ` Bjørn Mork
2015-04-09 13:11         ` Bjørn Mork
2015-04-09 17:57         ` David Miller
2015-04-09 17:57           ` David Miller
2015-04-13 20:23     ` Sergei Shtylyov
2015-04-13 20:23       ` Sergei Shtylyov
2015-04-14  5:27       ` Richard Cochran
2015-04-14  5:27         ` Richard Cochran
2015-04-14 10:14         ` Sergei Shtylyov
2015-04-14 10:14           ` Sergei Shtylyov
2015-04-14 16:30           ` Richard Cochran
2015-04-14 16:30             ` Richard Cochran
2015-04-14 16:58             ` Sergei Shtylyov
2015-04-14 16:58               ` Sergei Shtylyov
2015-04-14 18:30               ` Richard Cochran
2015-04-14 18:30                 ` Richard Cochran
2015-04-15  1:01                 ` masaru.nagai.vx
2015-04-15  1:01                   ` masaru.nagai.vx
2015-04-15  1:01                   ` masaru.nagai.vx
2015-04-15  5:31                   ` Richard Cochran
2015-04-15  5:31                     ` Richard Cochran
2015-04-02 13:56 ` Ben Hutchings
2015-04-02 13:56   ` Ben Hutchings
2015-04-13 20:34   ` Sergei Shtylyov
2015-04-13 20:34     ` Sergei Shtylyov
2015-04-13 22:13     ` Lino Sanfilippo
2015-04-13 22:13       ` Lino Sanfilippo
2015-04-13 22:31       ` Ben Hutchings
2015-04-13 22:31         ` Ben Hutchings
2015-04-13 22:53         ` Lino Sanfilippo
2015-04-13 22:53           ` Lino Sanfilippo
2015-04-13 23:08           ` Ben Hutchings [this message]
2015-04-13 23:08             ` Ben Hutchings

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=1428966484.8341.52.camel@xylophone.i.decadent.org.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=LinoSanfilippo@gmx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-sh@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.