From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 82050] R9270X pyrit benchmark perf regressions with latest kernel/llvm Date: Wed, 27 Aug 2014 08:45:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1098036676==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 404456E221 for ; Wed, 27 Aug 2014 01:45:44 -0700 (PDT) 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 --===============1098036676== Content-Type: multipart/alternative; boundary="1409129144.bCEBaA1.29727"; charset="us-ascii" --1409129144.bCEBaA1.29727 Date: Wed, 27 Aug 2014 08:45:44 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D82050 --- Comment #25 from Michel D=C3=A4nzer --- (In reply to comment #24) > Just a general note: We need to define that flag negated for compatibility > reasons. E.g. RADEON_GEM_NO_CPU_ACCESS because code must assume with an o= ld > client that the buffer is always CPU accessed. No, CPU access works fine even with old clients which don't set the flag. The flag is just an optimization, preventing BOs which are expected to be accessed by the CPU from being stored in the CPU-inaccessible part of VRAM. --=20 You are receiving this mail because: You are the assignee for the bug. --1409129144.bCEBaA1.29727 Date: Wed, 27 Aug 2014 08:45:44 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 25 on bug 82050<= /a> from Michel D=C3=A4nzer 
(In reply to comment #=
24)
> Just a general note: We need to define that flag=
 negated for compatibility
> reasons. E.g. RADEON_GEM_NO_CPU_ACCESS because code must assume with a=
n old
> client that the buffer is always CPU accessed.

No, CPU access works fine even with old clients which don't set the flag.

The flag is just an optimization, preventing BOs which are expected to be
accessed by the CPU from being stored in the CPU-inaccessible part of VRAM.=

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1409129144.bCEBaA1.29727-- --===============1098036676== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1098036676==--