|
xen-devel
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II
|
To: |
virtualization@xxxxxxxxxxxxxx |
|
Subject: |
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II |
|
From: |
Andi Kleen <ak@xxxxxxx> |
|
Date: |
Wed, 22 Mar 2006 22:39:44 +0100 |
|
Cc: |
Zachary Amsden <zach@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Pratap Subrahmanyam <pratap@xxxxxxxxxx>, Wim Coekaerts <wim.coekaerts@xxxxxxxxxx>, Joshua LeVasseur <jtl@xxxxxxxxxx>, Dan Hecht <dhecht@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jack Lo <jlo@xxxxxxxxxx>, Christopher Li <chrisl@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxx>, Anne Holler <anne@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Jyothy Reddy <jreddy@xxxxxxxxxx>, Kip Macy <kmacy@xxxxxxxxxxx>, Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, Leendert van Doorn <leendert@xxxxxxxxxxxxxx>, Dan Arai <arai@xxxxxxxxxx> |
|
Delivery-date: |
Thu, 23 Mar 2006 17:54:00 +0000 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<200603222105.58912.ak@xxxxxxx> |
|
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: |
<200603131759.k2DHxeep005627@xxxxxxxxxxxxxxxxxxx> <200603222105.58912.ak@xxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
KMail/1.9.1 |
> There was one other point I wanted to make but I forgot it now @)
Ah yes the point was that since most of the implementations of the hypercalls
likely need fast access to some per CPU state. How would you plan
to implement that? Should it be covered in the specification?
-Andi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation, (continued)
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation, Rik van Riel
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation, Andi Kleen
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation, Zachary Amsden
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II,
Andi Kleen <=
- [Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II, Daniel Arai
- [Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II, Zachary Amsden
- [Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II, Andi Kleen
- [Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II, Zachary Amsden
- [Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II, Andi Kleen
[Xen-devel] [RFC, PATCH 1/24] i386 Vmi documentation, Zachary Amsden
|
|
|
Home