From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0595965708==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id C9E156E2FC for ; Wed, 22 Nov 2017 10:40:11 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0595965708== Content-Type: multipart/alternative; boundary="15113472111.C024921a.26459"; charset="UTF-8" --15113472111.C024921a.26459 Date: Wed, 22 Nov 2017 10:40:11 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D103100 Michel D=C3=A4nzer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ckoenig.leichtzumerken@gmai | |l.com --- Comment #4 from Michel D=C3=A4nzer --- 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 does= n'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)? --=20 You are receiving this mail because: You are the assignee for the bug.= --15113472111.C024921a.26459 Date: Wed, 22 Nov 2017 10:40:11 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated = Michel D=C3=A4nzer changed bug 10310= 0
What Removed Added
CC   ckoenig.leichtzumerken@gmail.com

Commen= t # 4 on bug 10310= 0 from Michel D=C3=A4nzer 
One possible issue with per-VM BOs is that the kernel driver c=
an no longer
migrate BOs to more optimal placement for a command stream, because it does=
n'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.
= --15113472111.C024921a.26459-- --===============0595965708== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0595965708==--