[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100527201155.GB7449@srcf.ucam.org>
Date: Thu, 27 May 2010 21:11:56 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Arve Hjønnevåg <arve@...roid.com>,
Florian Mickler <florian@...kler.org>,
Vitaly Wool <vitalywool@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Paul@...p1.linux-foundation.org, felipe.balbi@...ia.com,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Linux PM <linux-pm@...ts.linux-foundation.org>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8)
On Thu, May 27, 2010 at 08:53:33PM +0100, Alan Cox wrote:
> On Thu, 27 May 2010 20:29:26 +0100
> Matthew Garrett <mjg59@...f.ucam.org> wrote:
> > But wakeup events won't be delivered to STOPped processes, and there's
>
> Try the following
>
> cat <pipe
> kill -STOP catpid
>
> echo "wombats are cool" > pipe
> kill -CONT catpid
>
> it will echo "wombats are cool"
>
> The event was not lost.
Not lost, but not delivered. So you need your policy agent to send
SIGCONT when you receive any wakeup event, which either means proxying
all your network traffic through your policy agent or having some
mechanism for alerting the policy agent whenever you leave the deep idle
state.
> > also the race of an application being in the middle of handling a wakeup
> > event when you send it the signal.
>
> sigmask()
Doesn't help - I may be hit by the signal between the poll() unblocking
and me having the opportunity to call sigmask().
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists