xen-devel
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II
To: |
Zachary Amsden <zach@xxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation II |
From: |
Andi Kleen <ak@xxxxxxx> |
Date: |
Wed, 22 Mar 2006 23:38:42 +0100 |
Cc: |
Andrew Morton <akpm@xxxxxxxx>, Joshua LeVasseur <jtl@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Pratap Subrahmanyam <pratap@xxxxxxxxxx>, Wim Coekaerts <wim.coekaerts@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxx>, Jack Lo <jlo@xxxxxxxxxx>, Dan Hecht <dhecht@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>, Christopher Li <chrisl@xxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx, Linus Torvalds <torvalds@xxxxxxxx>, Anne Holler <anne@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:59:41 +0000 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<4421D379.3090405@xxxxxxxxxx> |
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> <200603222239.46604.ak@xxxxxxx> <4421D379.3090405@xxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
KMail/1.9.1 |
On Wednesday 22 March 2006 23:45, Zachary Amsden wrote:
> I propose an entirely different approach - use segmentation.
That would require a lot of changes to save/restore the segmentation
register at kernel entry/exit since there is no swapgs on i386.
And will be likely slower there too and also even slow down the
VMI-kernel-no-hypervisor.
Still might be the best option.
How did that rumoured Xenolinux-over-VMI implementation solve that problem?
-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, 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
|
|
|