From: "Rafał Miłecki" <zajec5@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.sf.net
Subject: Re: [PATCH] [rfc] drm/radeon/kms: pm debugging check for vbl.
Date: Thu, 18 Feb 2010 11:12:33 +0100 [thread overview]
Message-ID: <b170af451002180212p5699dc73ub743e69446c21746@mail.gmail.com> (raw)
In-Reply-To: <21d7e9971002180028u583779aak5d9d86fd9c719527@mail.gmail.com>
W dniu 18 lutego 2010 09:28 użytkownik Dave Airlie <airlied@gmail.com> napisał:
>>
>>> It adds some reading & printing steps before every reclock, while we
>>> really want it to happen as soon as possible. Maybe you could execute
>>> this only on some
>
> btw you won't get the print if you are in vblank, and if you aren't
> well the print
> doesn't matter, I'm also thinking the engine change reads/writes a lot of regs,
> so two more might not matter so much.
Yeah, maybe that's right.
While your idea of testing being in VBLANK is "sane" :) it could
happen we start reclocking in VBLANK (first test will pass), we
reclock out of VBLANK (not wanted, possible corruption), and we hit
next VBLANK in second test.
In such situation (machine) I'm sure we will hit "false" in test
anyway (sooner or later) but maybe we could improve in anyway somehow?
To make sure it's sill the same VBLANK?
--
Rafał
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-02-18 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 6:50 [PATCH] [rfc] drm/radeon/kms: pm debugging check for vbl Dave Airlie
2010-02-18 8:04 ` Rafał Miłecki
2010-02-18 8:16 ` Dave Airlie
2010-02-18 8:28 ` Dave Airlie
2010-02-18 10:12 ` Rafał Miłecki [this message]
2010-02-18 10:29 ` Dave Airlie
2010-02-23 21:38 ` Luca Tettamanti
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=b170af451002180212p5699dc73ub743e69446c21746@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sf.net \
/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.