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 3/4] x86-64: EFI runtime code

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 3/4] x86-64: EFI runtime code
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Mon, 27 Jun 2011 18:36:44 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 27 Jun 2011 10:37:51 -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=mquayZZquqD13KA8Y5DrVH4zY+eqLGbEkFbTtOXJGF0=; b=DsaEVIsHv9XEwezNP+yIgeiW7W8r4mRF3V60buSVFxoe2p/EDRWSWHWWdiV9J2ZupQ LSdhS9NbeshAYg2lIldYSGe/qguaUaZOKClYR9sA6daytSpPda4eMYfxgPWKmaSqlDhu khx5qwl6VoOIn19C64mf3MwXpd2xKi4WPzIYo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110627162537.GS6978@xxxxxxxxxxxx>
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: Acw08MgNfqHjo6NuxE66ba8VH1LgUw==
Thread-topic: [Xen-devel] [PATCH 3/4] x86-64: EFI runtime code
User-agent: Microsoft-Entourage/
On 27/06/2011 17:25, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:

> On Mon, Jun 27, 2011 at 11:43:02AM +0100, Jan Beulich wrote:
>> This allows Dom0 access to all suitable EFI runtime services. The
> What type of patches for the upstream 3.0 kernel are needed to take
> advantage of these new hypercalls?

This is probably the biggest thing to get right, as details below the public
interface alterations can all be subject to change. I belive patches 2/4 and
3/4 are the only two with public header changes. Do you want to reserve an
Ack/Nack on those? You might need to get 2/4 direct from Jan as it seems to
have stalled at the list server.

 -- Keir

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list