From: Robert Love <rml@tech9.net>
To: Thunder from the hill <thunder@lightweight.ods.org>
Cc: Arador <diegocg@teleline.es>,
dag@newtech.fi,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
conman@kolivas.net
Subject: Re: Preempt note in the logs
Date: 24 Aug 2002 14:11:03 -0400 [thread overview]
Message-ID: <1030212663.861.3.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0208241157590.3234-100000@hawkeye.luckynet.adm>
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
next prev parent reply other threads:[~2002-08-24 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 8:52 Dag Nygren
2002-08-24 9:45 ` Thunder from the hill
2002-08-24 9:58 ` Preempt note in the logs (and patch) Dag Nygren
2002-08-24 16:15 ` Preempt note in the logs Robert Love
2002-08-24 17:02 ` Arador
2002-08-24 17:12 ` Thunder from the hill
2002-08-24 17:48 ` Robert Love
2002-08-24 18:01 ` Thunder from the hill
2002-08-24 18:11 ` Robert Love [this message]
2002-08-24 18:18 ` Thunder from the hill
2002-08-24 18:20 ` Thunder from the hill
2002-08-24 18:55 ` Dag Nygren
2002-08-24 21:15 ` Thunder from the hill
2002-08-24 23:03 ` conman
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=1030212663.861.3.camel@phantasy \
--to=rml@tech9.net \
--cc=conman@kolivas.net \
--cc=dag@newtech.fi \
--cc=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@lightweight.ods.org \
/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
all inboxes | Powered by JetHome®