From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: old radeon latency problem still unfixed?
Date: Mon, 27 Feb 2006 08:11:33 +1100 [thread overview]
Message-ID: <1140988293.3982.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1140982513.24141.118.camel@mindpipe>
> AFAICT it's more like trading 3D performance for having audio work at
> all. Other video drivers that were too aggressive and caused audio
> dropouts (VIA) were fixed, even though there was a slight performance
> cost.
In addition, the radeon DRI shouldn't do active spinning like that in
"normal" circumstances ... it should instead block on interrupts. if it
does, I suppose that could safely be considered as a bug in the radeon
DRM/DRI driver. It will do such loops on engine reset and such, which
happen on X launch, VT switches or in case of lockups... I have to
double check what happens in the code path used for 2d/3d transitions
though, those might be a problem.
Ben.
next prev parent reply other threads:[~2006-02-26 21:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 1:36 old radeon latency problem still unfixed? Lee Revell
2006-02-26 2:33 ` Fernando Lopez-Lezcano
2006-02-26 2:36 ` Lee Revell
2006-02-26 9:13 ` Arjan van de Ven
2006-02-26 19:35 ` Lee Revell
2006-02-26 21:11 ` Benjamin Herrenschmidt [this message]
2006-02-26 21:31 ` Lee Revell
2006-02-26 22:53 ` Benjamin Herrenschmidt
2006-02-26 23:02 ` Lee Revell
2006-02-27 0:18 ` Benjamin Herrenschmidt
2006-02-27 0:32 ` Lee Revell
2006-02-26 9:44 ` Andrew Morton
2006-02-26 9:57 ` Arjan van de Ven
2006-02-26 19:39 ` Lee Revell
2006-02-26 21:31 ` Dave Airlie
2006-02-26 21:35 ` Lee Revell
2006-02-26 22:09 ` Dave Airlie
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=1140988293.3982.8.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox