From: Johannes Engel <jcnengel@googlemail.com>
To: "Thomas Hellström" <thomas@tungstengraphics.com>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1 repost #1] DRM: don't enable irqs in locking
Date: Tue, 12 Aug 2008 14:22:51 +0100 [thread overview]
Message-ID: <48A18EAB.40808@googlemail.com> (raw)
In-Reply-To: <488E2CED.1040207@tungstengraphics.com>
Thomas Hellström wrote:
> Yes, this bug could occur, but the remedy is not to use
> spin_lock_irqsave() for lock_data::spinlock but to avoid calling
> drm_lock_take with the drm_device::tasklet_lock held with irqs disabled.
> I'll see if I can come up with a patch.
Hi Thomas,
any news on that so far?
Cheers, Johannes
next prev parent reply other threads:[~2008-08-12 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 8:42 [PATCH 1/1 repost #1] DRM: don't enable irqs in locking Jiri Slaby
2008-07-25 8:54 ` Dave Airlie
2008-07-28 20:32 ` Thomas Hellström
2008-07-29 7:31 ` Andrew Morton
2008-07-29 8:16 ` Dave Airlie
2008-08-12 13:22 ` Johannes Engel [this message]
2008-08-13 8:16 ` Thomas Hellström
2008-08-13 11:08 ` Johannes Engel
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=48A18EAB.40808@googlemail.com \
--to=jcnengel@googlemail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@tungstengraphics.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