From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Daniel Wagner <daniel.wagner@oss.bmw-carit.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [RFC v0] thermal: Protect schedule flag by raw spin
Date: Wed, 14 May 2014 12:23:42 +0200 [thread overview]
Message-ID: <20140514102342.GH15049@linutronix.de> (raw)
In-Reply-To: <53707BA0.60701@oss.bmw-carit.de>
* Daniel Wagner | 2014-05-12 09:43:28 [+0200]:
>Hi Sebastian,
Hi Daniel,
>I overlooked that one. I tried to avoid using thread for this but it
>looks like there isn't a simpler way. I'll do 'x86/mce' version then.
as an exercise you could come up with a generic infrastructure which
fires up one task and can be re-used by mce and the old other users
which attempt schedule a workqueue in hard irq context. I think a simple
swait based workqueue like thingy should work.
Sebastian
next prev parent reply other threads:[~2014-05-14 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 14:22 [RFC v0] thermal: Protect schedule flag by raw spin Daniel Wagner
2014-05-09 12:09 ` Sebastian Andrzej Siewior
2014-05-12 7:43 ` Daniel Wagner
2014-05-14 10:23 ` Sebastian Andrzej Siewior [this message]
2014-05-14 13:36 ` Daniel Wagner
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=20140514102342.GH15049@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=daniel.wagner@oss.bmw-carit.de \
--cc=linux-rt-users@vger.kernel.org \
/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).