From: Lukasz <el.es.cr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [OT] Re: [PATCH 00/15] GMA500 KMS and GEM
Date: Wed, 8 Jun 2011 11:15:25 +0000 (UTC) [thread overview]
Message-ID: <loom.20110608T130453-800@post.gmane.org> (raw)
In-Reply-To: 20110608100411.9478.86672.stgit@localhost.localdomain
Alan Cox <alan <at> lxorguk.ukuu.org.uk> writes:
> Vblank support is also possible but doesn't seem terribly useful.
Sorry for being gross off-topic.
But I see the vblank (the feature that lets the (whatever space) programs
know when the vertical return occurs ?) as a quite useful thing...
Because then the rendering rate is (supposed to be) limited to whatever
the monitor supports (say 60Hz, 1 frame every 15ms) it may be useful as a
comparision how much _free_ cpu time is left when the program
is ready for another frame, that including any (e.g. AI, engine or) system
tasks running (e.g. network communications, debugger)
IMvhO it so would be useful for tracing/profiling these apps, without
stress-testing and give you reproductible results for the performance
of your graphic engine... because there is plenty of time left
for everything else and it does not step on each others toes or turning
your machine into a (blow)heater :)
Just my thoughts.
L.
next prev parent reply other threads:[~2011-06-08 11:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 10:10 [PATCH 00/15] GMA500 KMS and GEM Alan Cox
2011-06-08 10:11 ` [PATCH 01/15] gma500: fix warnings Alan Cox
2011-06-08 10:11 ` [PATCH 02/15] gma500: Skip bogus LVDS VBT mode and check for LVDS before adding backlight Alan Cox
2011-06-08 10:11 ` [PATCH 03/15] gma500: Make GTT pages uncached Alan Cox
2011-06-08 10:12 ` [PATCH 04/15] gma500: Ensure the frame buffer has a linear virtual mapping Alan Cox
2011-06-08 10:12 ` [PATCH 05/15] gma500: Set the correct bits according to the pipe Alan Cox
2011-06-08 10:12 ` [PATCH 06/15] staging/gma500: get control from firmware framebuffer if conflicts Alan Cox
2011-06-08 10:13 ` [PATCH 07/15] gma500: Fix uninitialized variable and style issues Alan Cox
2011-06-08 10:13 ` [PATCH 08/15] gma500: revamp frame buffer creation and handling Alan Cox
2011-06-08 10:13 ` [PATCH 09/15] gma500: Do sane FB cleanup Alan Cox
2011-06-08 10:14 ` [PATCH 10/15] gma500: trim some of the debug Alan Cox
2011-06-08 10:14 ` [PATCH 11/15] gma500: polish for completion of this phase Alan Cox
2011-06-08 10:14 ` [PATCH 12/15] gma500: 2D acceleration tidying Alan Cox
2011-06-08 10:15 ` [PATCH 13/15] gma500: nuke the last bits of TTM code Alan Cox
2011-06-08 10:15 ` [PATCH 14/15] gma500: nuke the PSB debug stuff Alan Cox
2011-06-09 1:10 ` Patrik Jakobsson
2011-06-09 8:11 ` Alan Cox
2011-06-09 10:36 ` Dave Airlie
2011-06-09 11:45 ` Patrik Jakobsson
2011-06-09 12:04 ` Alan Cox
2011-06-12 19:02 ` Daniel Vetter
2011-06-13 15:44 ` Alan Cox
2011-06-13 19:35 ` Daniel Vetter
2011-06-09 11:55 ` Alan Cox
2011-06-08 10:15 ` [PATCH 15/15] gma500: Kill spare kref Alan Cox
2011-06-08 11:15 ` Lukasz [this message]
2011-06-08 12:24 ` [OT] Re: [PATCH 00/15] GMA500 KMS and GEM Alan Cox
2011-06-14 9:24 ` Pasi Kärkkäinen
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=loom.20110608T130453-800@post.gmane.org \
--to=el.es.cr@gmail.com \
--cc=linux-kernel@vger.kernel.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