From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58285) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtQm6-0000pR-Is for qemu-devel@nongnu.org; Wed, 18 Dec 2013 18:43:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VtQly-000386-6T for qemu-devel@nongnu.org; Wed, 18 Dec 2013 18:43:34 -0500 Received: from mail-ee0-x229.google.com ([2a00:1450:4013:c00::229]:34529) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtQlx-00037u-Vi for qemu-devel@nongnu.org; Wed, 18 Dec 2013 18:43:26 -0500 Received: by mail-ee0-f41.google.com with SMTP id t10so144575eei.0 for ; Wed, 18 Dec 2013 15:43:25 -0800 (PST) Sender: Paolo Bonzini Message-ID: <52B23319.9040302@redhat.com> Date: Thu, 19 Dec 2013 00:43:21 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1386753670-11238-1-git-send-email-ghammer@redhat.com> <52B1AFC3.1050809@redhat.com> <20131218152227.GA21186@redhat.com> <1387384032.2585.7.camel@localhost.localdomain> <20131218163306.GB21916@redhat.com> <178534992.41571400.1387384454834.JavaMail.root@redhat.com> <52B21D4A.8010204@redhat.com> In-Reply-To: <52B21D4A.8010204@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] piix: do not reset APIC base address (0x80) on piix4_reset. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Gal Hammer , seabios@seabios.org, "Michael S. Tsirkin" , qemu-devel@nongnu.org, marcel a Il 18/12/2013 23:10, Laszlo Ersek ha scritto: > > So, if PEI must do something after S3 resume that is independent of any > DXE drivers, it can simply do it. The boot script is only necessary when > the S3 resume PEI actions (in step 6) need to depend on earlier actions > during DXE (step 3). In SeaBIOS, PEI is really almost nothing (it's just the contents of src/resume.c), so all the setup needs to be placed in the "boot script". For example I suspect that using INT 13h for disk I/O does not work after S3. Paolo