From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Subject: Re: [PATCH 2/2] Fix console handling during suspend/resume Date: Wed, 14 Jun 2006 18:46:55 -0700 Message-ID: <200606141846.55839.david-b@pacbell.net> References: <20060614103404.GC28536@elf.ucw.cz> <20060614235713.GA24859@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20060614235713.GA24859@elf.ucw.cz> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: linux-pm@lists.osdl.org Cc: Linus Torvalds , Pavel Machek List-Id: linux-pm@vger.kernel.org On Wednesday 14 June 2006 4:57 pm, Pavel Machek wrote: > My point is that you really want the console enabled in writing phase > of suspend-to-disk. = Notice how nicely this generalizes a point that's been made before: Linux should have the ability to exclude certain devices (and their parents) from that first "prepare to suspend" phase. Originally the canonical example was the swap device (and its disk, controller, bus tree, etc). Now we recognize consoles (and their parents, network controllers, etc) have the same issue ... Of course using such a mechanism would call for a bit of rework in swsusp and str code, as well as implementing that exclusion mechanism. - Dave