From: Nicholas Mc Guire <der.herr@hofr.at>
To: linux-rt-users@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andreas Platschek <platschek@ict.tuwien.ac.at>
Subject: Re: [PATCH 2/2] remove recursive call to migrate_disable in write_lock_bh
Date: Thu, 21 Nov 2013 01:11:18 +0100 [thread overview]
Message-ID: <20131121001118.GA26317@opentech.at> (raw)
In-Reply-To: <20131120102734.GA3793@opentech.at>
Hi !
"[PATCH 2/2] remove recursive call to migrate_disable in write_lock_bh"
seems to be blowing up in unpin_current_cpu - seems that I still did not
get the dependencies between interleved write_lock_bh/read_unlock,
read_unlock/write_lock_bh right...
thx!
hofrat
prev parent reply other threads:[~2013-11-21 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 10:27 [PATCH 2/2] remove recursive call to migrate_disable in write_lock_bh Nicholas Mc Guire
2013-11-21 0:11 ` Nicholas Mc Guire [this message]
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=20131121001118.GA26317@opentech.at \
--to=der.herr@hofr.at \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=platschek@ict.tuwien.ac.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).