From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 00/12] Broadwell 3.14 backports
Date: Tue, 25 Mar 2014 10:43:54 +0100 [thread overview]
Message-ID: <20140325094354.GO26878@phenom.ffwll.local> (raw)
In-Reply-To: <20140324231741.GC2082@bwidawsk.net>
On Mon, Mar 24, 2014 at 04:17:42PM -0700, Ben Widawsky wrote:
> On Mon, Mar 24, 2014 at 04:14:32PM -0700, Ausmus, James wrote:
> > On Sat, Mar 22, 2014 at 4:34 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > On Fri, Mar 21, 2014 at 05:51:01PM -0700, Ben Widawsky wrote:
> > >> Let's try this again. I've pushed a branch here:
> > >> http://cgit.freedesktop.org/~bwidawsk/drm-intel/log/?h=bdw-backports
> > >>
> > >> I need to re-review some of the merge conflicts for 4g GGTT, which I
> > >> will try to do before Monday.
> > >>
> > >> Daniel: please make sure this is what you had in mind. I don't know
> > >> where you want Cc: stable tags.
> > >
> > > We don't need cc: stable, we just need to submit it (since it has the
> > > upstream sha1s already, which is the requirement for stable patches). Cc:
> > > stable is only for when you want it to get backport anyway. Otherwise
> > > looks good. I dunno whether git cherry-pick can be told to use the sha1
> > > reference layout Greg prefers or not, he uses "This is <sha1> in
> > > upstream." between the commit header and the actual commit message. But
> > > ime his scripts reformat your commit messages anyway.
> > >
> > >> James: please test this as soon as possible.
> > >
> > > Once this is tested and we conclude it's sufficient to get bdw going on
> > > 3.14 without hilarity I think we should do a quick review on intel-gfx to
> > > check that the impact outside of bdw is indeed minimal. Then once drm-next
> > > has landed with all the referenced commits we can submit it to Greg with a
> > > small cover letter why we want this and that plan B would be to kill bdw
> > > in 3.14.
> >
> > This seems to be working well for me, with the one caveat that on boot
> > and once per resume I'm hitting the WARN(!i915_preliminary_hw_support,
> > "GEN8_CENTROID_PIXEL_OPT_DIS not be needed for production") code in
> > gen8_init_clock_gating - can that WARN be dropped via "drm/i915: Don't
> > use i915_preliminary_hw_support to mean pre-production" ?
> >
> > Both with and without that patch added, the series is:
> >
> > Tested-by: James Ausmus <james.ausmus@intel.com>
>
> Thanks.
>
> Daniel, the patch is added to my backports branch. I think given that
> that it removes a WARN which we know to be bogus, it's a good patch for
> stable. But it's your call.
Oh, that patch definitely should go to stable if we fix up bdw in 3.14 ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-03-25 9:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 18:48 [PATCH 00/12] Broadwell 3.14 backports Ben Widawsky
2014-03-21 18:48 ` [PATCH 01/12] drm/i915: Fix forcewake counts for gen8 Ben Widawsky
2014-03-21 18:48 ` [PATCH 02/12] drm/i915: Do forcewake reset on gen8 Ben Widawsky
2014-03-21 18:48 ` [PATCH 03/12] drm/i915: Disable semaphore wait event idle message on BDW Ben Widawsky
2014-03-21 18:48 ` [PATCH 04/12] drm/i915: Implement WaDisableSDEUnitClockGating:bdw Ben Widawsky
2014-03-21 18:48 ` [PATCH 05/12] drm/i915: We implement WaDisableAsyncFlipPerfMode:bdw Ben Widawsky
2014-03-21 18:48 ` [PATCH 06/12] drm/i915: Add a partial instruction shootdown workaround on Broadwell Ben Widawsky
2014-03-21 18:48 ` [PATCH 07/12] drm/i915: Add thread stall DOP clock gating " Ben Widawsky
2014-03-21 18:48 ` [PATCH 08/12] drm/i915/bdw: The TLB invalidation mechanism has been removed from INSTPM Ben Widawsky
2014-03-21 18:48 ` [PATCH 09/12] drm/i915: Don't clobber CHICKEN_PIPESL_1 on BDW Ben Widawsky
2014-03-21 18:48 ` [PATCH 10/12] drm/i915: don't flood the logs about bdw semaphores Ben Widawsky
2014-03-21 22:06 ` [PATCH 10/12] [v2] " Ben Widawsky
2014-03-21 18:48 ` [PATCH 11/12] drm/i915/bdw: Use scratch page table for GEN8 PPGTT Ben Widawsky
2014-03-21 18:48 ` [PATCH 12/12] drm/i915/bdw: Restore PPAT on thaw Ben Widawsky
2014-03-21 19:49 ` [PATCH 00/12] Broadwell 3.14 backports Daniel Vetter
2014-03-21 22:14 ` Ben Widawsky
2014-03-21 23:47 ` Greg KH
2014-03-22 0:06 ` Ben Widawsky
2014-03-22 0:17 ` Ben Widawsky
2014-03-22 11:29 ` Daniel Vetter
2014-03-22 0:51 ` Ben Widawsky
2014-03-22 11:34 ` Daniel Vetter
2014-03-24 23:14 ` Ausmus, James
2014-03-24 23:17 ` Ben Widawsky
2014-03-25 9:43 ` Daniel Vetter [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=20140325094354.GO26878@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.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