From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: linux-rt-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andreas Platschek <platschek@ict.tuwien.ac.at>
Subject: Re: [PATCH] allow preemption in recursive migrate_disable call
Date: Fri, 22 Nov 2013 18:37:51 +0100 [thread overview]
Message-ID: <20131122173750.GJ8698@linutronix.de> (raw)
In-Reply-To: <20131120003333.GA13545@opentech.at>
* Nicholas Mc Guire | 2013-11-20 01:33:33 [+0100]:
> Minor cleanup in migrate_disable/migrate_enable. The recursive case
> does not need to disable preemption as it is "pinned" to the current
> cpu any way so it is safe to preempt it.
>
> No functional change to migrate_disable/enable
applied but I dropped this line^
>
>Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
Sebastian
prev parent reply other threads:[~2013-11-22 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 0:33 [PATCH] allow preemption in recursive migrate_disable call Nicholas Mc Guire
2013-11-21 10:19 ` Peter Zijlstra
2013-11-22 15:51 ` Sebastian Andrzej Siewior
2013-11-23 5:19 ` Nicholas Mc Guire
2013-11-22 17:37 ` Sebastian Andrzej Siewior [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=20131122173750.GJ8698@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=der.herr@hofr.at \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=platschek@ict.tuwien.ac.at \
--cc=tglx@linutronix.de \
/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).