[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180718072107.0bfdece8@vela.lan>
Date: Wed, 18 Jul 2018 07:21:07 +0900
From: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: hannah@...vell.com, Jonathan Corbet <corbet@....net>,
David Miller <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Josef Griebichler <griebichler.josef@....at>,
Hannes Frederic Sowa <hannes@...hat.com>,
Jesper Dangaard Brouer <jbrouer@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...pensource.com>,
Ingo Molnar <mingo@...nel.org>,
Network Development <netdev@...r.kernel.org>,
Paolo Abeni <pabeni@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Rik van Riel <riel@...hat.com>,
Alan Stern <stern@...land.harvard.edu>,
dma <dmaengine@...r.kernel.org>, vkoul@...nel.org,
Dan Williams <dan.j.williams@...el.com>, nadavh@...vell.com,
thomas.petazzoni@...tlin.com, omrii@...vell.com
Subject: Re: dvb usb issues since kernel 4.9
Hi Linus,
Em Tue, 17 Jul 2018 10:09:28 -0700
Linus Torvalds <torvalds@...ux-foundation.org> escreveu:
> On Tue, Jul 17, 2018 at 4:58 AM Hanna Hawa <hannah@...vell.com> wrote:
> >
> > After some debug/bisect/diff, found that patch "softirq: Let ksoftirqd
> > do its job" is problematic patch.
>
> Ok, this thread died down without any resolution.
>
> >- Using v4.14.0 (including softirq patch) and the additional fix
> > proposed by Linus - no timeout issue.
>
> Are you talking about the patch that made HI_SOFTIRQ and
> TASKLET_SOFTIRQ special, and had this:
>
> #define SOFTIRQ_NOW_MASK ((1 << HI_SOFTIRQ) | (1 << TASKLET_SOFTIRQ))
>
> in it?
>
> I think I'll just commit the damn thing. It's hacky, but it's simple,
> and it never got applied because we had smarter suggestions. But the
> smarter suggestions never ended up being applied either, so..
Yeah, IMHO the best would be to apply your patch[1], c/c stable up to
4.9. Nothing prevents applying a better/smarter solution once we
have it. From my side, I can keep testing whatever smart suggestions
people propose. Yet, better to have one fix on our hand than two
fixes flying around.
[1] e. g.
https://git.linuxtv.org/mchehab/experimental.git/commit/?h=v4.15%2bmedia%2bdwc2&id=ccf833fd4a5b99c3d3cf2c09c065670f74a230a7
Regards,
Mauro
Powered by blists - more mailing lists