All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97988] [radeonsi] playing back videos with VDPAU exhibits deinterlacing/anti-aliasing issues not visible with VA-API
Date: Tue, 04 Oct 2016 12:27:15 +0000	[thread overview]
Message-ID: <bug-97988-502-voCjzrKAAw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97988-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1031 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=97988

--- Comment #14 from Christian König <deathsimple@vodafone.de> ---
(In reply to Marek Olšák from comment #13)
> (In reply to Tom Stellard from comment #12)
> > 
> > I think the best solution here would be to teach the backend how to do a
> > scalar select based on value of vccz.
> 
> You are missing the point. The condition code (VCC) isn't the same across
> all threads. The problem is that the conditional assignment is transformed
> into a form that makes descriptor load addresses non-uniform (dependent on a
> VGPR). There is nothing the AMDGPU backend can do about it. It's not a
> problem in the backend.

Well the backend could iterate over all the variants to handle that, but I have
strong doubts that this would result in optimal performance.

So I think the best solution for now would be to mark the texture intrinsic in
a way which disallows such optimizations.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2088 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-10-04 12:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 14:35 [Bug 97988] [radeonsi] playing back videos with VDPAU exhibits deinterlacing/anti-aliasing issues not visible with VA-API bugzilla-daemon
2016-09-30 14:36 ` bugzilla-daemon
2016-09-30 14:37 ` bugzilla-daemon
2016-09-30 14:43 ` bugzilla-daemon
2016-09-30 14:44 ` bugzilla-daemon
2016-09-30 17:48 ` bugzilla-daemon
2016-09-30 18:55 ` bugzilla-daemon
2016-09-30 20:48 ` bugzilla-daemon
2016-09-30 22:58 ` bugzilla-daemon
2016-09-30 23:34 ` bugzilla-daemon
2016-10-01 14:38 ` bugzilla-daemon
2016-10-01 18:41 ` bugzilla-daemon
2016-10-03 17:29 ` bugzilla-daemon
2016-10-03 17:55 ` bugzilla-daemon
2016-10-04 12:27 ` bugzilla-daemon [this message]
2016-10-04 15:40 ` bugzilla-daemon
2016-10-04 16:01 ` bugzilla-daemon
2016-10-25  9:46 ` bugzilla-daemon
2016-10-25 10:19 ` bugzilla-daemon
2016-10-25 12:46 ` bugzilla-daemon
2016-11-07 11:10 ` bugzilla-daemon
2016-11-07 11:38 ` bugzilla-daemon
2016-11-07 13:40 ` bugzilla-daemon
2016-11-07 14:20 ` bugzilla-daemon
2016-11-07 14:58 ` bugzilla-daemon
2016-11-07 15:09 ` bugzilla-daemon
2016-11-11 21:17 ` bugzilla-daemon
2017-02-06 12:35 ` bugzilla-daemon
2017-02-06 13:01 ` bugzilla-daemon
2017-03-05 20:09 ` bugzilla-daemon
2017-03-15 13:33 ` bugzilla-daemon

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=bug-97988-502-voCjzrKAAw@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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 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.