public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	"Sun, Yi" <yi.sun@intel.com>
Subject: Re: Updated -next
Date: Mon, 9 Apr 2012 18:19:35 +0200	[thread overview]
Message-ID: <20120409161935.GB4813@phenom.ffwll.local> (raw)
In-Reply-To: <20120405094529.GB4291@phenom.ffwll.local>

On Thu, Apr 05, 2012 at 11:45:29AM +0200, Daniel Vetter wrote:
> Hi all,
> 
> I've pushed out a new -next and testing tree. Highlights:
> - first batch of hsw enabling (Eugeni)
> - first batch of vlv enabling (Jesse and others)
> - a few cleanups spurred by the above items
> - pwrite/pread rework and speedups
> - less mappable pressure and reloc optimizations (Chris)
> - mmap_offset exhaustion mitigation (Chris)
> - more gmbus cleanups and fixes (Daniel Kurtz), now also enabled for gen2
> - a start at figuring out what code of our gem+ums/kms/dri1 codebase is
>   actually support by disallowing these ioctls
> 
> Happy testing!

Ben Widawsky noticed that one of the patches I've merged accidentally
disabled rc6 and gpu turbo on snb and ivb, essentially making any gpu
render and performance testing void.

My apologies for this screw-up, I should have done better. Especially
since I've noticed the error in review, but managed to merge the patch
despite that.

I've updated the drm-intel-next and -testing branchs, the new tip of
-testing is:

commit 9d0b5b5468650e0ac72a7786cf6625963f926d4d
Merge: ec34a01 b4db1e3
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Mon Apr 9 18:12:03 2012 +0200

    Merge remote-tracking branch 'danvet/drm-intel-fixes' into
    drm-intel-testing'

Sun, I'm sorry for the additional work, but please re-run any gpu render
and performance testing on this new branch. Modeset issues and output
testing should not be affected by this, so there's no need to re-run these
tests you have already done on the old -testing branch.

Yours, Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-04-09 16:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  9:45 Updated -next Daniel Vetter
2012-04-09 16:19 ` Daniel Vetter [this message]
2012-04-10  2:09   ` Sun, Yi
2012-04-11  3:20 ` Sun, Yi
2012-04-11  7:54   ` Paul Menzel
2012-04-11  8:24     ` Sun, Yi
2012-04-11  9:45       ` Paul Menzel
  -- strict thread matches above, loose matches on Subject: below --
2012-07-22 14:33 updated -next Daniel Vetter
2012-06-21  8:25 Updated -next Daniel Vetter
2012-06-04 20:59 Daniel Vetter
2012-06-12  8:37 ` Daniel Vetter
2012-05-06 19:09 Daniel Vetter
2012-04-21 16:40 Daniel Vetter
2012-04-23  7:39 ` Daniel Vetter
2012-04-23  7:40   ` Sun, Yi
2012-04-27 11:45 ` Daniel Vetter
2012-04-27 13:44   ` Daniel Vetter
2012-03-23 10:03 Daniel Vetter
2012-03-29  7:38 ` Sun, Yi
2012-03-01 20:59 Daniel Vetter
2012-03-08  8:10 ` Sun, Yi
2012-03-18 21:20   ` Daniel Vetter
2012-02-16 17:27 updated -next Daniel Vetter
2012-02-17 17:56 ` Jesse Barnes
2012-02-21  7:45 ` Sun, Yi
2012-02-07 22:59 Daniel Vetter
2012-01-20 10:10 Updated -next Daniel Vetter
2012-01-21  4:15 ` Sun, Yi
2012-01-21 14:12   ` Daniel Vetter
2012-01-21 19:45     ` Alan W. Irwin
2012-01-31  9:07       ` Jin, Gordon

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=20120409161935.GB4813@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=yi.sun@intel.com \
    /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