From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1
Date: Wed, 18 May 2016 21:13:05 +0000 [thread overview]
Message-ID: <bug-95474-502-B9pdQ4rAbn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95474-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3069 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95474
--- Comment #5 from Jan Ziak <0xe2.0x9a.0x9b@gmail.com> ---
(In reply to Alex Deucher from comment #2)
> Can you identify what component caused the regression? mesa? llvm? kernel?
Output from "perf report":
# Samples: 660K of event 'cycles'
# Event count (approx.): 568704142352
#
# Overhead Command Shared Object Symbol
9.94% G.26 radeonsi_dri.so [.] pb_cache_is_buffer_compat
2.51% G.26 libgcc_s.so.1 [.] __umoddi3
1.66% G.26 libc-2.22.so [.] _int_malloc
1.52% G.26 libc-2.22.so [.] _int_free
1.42% G.26 radeonsi_dri.so [.] radeon_drm_cs_add_buffer
1.22% bioshock.i386 radeonsi_dri.so [.] radeon_cs_context_cleanup
1.14% bioshock.i386 [kernel.vmlinux] [k]
reservation_object_add_shared_fence
1.02% G.26 libc-2.22.so [.] __libc_calloc
0.93% G.26 libpthread-2.22.so [.] pthread_mutex_lock
0.81% bioshock.i386 [kernel.vmlinux] [k] __ww_mutex_lock_interruptible
0.79% G.26 bioshock.i386 [.] 0x00000000001a8853
0.79% G.26 radeonsi_dri.so [.] pb_cache_reclaim_buffer
0.78% G.26 libpthread-2.22.so [.]
__pthread_mutex_unlock_usercnt
0.74% G.26 libc-2.22.so [.] malloc
0.72% bioshock.i386 radeonsi_dri.so [.]
radeon_drm_cs_emit_ioctl_oneshot
0.66% bioshock.i386 [radeon] [k] radeon_bo_list_validate
0.60% G.26 radeonsi_dri.so [.] __x86.get_pc_thunk.bx
0.56% G.26 bioshock.i386 [.] 0x00000000001a8e53
0.56% G.26 radeonsi_dri.so [.] set_add
0.55% G.26 radeonsi_dri.so [.] ir_expression::accept
0.54% bioshock.i386 [ttm] [k] ttm_bo_list_ref_sub
0.54% G.26 radeonsi_dri.so [.] _mesa_glsl_parse
0.53% G.26 radeonsi_dri.so [.] radeon_lookup_buffer
0.52% G.26 libc-2.22.so [.] __memcmp_sse4_2
0.48% G.26 radeonsi_dri.so [.] visit_list_elements
0.47% bioshock.i386 [kernel.vmlinux] [k]
reservation_object_reserve_shared
0.46% G.26 radeonsi_dri.so [.] si_reset_buffer_resources
0.45% G.26 radeonsi_dri.so [.] hash_table_search
0.45% bioshock.i386 [drm] [k] drm_gem_object_lookup
0.42% G.26 libc-2.22.so [.] malloc_consolidate
0.41% bioshock.i386 [radeon] [k] radeon_sync_fence
0.41% G.26 radeonsi_dri.so [.] set_search
0.40% G.26 radeonsi_dri.so [.]
u_default_transfer_inline_write
0.40% bioshock.i386 [ttm] [k] ttm_bo_add_to_lru
0.38% G.26 radeonsi_dri.so [.] st_validate_state
0.36% bioshock.i386 [ttm] [k] ttm_bo_del_from_lru
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4001 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:[~2016-05-18 21:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 19:19 [Bug 95474] Bioshock Infinite and DiRT Showdown perform very poor on any GPU with GCN >=1.1 bugzilla-daemon
2016-05-18 19:22 ` [Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly " bugzilla-daemon
2016-05-18 19:26 ` bugzilla-daemon
2016-05-18 19:39 ` bugzilla-daemon
2016-05-18 21:09 ` bugzilla-daemon
2016-05-18 21:12 ` bugzilla-daemon
2016-05-18 21:13 ` bugzilla-daemon [this message]
2016-05-18 21:14 ` bugzilla-daemon
2016-05-19 17:36 ` bugzilla-daemon
2016-05-20 13:22 ` bugzilla-daemon
2016-05-24 20:21 ` bugzilla-daemon
2016-05-24 21:06 ` bugzilla-daemon
2016-05-24 21:24 ` bugzilla-daemon
2016-05-25 12:09 ` bugzilla-daemon
2016-05-25 14:14 ` bugzilla-daemon
2016-08-01 17:33 ` bugzilla-daemon
2016-08-14 21:27 ` 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-95474-502-B9pdQ4rAbn@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