This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 1 of 3] Enable UEFI BIOS(OVMF) support in Xen-uns

To: Andrei Warkentin <andreiw@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1 of 3] Enable UEFI BIOS(OVMF) support in Xen-unstable HVM
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Sat, 23 Jul 2011 07:53:50 +0100
Cc: edk2-devel@xxxxxxxxxxxxxxxxxxxxx, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jordan Justen <jljusten@xxxxxxxxx>, Bei Guan <gbtju85@xxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Delivery-date: Fri, 22 Jul 2011 23:54:54 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=MZh9Meh7KOvWjqYbPHg5VX/7/4Pfr6cquFnmdITn8HY=; b=k0ybhUywOVyZiS7dJFS+jMzW3AaNWM4hk523mpCgBpsrCRFzeGdvX1yhOs1BCBswcx z0BKZL5apERphoV+8rqJfmwYBSON7emlKKJgQyZtb+bDCmPm81evewTiqKDl+ROuN1x3 542+8ZvUtGxLXXrNOFNYLYxhyJlHcfDZwBYVQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CALfQTu5qNSE3_=NqZQ7Hz0SZJbEAt0WC8E-66br9VGA9oykYVQ@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxJBUbl+XypC1FrJ0qDOPkuRK47+w==
Thread-topic: [Xen-devel] [PATCH 1 of 3] Enable UEFI BIOS(OVMF) support in Xen-unstable HVM
User-agent: Microsoft-Entourage/
On 22/07/2011 19:38, "Andrei Warkentin" <andreiw@xxxxxxxxxxxx> wrote:

> On Fri, Jul 22, 2011 at 11:38 AM, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>> Looks pretty decent. I wonder why you need to change get_shared_info() --
>> the existing mapping location is unused at the time hvmloader runs, and you
>> instead map it over the top of a page of RAM. If you want shared_info mapped
>> elsewhere, you can map it wherever you like as soon as your BIOS payload
>> takes over.
> The problem is that this page lies in an unsafe for OVMF area (right
> below 4GB). In a typical PC environment,
> you have the firmware ROM decoding the physical address space right
> below 4GB, and it also has a chunk (~64-128k) shadowed below 1MB for
> legacy reasons. The EFI firmware bootstrap code is written with the
> assumption that it can transfer control to code < 4GB that will
> finalize the 16->PM-(>LM if 64) transitions and call C code. The
> get_shared_info page overlaps code we copy up below 4GB. This is why
> it was moved to a safer region.

Okay, we can work with this easily enough.

 -- Keir

Xen-devel mailing list