From: Robert Love <rml@novell.com>
To: dwalker@mvista.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch] Voluntary Preempt additions
Date: Mon, 18 Oct 2004 14:30:52 -0400 [thread overview]
Message-ID: <1098124252.1597.8.camel@betsy.boston.ximian.com> (raw)
In-Reply-To: <1098121769.26597.5.camel@dhcp153.mvista.com>
On Mon, 2004-10-18 at 10:49 -0700, Daniel Walker wrote:
> - Modified latency tracer to trace non-preemptable mutex locking , in
> /proc/lock_trace
Why?
It is a bug to have preemption disabled when entering non-atomic
(schedulable) code, and a stack trace is dumped if that happens.
Isn't that sufficient?
Robert Love
next prev parent reply other threads:[~2004-10-18 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 17:49 Daniel Walker
2004-10-18 18:13 ` Ingo Molnar
2004-10-18 18:30 ` Robert Love [this message]
2004-10-18 18:38 ` Ingo Molnar
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=1098124252.1597.8.camel@betsy.boston.ximian.com \
--to=rml@novell.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®