User:DanielDrake/X hacking

From OLPC
< User:DanielDrake
Revision as of 11:25, 5 October 2012 by DanielDrake (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

EXA

(thanks to Mart Raudsepp for getting me started with much of the info below)

Core reading list

Measure

To find code paths that aren't being accelerated that would potentially be worth accelerating, look at the CheckComposite/PrepareComposite calls in the driver that return FALSE. The geode driver has some optional logging here, skimming the logs will give an idea.

Also, in the xserver EXA code there is a macro which can be enabled to report fallback cases in a driver-independent manner. EXA also has some helper functions which can be used to print details of the operation.

Some CheckComposite/PrepareComposite failures won't directly result in software rendering - sometimes EXA will then break the operation into multiple operations and see if the driver can accelerate those.

Other resources