|
xen-devel
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching
|
To: |
virtualization@xxxxxxxxxxxxxx |
|
Subject: |
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching |
|
From: |
Andi Kleen <ak@xxxxxxx> |
|
Date: |
Wed, 22 Mar 2006 21:15: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:48:09 +0000 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<200603131802.k2DI2nv8005665@xxxxxxxxxxxxxxxxxxx> |
|
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> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
KMail/1.9.1 |
On Monday 13 March 2006 19:02, Zachary Amsden wrote:
> The VMI ROM detection and code patching mechanism is illustrated in
> setup.c. There ROM is a binary block published by the hypervisor, and
> and there are certainly implications of this. ROMs certainly have a
> history of being proprietary, very differently licensed pieces of
> software, and mostly under non-free licenses. Before jumping to the
> conclusion that this is a bad thing, let us consider more carefully
> why hiding the interface layer to the hypervisor is actually a good
> thing.
How about you fix all these issues you describe here first
and then submit it again?
The disassembly stuff indeed doesn't look like something
that belongs in the kernel.
-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 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
|
|
|
Home