|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for
To: |
Christoph Lameter <clameter@xxxxxxx> |
Subject: |
[Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface |
From: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
Date: |
Wed, 21 Feb 2007 12:02:58 -0800 |
Cc: |
Zachary Amsden <zach@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>, Andi Kleen <ak@xxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> |
Delivery-date: |
Wed, 21 Feb 2007 12:02:50 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<Pine.LNX.4.64.0702211036060.24941@xxxxxxxxxxxxxxxxxxxxxxxxx> |
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<20070216022449.739760547@xxxxxxxx> <Pine.LNX.4.64.0702161244380.26718@xxxxxxxxxxxxxxxxxxxxxxxxx> <45D61C74.2000601@xxxxxxxxxx> <Pine.LNX.4.64.0702161312460.28871@xxxxxxxxxxxxxxxxxxxxxxxxx> <45D626BB.20007@xxxxxxxxxx> <Pine.LNX.4.64.0702161356380.29218@xxxxxxxxxxxxxxxxxxxxxxxxx> <20070217135112.GA15102@xxxxxx> <Pine.LNX.4.64.0702211036060.24941@xxxxxxxxxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Thunderbird 1.5.0.9 (X11/20070212) |
Christoph Lameter wrote:
> And it seems that the hooks are not generic but bound to a particular
> hypervisor. Should the Xen specific stuff not be in the binary blob?
Xen has no "binary blob". It needs guests to cooperate with it by
making hypercalls; all that code is in the Xen implementation of the
paravirt_ops interface, which is just ordinary code which lives in the
kernel sources.
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, (continued)
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Christoph Lameter
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Zachary Amsden
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Christoph Lameter
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Zachary Amsden
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Rusty Russell
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Christoph Lameter
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Zachary Amsden
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Andi Kleen
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Christoph Lameter
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Zachary Amsden
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface,
Jeremy Fitzhardinge <=
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Jeremy Fitzhardinge
- [Xen-devel] Re: [patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface, Rusty Russell
|
|
|
|
|