|
xen-devel
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation
|
To: |
Andi Kleen <ak@xxxxxxx> |
|
Subject: |
[Xen-devel] Re: [RFC, PATCH 1/24] i386 Vmi documentation |
|
From: |
Zachary Amsden <zach@xxxxxxxxxx> |
|
Date: |
Wed, 22 Mar 2006 16:06:10 -0800 |
|
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>, Chris Wright <chrisw@xxxxxxxxxxxx>, 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 18:02:42 +0000 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<200603222213.45910.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> <20060322213435.GI15997@xxxxxxxxxxxxxxxxxx> <200603222213.45910.ak@xxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Thunderbird 1.5 (X11/20051201) |
Andi Kleen wrote:
Even then it's useless for many flags because any user program can (and will)
call CPUID directly.
Turns out not to matter, since userspace can only make use of
capabilities that are already available to userspace. If the feature
bits for system features are visible to it, it doesn't really matter.
Yes, this could be broken in some cases. But it turns out to be safe.
Even sysenter support, which userspace does care about, is done via
setting the vsyscall page up in the kernel, rather than userspace CPUID
detection.
Sure the point was if they write this long fancy document why stop
at documenting the last 5%?
Because the last 5% is what is changing to meet Xen's needs. Why
document something that you know you are going to break in a week? I
chose to document the stable interfaces first.
_______________________________________________
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, 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