From: Alexey Fisher <bug-track@fisher-privat.net>
To: intel-gfx@lists.freedesktop.org
Subject: [regression] drm/i915/execbuffer: Reorder binding of objects to favour restrictions
Date: Fri, 14 Jan 2011 16:11:07 +0100 [thread overview]
Message-ID: <1295017867.5920.7.camel@zwerg> (raw)
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Hi Chris,
i have new regression after this patch. Like usual, artifakts,
disappearing icons, with only one difference gl seems to work ok.
see screencast in attachment.
My HW:
board Intel DG45ID, graphic:
Vendor: 0x8086, Device: 0x2e22, Revision: 0x03 (A3)
xserver-xorg-video-intel
2:2.14.0+git20110110.fd9235eb-0ubuntu0sarvatt~maverick
xserver-xorg
1:7.5+6+xserver1.9
commit 6fe4f14044f181e146cdc15485428f95fa541ce8
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Mon Jan 10 17:35:37 2011 +0000
drm/i915/execbuffer: Reorder binding of objects to favour restrictions
As the mappable portion of the aperture is always a small subset at the
start of the GTT, it is allocated preferentially by drm_mm. This is
useful in case we ever need to map an object later. However, if you have
a large object that can consume the entire mappable region of the
GTT this prevents the batchbuffer from fitting and so causing an error.
Instead allocate all those that require a mapping up front in order to
improve the likelihood of finding sufficient space to bind them.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
--
Regards,
Alexey
[-- Attachment #2: bild-1.ogv --]
[-- Type: video/ogg, Size: 1705930 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2011-01-14 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 15:11 Alexey Fisher [this message]
2011-01-16 14:38 ` [regression] drm/i915/execbuffer: Reorder binding of objects to favour restrictions Alexey Fisher
2011-01-16 14:53 ` Chris Wilson
2011-01-16 14:55 ` Alexey Fisher
2011-01-16 15:02 ` Chris Wilson
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=1295017867.5920.7.camel@zwerg \
--to=bug-track@fisher-privat.net \
--cc=intel-gfx@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