Robert Bragg 2f0c0aa8ae Increases the sample frequency from 100/sec to 10,000/sec
For a typical vsync locked application running at 60fps, sampling at just
under twice a frame doesn't seem to give very stable lists of relevent hardware
units because there are a number of units involved that may not be sampled one
second to the next.

This bumps the sample rate to 10,000 instead which is ~ 170 samples per
frame so we tend to hit all the units involved.

It also changes the report threshold to a sample count >= 1, so you don't
see as many units with a percentage of 0.

Signed-off-by: Eric Anholt <eric@anholt.net>
2009-06-09 11:31:24 -07:00
2009-05-14 14:39:48 -07:00
2009-05-19 15:53:55 -07:00
2009-03-27 16:03:02 -07:00

This is a collection of tools for development and testing of the Intel DRM
driver.  There are many macro-level test suites that get used against our
driver, including xtest, rendercheck, piglit, and oglconform, but failures
from those can be difficult to track down to kernel changes, and many require
complicated build procedures or specific testing environments to get useful
results.

Thus, intel-graphics-tools was a project I started to collect some low-level
tools I intended to build.  There are 3 subdirectories:

benchmarks/
	This should be a collection of useful microbenchmarks.  The hope is
	that people can use these to tune some pieces of DRM code in relevant
	ways.

	The benchmarks require KMS to be enabled.  When run with an X Server
	running, they must be run as root to avoid the authentication
	requirement.

tests/
	This is a set of automated tests to run against the DRM to validate
	changes.  Hopefully this can cover the relevant cases we need to
	worry about, including backwards compatibility.

	To run the tests, do "sudo make check" from this directory with
	KMS enabled.

tools/
	This is a collection of debugging tools that had previously been
	built with the 2D driver but not shipped.  Some distros were hacking
	up the 2D build to ship them.  Instead, here's a separate package for
	people debugging the driver.

	These tools generally must be run as root.
Description
No description provided
Readme 18 MiB
Languages
C 95.5%
Yacc 2.5%
Makefile 0.5%
Shell 0.5%
Lex 0.3%
Other 0.6%