From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: watermark problem in kernel 3.14
Date: Thu, 3 Sep 2015 13:54:25 +0300 [thread overview]
Message-ID: <20150903105425.GS29811@intel.com> (raw)
In-Reply-To: <87mvx40xev.fsf@intel.com>
On Thu, Sep 03, 2015 at 10:33:44AM +0300, Jani Nikula wrote:
> On Thu, 03 Sep 2015, "Xie, William" <william.xie@intel.com> wrote:
> > We suspect watermark has problem in kernel 3.14,
> > Does anyone have a new watermark patch for 3.14 similar as below patch:
> > http://patchwork.freedesktop.org/bundle/anderco/matt-watermarks/
>
> Obviously can't speak for everyone out there, but the educated guess is
> no, nobody is working on watermark code for v3.14. You should try
> upgrading to newer kernels, even if only to see if the problems you're
> experiencing go away.
The only tree with properly done watermark updates was my watermark
branch. Since gitorious has died I suppose my branches have disappeared
too. Fortunately I have it all locally still, so I pushed something to
git://github.com/vsyrjala/linux.git watermarks_intm_33
That looked to be one of the last versions of that code that may
actually have been tested. After that a bunch of skl code landed in the
middle of the wm code and the rebase became very painful, and apparently
I never finished it properly (juddging by what I have in later versions
of the branch).
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-09-03 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 22:31 watermark problem in kernel 3.14 Xie, William
2015-09-03 7:33 ` Jani Nikula
2015-09-03 10:54 ` Ville Syrjälä [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=20150903105425.GS29811@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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