From: Clark Williams <williams@redhat.com>
To: pavel@pavlinux.ru
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: Mainline patch-3.14.4-5.xz
Date: Mon, 2 Jun 2014 11:46:58 -0500 [thread overview]
Message-ID: <20140602114658.3c81b2f8@sluggy> (raw)
In-Reply-To: <538A6552.3050501@pavlinux.ru>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
On Sun, 01 Jun 2014 03:27:14 +0400
Pavel Vasilyev <pavel@pavlinux.ru> wrote:
> Vanila patch:
>
> --- a/include/linux/thread_info.h
> +++ b/include/linux/thread_info.h
> @@ -118,8 +118,6 @@ static inline __deprecated void set_need_resched(void)
> */
> }
>
> -#define tif_need_resched() test_thread_flag(TIF_NEED_RESCHED)
> -
> #if defined TIF_RESTORE_SIGMASK && !defined HAVE_SET_RESTORE_SIGMASK
> /*
> * An arch can define its own version of set_restore_sigmask() to get the
>
> RT Code (same file):
>
>
> #ifdef CONFIG_PREEMPT_LAZY
> #define tif_need_resched() (test_thread_flag(TIF_NEED_RESCHED) || \
> test_thread_flag(TIF_NEED_RESCHED_LAZY))
> #define tif_need_resched_now() (test_thread_flag(TIF_NEED_RESCHED))
> #define tif_need_resched_lazy() (test_thread_flag(TIF_NEED_RESCHED_LAZY))
>
> #else
> #define tif_need_resched() (test_thread_flag(TIF_NEED_RESCHED))
> #define tif_need_resched_now() (test_thread_flag(TIF_NEED_RESCHED))
> #define tif_need_resched_lazy() (0)
>
> #endif
>
> 1 out of 1 hunk ignored -- saving rejects to file include/linux/thread_info.h.rej
>
>
> What to do? :)
>
I thought I was the only one to do crazy rebasing like this :)
I kept the #ifdef CONFIG_PREEMPT_LAZY block (the RT code) in
include/linux/thread_info.h and removed the definition of
tif_need_resched() in include/linux/preempt.h.
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-06-02 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 23:27 Mainline patch-3.14.4-5.xz Pavel Vasilyev
2014-06-02 16:46 ` Clark Williams [this message]
2014-06-02 22:02 ` Pavel Vasilyev
2014-06-02 22:07 ` Clark Williams
2014-06-02 22:13 ` Pavel Vasilyev
2014-06-03 0:04 ` Pavel Vasilyev
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=20140602114658.3c81b2f8@sluggy \
--to=williams@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@pavlinux.ru \
/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).