|
xen-devel
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching
|
To: |
Zachary Amsden <zach@xxxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching |
|
From: |
Pavel Machek <pavel@xxxxxx> |
|
Date: |
Thu, 16 Mar 2006 00:00:13 +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 Mailing List <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: |
Fri, 17 Mar 2006 10:40:08 +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: |
Mutt/1.5.9i |
Hi!
> Currently, the system is designed to boot under a fully virtualized
> (or native) environment, then switch into paravirtual mode. It does
> this by detecting the presence of a ROM code page, invoking the
This is not going to work with xen, is it?
> The question of licensing of such ROM code is a completely separate
> issue. We are not trying to hide some proprietary code by putting it
> inside of a ROM to keep it hidden. In fact, you can disassemble the
> ROM code and see it quite readily - and you know all of the entry
> points.
Could you disassemble one entry point for us and describe how it works?
> Whether we can distribute our ROM code under a GPL compatible license
> is not something I know at this time. Just as you can't compile a
> binary using Linux kernel headers and claim that your binary is not
> subject to the GPL, our ROM code includes headers from other parts of
> our system that are specifically not under the GPL. How this
VMware is probably sole copyright holder (no?), you are perfectly free
to relicence resulting ROM code under whatever licence you want.
--
31: }
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home