public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Gao Xiang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
	koujilong@huawei.com, akpm@linux-foundation.org, tj@kernel.org,
	miaoxie@huawei.com, mingo@kernel.org, peterz@infradead.org,
	gaoxiang25@huawei.com, tglx@linutronix.de,
	torvalds@linux-foundation.org
Subject: [tip:sched/core] sched/core: Add __sched tag for io_schedule()
Date: Mon, 17 Jun 2019 07:20:05 -0700	[thread overview]
Message-ID: <tip-e3b929b0a184edb35531153c5afcaebb09014f9d@git.kernel.org> (raw)
In-Reply-To: <20190603091338.2695-1-gaoxiang25@huawei.com>

Commit-ID:  e3b929b0a184edb35531153c5afcaebb09014f9d
Gitweb:     https://git.kernel.org/tip/e3b929b0a184edb35531153c5afcaebb09014f9d
Author:     Gao Xiang <gaoxiang25@huawei.com>
AuthorDate: Mon, 3 Jun 2019 17:13:38 +0800
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Mon, 17 Jun 2019 12:15:56 +0200

sched/core: Add __sched tag for io_schedule()

Non-inline io_schedule() was introduced in:

  commit 10ab56434f2f ("sched/core: Separate out io_schedule_prepare() and io_schedule_finish()")

Keep in line with io_schedule_timeout(), otherwise "/proc/<pid>/wchan" will
report io_schedule() rather than its callers when waiting for IO.

Reported-by: Jilong Kou <koujilong@huawei.com>
Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miao Xie <miaoxie@huawei.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Fixes: 10ab56434f2f ("sched/core: Separate out io_schedule_prepare() and io_schedule_finish()")
Link: https://lkml.kernel.org/r/20190603091338.2695-1-gaoxiang25@huawei.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 kernel/sched/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 29984d8c41f0..cd047927f707 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5122,7 +5122,7 @@ long __sched io_schedule_timeout(long timeout)
 }
 EXPORT_SYMBOL(io_schedule_timeout);
 
-void io_schedule(void)
+void __sched io_schedule(void)
 {
 	int token;
 

      parent reply	other threads:[~2019-06-17 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31  8:29 [PATCH] sched/core: add __sched tag for io_schedule() Gao Xiang
2019-05-31 14:37 ` Tejun Heo
2019-06-03  4:25   ` Gao Xiang
2019-06-03  8:58 ` Peter Zijlstra
2019-06-03  9:00   ` Gao Xiang
2019-06-03  9:13 ` [PATCH v2] " Gao Xiang
2019-06-03  9:44   ` Peter Zijlstra
2019-06-12 11:34   ` Gao Xiang
2019-06-17 14:20   ` tip-bot for Gao Xiang [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=tip-e3b929b0a184edb35531153c5afcaebb09014f9d@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=gaoxiang25@huawei.com \
    --cc=hpa@zytor.com \
    --cc=koujilong@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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