From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Subject: Re: V4L-DVB drivers and BKL
Date: Sat, 03 Apr 2010 16:19:35 +0200 [thread overview]
Message-ID: <4BB74E77.7010703@s5r6.in-berlin.de> (raw)
In-Reply-To: <4BB4A7C6.40207@redhat.com>
Mauro Carvalho Chehab wrote:
> Hans Verkuil wrote:
>> On the DVB side there seem to be only two sources that use the BKL:
>>
>> linux/drivers/media/dvb/bt8xx/dst_ca.c: lock_kernel();
>> linux/drivers/media/dvb/bt8xx/dst_ca.c: unlock_kernel();
>> linux/drivers/media/dvb/dvb-core/dvbdev.c: lock_kernel();
>> linux/drivers/media/dvb/dvb-core/dvbdev.c: unlock_kernel();
>> linux/drivers/media/dvb/dvb-core/dvbdev.c: unlock_kernel();
>>
>> At first glance it doesn't seem too difficult to remove them, but I leave
>> that to the DVB experts.
>
> The main issue is at dvbdev, since it is used by all devices. We need to get rid
> of it.
Get rid of its lock_kernel in open and its locked ioctl, or of the
dvbdev 'library' itself?
> That's said, Stefan Richter sent a patch meant to reduce the issues with
> DVB. Unfortunately, I haven't seen any comments on it. It would be really important
> to test his approach.
I will attempt to continue with this (convert more drivers if not all,
in a properly organized patch series for review), though it won't happen
overnight as I'm chronically short of spare time. I.e. if others step
in, even better.
--
Stefan Richter
-=====-==-=- -=-- ---==
http://arcgraph.de/sr/
prev parent reply other threads:[~2010-04-03 14:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 8:01 V4L-DVB drivers and BKL Hans Verkuil
2010-04-01 9:23 ` Laurent Pinchart
2010-04-01 11:11 ` Hans Verkuil
2010-04-01 12:11 ` Laurent Pinchart
2010-04-01 14:12 ` Mauro Carvalho Chehab
2010-04-01 14:30 ` Laurent Pinchart
2010-04-01 14:44 ` Mauro Carvalho Chehab
2010-04-01 14:42 ` Hans Verkuil
2010-04-01 15:02 ` Mauro Carvalho Chehab
2010-04-01 15:27 ` Hans Verkuil
2010-04-01 16:58 ` Devin Heitmueller
2010-04-01 17:36 ` Mauro Carvalho Chehab
2010-04-01 18:29 ` Devin Heitmueller
2010-04-01 18:42 ` Mauro Carvalho Chehab
2010-04-01 18:56 ` Devin Heitmueller
2010-04-01 21:07 ` Mauro Carvalho Chehab
2010-04-01 21:40 ` Devin Heitmueller
2010-04-01 23:10 ` Mauro Carvalho Chehab
2010-04-01 21:11 ` Hans Verkuil
2010-04-01 21:06 ` Hans Verkuil
2010-04-01 21:16 ` Mauro Carvalho Chehab
2010-04-01 21:29 ` Devin Heitmueller
2010-04-03 0:23 ` Andy Walls
2010-04-07 20:07 ` [PATCH] em28xx: fix locks during dvb init sequence - was: " Mauro Carvalho Chehab
2010-04-07 20:15 ` Devin Heitmueller
2010-04-07 20:23 ` Mauro Carvalho Chehab
2010-04-01 11:57 ` Stefan Richter
2010-04-01 12:11 ` Hans Verkuil
2010-04-01 12:08 ` Stefan Richter
2010-04-01 12:12 ` Stefan Richter
2010-04-01 14:03 ` Mauro Carvalho Chehab
2010-04-03 14:19 ` Stefan Richter [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=4BB74E77.7010703@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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