From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L5g5n-0005ht-7y for qemu-devel@nongnu.org; Thu, 27 Nov 2008 07:35:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L5g5l-0005dl-Gm for qemu-devel@nongnu.org; Thu, 27 Nov 2008 07:35:34 -0500 Received: from [199.232.76.173] (port=33913 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L5g5l-0005dR-6Z for qemu-devel@nongnu.org; Thu, 27 Nov 2008 07:35:33 -0500 Received: from mx2.redhat.com ([66.187.237.31]:40963) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L5g5k-0007eO-PX for qemu-devel@nongnu.org; Thu, 27 Nov 2008 07:35:33 -0500 Date: Thu, 27 Nov 2008 14:35:57 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] [PATCH v5 0/5] Support for S3 ACPI state (suspend to memory) in BIOS Message-ID: <20081127123557.GB21985@redhat.com> References: <20081127110220.25353.83454.stgit@dhcp-1-237.tlv.redhat.com> <492E8FCC.2020203@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <492E8FCC.2020203@gmx.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: bochs-developers@lists.sourceforge.net On Thu, Nov 27, 2008 at 01:17:16PM +0100, Carl-Daniel Hailfinger wrote: > Hi, > > On 27.11.2008 12:02, Gleb Natapov wrote: > > This patch series adds S3 (suspend to RAM) ACPI state to BIOS. Most > > changes concern themselves with preventing BIOS from using memory > > locations available to a guest OS. > > > > I see the problem you're facing with the overwrite and it looks there > might be a cleaner solution: If you can lock the CPU cache so that > writes don't get passed through to RAM, you're free to use any area > (with a few contraints) for stack without having to worry about > clobbering memory contents there. > > That method is called Cache-as-RAM and I'm currently trying to implement > it in Qemu. I haven't looked into Bochs yet, but it should be doable > there as well. > It would be nice to not worry about stack location. We may try to use it when you changes will work in Qemu and BOCHS. -- Gleb.