Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 1/4] sched: Export io_schedule_timeout()
Date: Mon,  1 Nov 2010 13:23:41 -0700	[thread overview]
Message-ID: <1288643024-5706-2-git-send-email-eric@anholt.net> (raw)
In-Reply-To: <1288643024-5706-1-git-send-email-eric@anholt.net>

This is the logical partner to the already exported io_schedule() and
schedule_timeout(), and will be used by the DRM.

Signed-off-by: Eric Anholt <eric@anholt.net>
---
 kernel/sched.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/kernel/sched.c b/kernel/sched.c
index aa14a56..ec853f9 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -5287,6 +5287,7 @@ long __sched io_schedule_timeout(long timeout)
 	delayacct_blkio_end();
 	return ret;
 }
+EXPORT_SYMBOL(io_schedule_timeout);
 
 /**
  * sys_sched_get_priority_max - return maximum RT priority.
-- 
1.7.2.3

  reply	other threads:[~2010-11-01 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 20:23 [RFC] Hack to avoid C-state reduction during graphics activity Eric Anholt
2010-11-01 20:23 ` Eric Anholt [this message]
2010-11-01 20:23 ` [PATCH 2/4] Add io_ variants of wait_event() and wait_event_interruptible() Eric Anholt
2010-11-01 20:23 ` [PATCH 3/4] drm/i915: Declare waits on GPU as io waits, to reduce C-state reduction Eric Anholt
2010-11-01 20:23 ` [PATCH 4/4] cpuidle: Hack iowait weighting to avoid C-state reduction for graphics Eric Anholt
2010-11-02 12:20   ` [Intel-gfx] " ykzhao
2010-11-02 15:42     ` Eric Anholt
2010-11-02 20:00       ` [Intel-gfx] " Alexey Fisher
2010-11-02 20:44         ` Chris Wilson
2010-11-01 21:00 ` [RFC] Hack to avoid C-state reduction during graphics activity Andrew Lutomirski
2010-11-01 21:43   ` Eric Anholt

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=1288643024-5706-2-git-send-email-eric@anholt.net \
    --to=eric@anholt.net \
    --cc=intel-gfx@lists.freedesktop.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