Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265173AbUATAd3 (ORCPT ); Mon, 19 Jan 2004 19:33:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265062AbUATA1h (ORCPT ); Mon, 19 Jan 2004 19:27:37 -0500 Received: from gprs214-67.eurotel.cz ([160.218.214.67]:63362 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S263580AbUATAFH (ORCPT ); Mon, 19 Jan 2004 19:05:07 -0500 Date: Tue, 20 Jan 2004 01:04:35 +0100 From: Pavel Machek To: Benjamin Herrenschmidt Cc: ncunningham@users.sourceforge.net, Hugang , ncunningham@clear.net.nz, Linux Kernel Mailing List , debian-powerpc@lists.debian.org Subject: Re: Help port swsusp to ppc. Message-ID: <20040120000435.GB837@elf.ucw.cz> References: <20040119105237.62a43f65@localhost> <1074483354.10595.5.camel@gaston> <1074489645.2111.8.camel@laptop-linux> <1074490463.10595.16.camel@gaston> <20040119204551.GB380@elf.ucw.cz> <1074555531.10595.89.camel@gaston> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1074555531.10595.89.camel@gaston> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1319 Lines: 32 Hi! > > Well, then what you do is not swsusp. > > > > swsusp does assume same kernel during suspend and resume. Doing resume > > within bootloader (and thus avoiding this) would be completely > > different design. > > Wait... what the hell in swsusp requires this assumption ? It seems to > me like a completely unnecessary design limitation. (1) There's routine during resume that copies pages to their old locations. If you (would want to) have different kernel during resume, how do you guarantee that that "kernel being resumed" does not use memory ocupied by copying routine? (2) Plus number of problems with devices grows with number of versions squared. To guarantee it works properly you'd have to test all combinations of "suspend kernel" and "resume kernel". [(1) Could be solved by reserving 4KB somewhere for copy routine, and making sure copy routine is never bigger than 4KB etc. But I'd like to keep it simple and really don't want to deal with (2).] Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - 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/