From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCWsR-0005V8-AT for qemu-devel@nongnu.org; Mon, 23 Nov 2009 06:14:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCWsM-0005PP-8E for qemu-devel@nongnu.org; Mon, 23 Nov 2009 06:14:38 -0500 Received: from [199.232.76.173] (port=40975 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCWsL-0005PB-Im for qemu-devel@nongnu.org; Mon, 23 Nov 2009 06:14:34 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54985) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCWsL-00021B-3k for qemu-devel@nongnu.org; Mon, 23 Nov 2009 06:14:33 -0500 Date: Mon, 23 Nov 2009 13:14:28 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: POST failure (loop) with isapc and seabios Message-ID: <20091123111428.GG2999@redhat.com> References: <20091120225113.GD24539@morn.localdomain> <20091122123503.GH3193@redhat.com> <20091122151052.GK3193@redhat.com> <217FD12D88EA4AC2B2A32D77E010B16C@FSCPC> <20091122153809.GL3193@redhat.com> <20091122174024.GD13491@morn.localdomain> <25D5F9DE78F3461EB5CA80EE4B22AE91@FSCPC> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25D5F9DE78F3461EB5CA80EE4B22AE91@FSCPC> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sebastian Herbszt Cc: Kevin O'Connor , qemu-devel@nongnu.org On Sun, Nov 22, 2009 at 11:04:34PM +0100, Sebastian Herbszt wrote: > Kevin O'Connor wrote: > >On Sun, Nov 22, 2009 at 05:38:09PM +0200, Gleb Natapov wrote: > >>On Sun, Nov 22, 2009 at 04:31:24PM +0100, Sebastian Herbszt wrote: > >>> // Write protect bios memory. > >>> make_bios_readonly(); > >>Hmmm. How is tpr patching works then? It relies on ability of a guest to > >>write into BIOS memory region. Need to retest if it actually works I > >>guess. > > > >The last time I looked, the TPR patching backend forced the "vapic" > >pages to be writable (effectively overriding the bios decision to make > >it readonly). > > Does the TPR thing have to live in the optionrom/bios space or can it be moved > somewhere else like just below 4GB (some other kvm stuff is already there) ? > It needs to be in a memory that is mapped by WindowsXP kernel (but not used by it). WindowsXP maps optionrom/bios memory, but AFAIK not e820 memory. -- Gleb.