xen-devel
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching
To: |
Andi Kleen <ak@xxxxxxx> |
Subject: |
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching |
From: |
Chris Wright <chrisw@xxxxxxxxxxxx> |
Date: |
Wed, 22 Mar 2006 13:40:25 -0800 |
Cc: |
Zachary Amsden <zach@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Pratap Subrahmanyam <pratap@xxxxxxxxxx>, Wim Coekaerts <wim.coekaerts@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxx>, Joshua LeVasseur <jtl@xxxxxxxxxx>, Dan Hecht <dhecht@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jack Lo <jlo@xxxxxxxxxx>, Christopher Li <chrisl@xxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx, 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:49:55 +0000 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<200603222115.46926.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: |
<200603131802.k2DI2nv8005665@xxxxxxxxxxxxxxxxxxx> <200603222115.46926.ak@xxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.4.2.1i |
* Andi Kleen (ak@xxxxxxx) wrote:
> The disassembly stuff indeed doesn't look like something
> that belongs in the kernel.
Strongly agreed. The strict ABI requirements put forth here are not
in-line with Linux, IMO. I think source compatibility is the limit of
reasonable, and any ROM code be in-tree if something like this were to
be viable upstream.
thanks,
-chris
_______________________________________________
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 5/24] i386 Vmi code patching, (continued)
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Jan Engelhardt
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Andi Kleen
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching,
Chris Wright <=
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Anthony Liguori
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Chris Wright
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Keir Fraser
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Zachary Amsden
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Eli Collins
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Stefan Berger
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Zachary Amsden
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Anthony Liguori
- Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Zachary Amsden
- [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching, Zachary Amsden
|
|
|