From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC][PATCH 1/1] drm/i915: Rewrite ILK+ watermark handling
Date: Fri, 10 May 2013 10:14:18 +0300 [thread overview]
Message-ID: <20130510071418.GT14974@intel.com> (raw)
In-Reply-To: <20130509120930.49a7ba41@jbarnes-desktop>
On Thu, May 09, 2013 at 12:09:30PM -0700, Jesse Barnes wrote:
> On Mon, 6 May 2013 16:45:52 +0300
> ville.syrjala@linux.intel.com wrote:
>
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Rewrite the ILK+ watermark code to allow:
> > - updating the watermarks safely (to avoid underruns)
> > - pre-computing watermarks (will help with atomic modest and pageflip)
> > - enabling LP1+ watermarks for HSW multi-pipe scenarios
>
> This looks like the right way to go long term. But Paulo's patches for
> HSW are fairly small and make things better immediately, so we should
> probably get them in first.
Agreed. I'll try to review them properly soon, so far I just glanced at
them.
> This one needs to be split up somehow so we can review it better like
> you mention in the TODO.
>
> Another thing that I used when doing the WM code way back when was to
> port it to userspace and run through various configs to make sure the
> values were all sane. Might be nice if we could do that easily
> somehow, maybe with an #ifdef or putting all the wm stuff into a
> separate file.
Actually I had this stuff running in user space first :)
It's not that hard to implement the required stubs to get some drm
file to compile in userland. I did it already for drm_edid.c (stuff
that I've neglected to publish anywhere). I've not tried it for i915
code, and I suppose it may be a bit more work. Splitting the watermark
stuff into a separate file could help a bit though.
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2013-05-10 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 13:45 [RFC][PATCH 0/1] drm/i915: Big watermark changes ville.syrjala
2013-05-06 13:45 ` [RFC][PATCH 1/1] drm/i915: Rewrite ILK+ watermark handling ville.syrjala
2013-05-07 19:55 ` Paulo Zanoni
2013-05-09 19:09 ` Jesse Barnes
2013-05-10 7:14 ` 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=20130510071418.GT14974@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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