From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103100] Performance regression with various games in drm-next-amd-staging Kernel
Date: Wed, 22 Nov 2017 10:40:11 +0000 [thread overview]
Message-ID: <bug-103100-502-64tdhu91cz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103100-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1037 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103100
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ckoenig.leichtzumerken@gmai
| |l.com
--- Comment #4 from Michel Dänzer <michel@daenzer.net> ---
One possible issue with per-VM BOs is that the kernel driver can no longer
migrate BOs to more optimal placement for a command stream, because it doesn't
know which BOs are used by the command stream. So if e.g. a per-VM BO is
evicted from VRAM, e.g. due to CPU access to it, it will normally never move
back to VRAM.
Christian, might it be possible to e.g. maintain a list of per-VM BOs which
were evicted from VRAM, and try to move them back to VRAM as part of the
existing mechanism for this (for "normal" BOs)?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2396 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
next prev parent reply other threads:[~2017-11-22 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 16:38 [Bug 103100] Image corruptions, instability and performance regression in drm-next-wip Kernel bugzilla-daemon
2017-10-12 6:52 ` bugzilla-daemon
2017-10-15 18:57 ` bugzilla-daemon
2017-11-21 20:35 ` [Bug 103100] Performance regression with various games in drm-next-amd-staging Kernel bugzilla-daemon
2017-11-22 10:40 ` bugzilla-daemon [this message]
2017-11-22 11:42 ` bugzilla-daemon
2017-11-22 11:56 ` bugzilla-daemon
2017-11-22 20:58 ` bugzilla-daemon
2017-11-22 20:59 ` bugzilla-daemon
2017-11-22 21:02 ` bugzilla-daemon
2017-12-02 19:32 ` bugzilla-daemon
2017-12-12 13:02 ` bugzilla-daemon
2017-12-12 19:51 ` 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-103100-502-64tdhu91cz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox