From: Eric Anholt <eric@anholt.net>
To: Andrew Lutomirski <luto@mit.edu>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] Hack to avoid C-state reduction during graphics activity.
Date: Mon, 01 Nov 2010 14:43:36 -0700 [thread overview]
Message-ID: <871v741zzr.fsf@pollan.anholt.net> (raw)
In-Reply-To: <AANLkTikAHsT3Jhr+pMnRR+2Vg7kvHEYEf=io1YPHq1oY@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 375 bytes --]
On Mon, 1 Nov 2010 17:00:46 -0400, Andrew Lutomirski <luto@mit.edu> wrote:
> Out of curiousity, what happened to ACPI_BM_BREAK_EN here:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=30364
>
> On my box, that register is (according to setpci) 0x00, but I'm
> testing on an ICH9M and I don't seem to be affected anyway.
Those registers aren't there on Ironlake.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2010-11-01 21:43 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 ` [PATCH 1/4] sched: Export io_schedule_timeout() Eric Anholt
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 [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=871v741zzr.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=luto@mit.edu \
/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