Hello!
===
[ INFO: possible circular locking dependency detected ]
2.6.21.1-cfs-v11 #4
---
tvtime/6360 is trying to acquire lock:
(&mm->mmap_sem){}, at: []
videobuf_dma_init_user+0xb6/0x14
Linus Torvalds wrote:
On Fri, 27 Apr 2007, John Anthony Kazos Jr. wrote:
Could[/should] this stuff be changed from ratios to amounts? Or a quick
boot-time test to use a ratio if the memory is small and an amount (like
tax brackets, I would expect) if it's great?
Yes, the "percentage" thing w
Ulrich Drepper wrote:
A solution for this problem is a madvise() operation with the following
property:
- the content of the address range can be discarded
- if an access to a page in the range happens in the future it must
succeed. The old page content can be provided or a new, empty
Linus Torvalds wrote:
On Thu, 8 Mar 2007, Davide Libenzi wrote:
So, to cut it short, I can do the pseudo-siginfo read(2), but I don't
like it too much (little, actually). The siginfo, as bad as it is, is a
standard used in many POSIX APIs (hence even in kernel), and IMO if we
want to send tha
Linus Torvalds wrote:
On Thu, 8 Mar 2007, Davide Libenzi wrote:
So, to cut it short, I can do the pseudo-siginfo read(2), but I don't
like it too much (little, actually). The siginfo, as bad as it is, is a
standard used in many POSIX APIs (hence even in kernel), and IMO if we
want to send tha
Otto Wyss wrote:
> No
mouse or keyboard input was possible. I was completely stuck, IMO
something _never_ should happen. Who's to blame for this situation:
wxWidgets, GDB, GCC/G++, X or the Linux kernel? Or any combination?
This is by design in X. XGrabKeyboard and XGrabPointer are usually to
blam
>In fact, if you did leave the read queued in a daemon using select()
>before, you'd keep looping endlessly taking all CPU and never idle
>because there would always be read data available.
Also, level triggered notifications would also seem to cause
multiple thread wakeups and thundering herd p
7 matches
Mail list logo
