From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Liu, Chuansheng" <chuansheng.liu@intel.com>
Cc: "'linux-kernel@vger.kernel.org' (linux-kernel@vger.kernel.org)"
<linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"airlied@redhat.com" <airlied@redhat.com>,
"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
"Shi, Yang A" <yang.a.shi@intel.com>
Subject: Re: [Patch 0/1]drm_irq: Introducing the irq_thread support
Date: Wed, 5 Sep 2012 13:49:32 +0100 [thread overview]
Message-ID: <20120905134932.00707b98@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <27240C0AC20F114CBF8149A2696CBE4A177306@SHSMSX101.ccr.corp.intel.com>
On Wed, 5 Sep 2012 01:53:44 +0000
"Liu, Chuansheng" <chuansheng.liu@intel.com> wrote:
> This patch is for introducing the irq thread support in drm_irq.
>
> Why we need irq thread in drm_irq code?
> In our GPU system, the gpu interrupt handler need some time even > 1ms to finish,
> in that case, the whole system will stay in irq disable status. One case is:
> when audio is playing, it sometimes effects the audio quality.
This possibly ought to be submitted in parallel with the code that uses it
so that the whole proposal can be evaluated as one thing ?
Alan
next prev parent reply other threads:[~2012-09-05 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 1:53 [Patch 0/1]drm_irq: Introducing the irq_thread support Liu, Chuansheng
2012-09-05 12:49 ` Alan Cox [this message]
2012-09-06 0:42 ` Liu, Chuansheng
2012-09-06 7:39 ` Daniel Vetter
2012-09-05 13:27 ` Daniel Vetter
2012-09-05 15:12 ` Shi, Yang A
2012-09-05 15:32 ` Daniel Vetter
2012-09-06 0:54 ` Liu, Chuansheng
2012-09-05 15:47 ` Rob Clark
2012-09-06 0:48 ` Liu, Chuansheng
2012-10-11 12:07 ` Laurent Pinchart
2012-10-11 13:19 ` Rob Clark
2012-10-11 15:18 ` Daniel Vetter
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=20120905134932.00707b98@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=chuansheng.liu@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yang.a.shi@intel.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;
as well as URLs for NNTP newsgroup(s).