All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	Li Zefan <lizf@cn.fujitsu.com>,
	linux-kernel@vger.kernel.org
Subject: Re: LTTng "TIF_KERNEL_TRACE"
Date: Tue, 28 Apr 2009 18:44:21 +0200	[thread overview]
Message-ID: <20090428164420.GA7337@nowhere> (raw)
In-Reply-To: <20090428163825.GA2030@Krystal>

On Tue, Apr 28, 2009 at 12:38:25PM -0400, Mathieu Desnoyers wrote:
> No, read-write lock is a "special case" where it does not deadlock if
> you have an interrupt handler taking the read lock over another read
> lock. It's just the write lock that _must absolutely_ disable
> interrupts.


Ah, you're right, I was thinking with spinlock rules in mind :)


> However, the "latency race" scenario I explained above applies here,
> because the write lock disables interrupts and the read locks doesn't.
> 
> Mathieu
> 


  reply	other threads:[~2009-04-28 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 13:20 LTTng "TIF_KERNEL_TRACE" Mathieu Desnoyers
2009-04-28 15:01 ` Ingo Molnar
2009-04-28 15:21   ` Mathieu Desnoyers
2009-04-28 15:40   ` Mathieu Desnoyers
2009-04-28 16:33     ` Frederic Weisbecker
2009-04-28 16:37       ` Frédéric Weisbecker
2009-04-28 16:38       ` Mathieu Desnoyers
2009-04-28 16:44         ` Frederic Weisbecker [this message]
2009-04-28 16:52           ` Steven Rostedt
2009-04-28 16:43       ` Steven Rostedt
2009-04-28 16:48         ` Frederic Weisbecker

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=20090428164420.GA7337@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.