lkml.org 
[lkml]   [2002]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Preempt note in the logs
From
Date
On Sat, 2002-08-24 at 14:01, Thunder from the hill wrote:

> Do you think it's useful to temporarily put a lock counter into struct
> task (TEMPORARILY, Linus, temporarily!) and check that as well? Maybe that
> will point us something.

There already is, it is called preempt_count.

> Or we should extend that whole crap a bit so we could see exactly what
> caused the preemption count to rise. I don't know if we can do that, but
> we can try doing that.

A lock trace would be helpful here. But since I know normal kernel code
is not suspect, all these users need to do is find which oddball module
or patch they are using... e.g. watch it be nvidia.

Robert Love

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.057 / U:0.420 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site