From: Andreas Mohr <andi@lisas.de>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] irq_work changes for 3.9
Date: Wed, 16 Jan 2013 23:04:47 +0100 [thread overview]
Message-ID: <20130116220447.GA20148@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <1358345841-29136-1-git-send-email-fweisbec@gmail.com>
Hi,
> These three patches are general fixes for irq work. The two first
> patches fix tight races on global irq work claiming that prevent the irq work
> subsystem from dropping a work enqueuing attempt because it thinks it's
> already pending while it may be already executing or executed.
Would that one happen to be one that would fix my system dropping
dead on sound output (looping the existing buffer ad infinitum)
every couple idle minutes when using my sound card's
PulseAudio IRQ-less playback patch (to-be-submitted),
and which seems to have started (or got quite a bit worse
so as to let me notice?) once I added my
"quirks: enable APIC De-Assert Message bit for VIA 8235, too."
(to-be-submitted) commit?
(which reduces IRQs from duplicate to single - thereby probably
reducing the opportunities for the system to notice that work is pending)
Of course a lone kick to the mouse always fixes it...
(-rc2 here)
Hell yeah that does sound like a potential candidate to me.
Andreas Mohr
next prev parent reply other threads:[~2013-01-16 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 14:17 Frederic Weisbecker
2013-01-16 22:04 ` Andreas Mohr [this message]
2013-01-16 22:12 ` Frederic Weisbecker
2013-01-16 22:48 ` Andreas Mohr
2013-01-24 11:51 ` Ingo Molnar
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=20130116220447.GA20148@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®