All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <shawn.starr-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>,
	"Mario Kleiner"
	<mario.kleiner.de-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [AMDGPU][CIK] PRIME with DRI3 + stalls rendering
Date: Mon, 14 Nov 2016 15:40:17 -0500	[thread overview]
Message-ID: <1502264.CaXMU5SOfp@segfault> (raw)
In-Reply-To: <472120da-9ec1-3963-484f-24add93f8eb6-otUistvHUpPR7s880joybQ@public.gmane.org>

On Monday, November 14, 2016 10:40:17 AM EST Michel Dänzer wrote:
> On 13/11/16 06:59 AM, Shawn Starr wrote:
> > I'm currently trying the new fence patches that prevent tearing in PRIME
> > on
> > Bonaire CIK, it works with no tearing with latest patches from Mario, but
> > there is significant frame stalls, even though the performance is higher
> > than running the AMDGPU as dedicated.
> 
> Please elaborate on what "frame stalls" means exactly.

It looks like vsync issues, even though if I try vblank_mode=# it still shows 
stalling.

I'll have to make a video to show the results and post link here.

Thanks,
Shawn



_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2016-11-14 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-12 21:59 [AMDGPU][CIK] PRIME with DRI3 + stalls rendering Shawn Starr
2016-11-14  1:40 ` Michel Dänzer
     [not found]   ` <472120da-9ec1-3963-484f-24add93f8eb6-otUistvHUpPR7s880joybQ@public.gmane.org>
2016-11-14 20:40     ` Shawn Starr [this message]
2016-11-15  8:25       ` Shawn Starr
2016-11-16  0:42         ` Mario Kleiner
     [not found]           ` <3eff28a2-e53c-74b9-4e34-6e7e206f0fc5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-11-16 11:45             ` Mike Lothian

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=1502264.CaXMU5SOfp@segfault \
    --to=shawn.starr-bjeeyj9ojedqt0dzr+alfa@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=mario.kleiner.de-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=michel-otUistvHUpPR7s880joybQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.