From: Chris Wilson <chris@chris-wilson.co.uk>
To: zhigang.gong@gmail.com
Cc: intel-gfx@lists.freedesktop.org, glamor@lists.freedesktop.org
Subject: Re: [PATCH v2] uxa/glamor: Create glamor pixmap by default.
Date: Tue, 10 Jan 2012 18:00:32 +0000 [thread overview]
Message-ID: <e0d58a$2s54ne@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1326247269-14332-1-git-send-email-zhigang.gong@linux.intel.com>
On Wed, 11 Jan 2012 10:01:09 +0800, zhigang.gong@gmail.com wrote:
> From: Zhigang Gong <zhigang.gong@linux.intel.com>
>
> A minor fix, after convert the old pixmap to the textured-drm pixmap,
> we need to modify the old pixmap's header to make sure the width/height
> and stride are the same as the new textured-drm BO.
We can not just call FatalError there, but should just propagate the error
so that the client at least sees BadMatch and X doesn't simply die... How
does this resolve the issue of mesa replacing a bo for a glamor pixmap
even though we've exported it? Or is that simply an orthogonal problem
to be tackled later?
> ---
> As create glamor pixmap by default will get much better performance
> by using the textured-drm pixmap, this commit is to make that the
> default behaviour when configure to use glamor.
>
> A side effect is that for those glamor pixmaps, they don't have a
> valid BO attached to it and thus it fails to get a DRI drawable. This
> commit also fixes that problem by copy the fixup_shadow mechanism. I
> tested this with mutter, and it seems work fine.
>
> The performance gain to apply this patch is about 20% to 40% with
> different workload.
Waiting to see if I get any results to support that claim... ;-)
You can also mention that by using glamor to allocate the pixmaps, we
reduce the risk of encountering the "incompatible region exists for this name"
and the associated render corruption. Until that is resolved, every time
we export a DRI pixmap and create a BO we still may trigger that bug.
However, since we now never intentionally allocate a reusable pixmap we
could just make all (intel_glamor) allocations non-reusable without
incurring too great an overhead.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-10 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 2:01 [PATCH v2] uxa/glamor: Create glamor pixmap by default zhigang.gong
2012-01-10 18:00 ` Chris Wilson [this message]
2012-01-11 8:59 ` [Glamor] " Zhigang Gong
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='e0d58a$2s54ne@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=glamor@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=zhigang.gong@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.