Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "daniel@ffwll.ch" <daniel@ffwll.ch>,
	"Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH CI 1/2] drm/i915/display/skl+: Drop frontbuffer rendering support
Date: Thu, 9 Sep 2021 23:28:25 +0300	[thread overview]
Message-ID: <YTpuaUI6rpPzHDFS@intel.com> (raw)
In-Reply-To: <32357a14fd9926ac5c332868e3aadfbb8105caf9.camel@intel.com>

On Thu, Sep 09, 2021 at 08:23:20PM +0000, Souza, Jose wrote:
> On Thu, 2021-09-09 at 23:20 +0300, Ville Syrjälä wrote:
> > On Thu, Sep 09, 2021 at 12:49:16PM -0700, José Roberto de Souza wrote:
> > > By now all the userspace applications should have migrated to atomic
> > > or at least be calling DRM_IOCTL_MODE_DIRTYFB.
> > > 
> > > With that we can kill frontbuffer rendering support in i915 for
> > > modern platforms.
> > > 
> > > So here converting legacy APIs into atomic commits so it can be
> > > properly handled by driver i915.
> > > 
> > > Several IGT tests will fail with this changes, because some tests
> > > were stressing those frontbuffer rendering scenarios that no userspace
> > > should be using by now, fixes to IGT should be sent soon.
> > > 
> > 
> > I just gave this a try here and it's unusable. glxgears went from
> > 9000 to 120 fps (was expecting 60fps tbh, not sure why I get
> > double), everything lags like mad, if I drag a window around
> > glxgears/other windows stop updating entirely, etc. NAK
> 
> Can you share your setup? What GPU? Desktop environment? Mesa version? resolutions of sinks?
> Will try it in my end.

Doesn't really matter as long as you don't have a compositor making a
mess of things. This machine is a cfl running mate w/ compositor off,
and some 1920x1200 display.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2021-09-09 20:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 19:49 [Intel-gfx] [PATCH CI 1/2] drm/i915/display/skl+: Drop frontbuffer rendering support José Roberto de Souza
2021-09-09 19:49 ` [Intel-gfx] [PATCH CI 2/2] drm/i915/display: Drop PSR " José Roberto de Souza
2021-09-09 20:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/2] drm/i915/display/skl+: Drop " Patchwork
2021-09-09 20:20 ` [Intel-gfx] [PATCH CI 1/2] " Ville Syrjälä
2021-09-09 20:23   ` Souza, Jose
2021-09-09 20:28     ` Ville Syrjälä [this message]
2021-09-13 22:54       ` Souza, Jose
2021-09-15 13:48         ` Ville Syrjälä
2021-09-15 15:57           ` Ville Syrjälä
2021-09-15 16:49             ` Ville Syrjälä
2021-09-15 20:05               ` Souza, Jose
2021-09-15 19:50           ` Souza, Jose
2021-09-09 20:33 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [CI,1/2] " Patchwork
2021-09-14  0:17 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [CI,1/2] drm/i915/display/skl+: Drop frontbuffer rendering support (rev2) Patchwork

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=YTpuaUI6rpPzHDFS@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=gwan-gyeong.mun@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=jose.souza@intel.com \
    --cc=rodrigo.vivi@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