From: Florian Mickler <florian@mickler.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: markgross@thegnar.org, Frederic Weisbecker <fweisbec@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linville@tuxdriver.com, linux-kernel@vger.kernel.org,
pm list <linux-pm@lists.linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v4] pm_qos: make update_request non blocking
Date: Mon, 14 Jun 2010 17:20:57 +0200 [thread overview]
Message-ID: <20100614172057.778a49d0__33346.0294911221$1276528985$gmane$org@schatten.dmk.lab> (raw)
In-Reply-To: <1276528206.5374.24.camel@mulgrave.site>
On Mon, 14 Jun 2010 10:10:06 -0500
James Bottomley <James.Bottomley@suse.de> wrote:
> On closer inspection, it looks like the
> notifier mutexes are sufficient to make sure it doesn't return running
> the notifier to be removed ... but that does mean that add and remove
> require user context.
>
> James
>
Yes. I don't think we need to make the add and remove callable from
interrupt context?
Cheers,
Flo
next prev parent reply other threads:[~2010-06-14 15:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 15:29 [PATCH v4] pm_qos: make update_request non blocking florian
2010-06-09 15:37 ` James Bottomley
2010-06-09 15:37 ` James Bottomley
2010-06-09 16:00 ` Florian Mickler
2010-06-09 16:00 ` Florian Mickler
2010-06-09 16:07 ` James Bottomley
2010-06-09 16:07 ` James Bottomley
2010-06-09 16:32 ` Florian Mickler
2010-06-09 17:05 ` James Bottomley
2010-06-09 17:05 ` James Bottomley
2010-06-09 17:31 ` Florian Mickler
2010-06-09 17:31 ` Florian Mickler
2010-06-10 7:45 ` Florian Mickler
2010-06-10 13:39 ` James Bottomley
2010-06-10 13:39 ` [linux-pm] " James Bottomley
2010-06-10 14:41 ` Florian Mickler
2010-06-11 14:25 ` James Bottomley
2010-06-11 14:25 ` [linux-pm] " James Bottomley
2010-06-11 15:49 ` Florian Mickler
2010-06-11 15:49 ` [linux-pm] " Florian Mickler
2010-06-14 14:33 ` Florian Mickler
2010-06-14 14:33 ` [linux-pm] " Florian Mickler
2010-06-14 14:44 ` James Bottomley
2010-06-14 14:44 ` [linux-pm] " James Bottomley
2010-06-14 14:49 ` Florian Mickler
2010-06-14 14:49 ` [linux-pm] " Florian Mickler
2010-06-14 15:10 ` James Bottomley
2010-06-14 15:20 ` Florian Mickler [this message]
2010-06-14 15:20 ` Florian Mickler
2010-06-14 15:10 ` James Bottomley
2010-06-14 14:46 ` [PATCH 1/3] " florian
2010-06-14 14:46 ` [PATCH 2/3] pm_qos: add atomic notifier chain florian
2010-06-14 14:46 ` [PATCH 3/3] pm_qos: only schedule work when in interrupt context florian
2010-06-15 17:23 ` Florian Mickler
2010-06-15 17:23 ` Florian Mickler
2010-06-17 23:02 ` James Bottomley
2010-06-17 23:02 ` James Bottomley
2010-06-10 14:41 ` [PATCH v4] pm_qos: make update_request non blocking Florian Mickler
2010-06-10 7:45 ` Florian Mickler
2010-06-09 16:32 ` Florian Mickler
2010-06-09 15:29 florian
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='20100614172057.778a49d0__33346.0294911221$1276528985$gmane$org@schatten.dmk.lab' \
--to=florian@mickler.org \
--cc=James.Bottomley@suse.de \
--cc=corbet@lwn.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linville@tuxdriver.com \
--cc=markgross@thegnar.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.