Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755888Ab2BLWCa (ORCPT ); Sun, 12 Feb 2012 17:02:30 -0500 Received: from netrider.rowland.org ([192.131.102.5]:60836 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753438Ab2BLWC3 (ORCPT ); Sun, 12 Feb 2012 17:02:29 -0500 Date: Sun, 12 Feb 2012 17:02:27 -0500 (EST) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: "Rafael J. Wysocki" cc: Tejun Heo , Jens Axboe , Linux-pm mailing list , Kernel development list Subject: Re: Bug in disk event polling In-Reply-To: <201202122226.22082.rjw@sisk.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 625 Lines: 19 On Sun, 12 Feb 2012, Rafael J. Wysocki wrote: > > > Given the stuff async is used for, maybe just make all async execution > > > freezable? > > > > That probably won't work. What if a driver relies on async thread > > execution to carry out its I/O? > > Well, we use async in the suspend code itself. :-) Yeah, I remembered that after sending the email message. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/