From: Jon S. <jon...@ya...> - 2004-08-22 01:51:46
|
Michel pointed out that all IOCTL calls hold the big kernel lock. Releasing this lock is sure to case problems since the DRM code is not designed to be reentrant. I don't know what it will take to fix locking to allow this, maybe one of the original DRM authors will pop in here with the answer. Until locking is adjusted we can't add the schedule call. --- Fernando Pablo Lopez-Lezcano <na...@cc...> wrote: > On Fri, 2004-08-20 at 22:59, Jon Smirl wrote: > > I don't believe the DRM drivers are holding any global kernel locks > > when they do wait_for_fifo. Any locks held would be internal to DRM > and > > can be changed if needed. > > There must be a lock. I used to use a patch that I found somewhere > (that > does conditional reschedules), but it triggers the "scheduling while > lock held" kernel oops if you enable that option in the kernel > configuration. > > -- Fernando > > > --- Lee Revell <rlr...@jo...> wrote: > > > > > On Sat, 2004-08-21 at 01:29, Jon Smirl wrote: > > > > > > > What's the right way to write a loop like this that meets the > above > > > > requirements and also satisfies the audio needs? > > > > > > > > > > I think it depends on which locks you are holding, and what kind > of > > > locks they are. > > > > > > Lee > > > > > > > > > > > > ===== > > Jon Smirl > > jon...@ya... > > > > > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Mail Address AutoComplete - You start. We finish. > > http://promotions.yahoo.com/new_mail > > ===== Jon Smirl jon...@ya... __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail |