From: Zachary Amsden <zach@vmware.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Xen-devel <xen-devel@lists.xensource.com>,
virtualization@lists.osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christopher Li <chrisl@vmware.com>,
Wim Coekaerts <wim.coekaerts@oracle.com>, Andi Kleen <ak@suse.de>,
Chris Wright <chrisw@osdl.org>,
Linus Torvalds <torvalds@osdl.org>, Anne Holler <anne@vmware.com>,
Jan Beulich <jbeulich@novell.com>,
Jyothy Reddy <jreddy@vmware.com>, Kip Macy <kmacy@fsmware.com>,
Ky Srinivasan <ksrinivasan@novell.com>,
Leendert van Doorn <leendert@watson.ibm.com>
Subject: Re: [Xen-devel] Re: [RFC, PATCH 5/24] i386 Vmi code patching
Date: Wed, 22 Mar 2006 17:01:03 -0800 [thread overview]
Message-ID: <4421F34F.6030300@vmware.com> (raw)
In-Reply-To: <4421F190.2050908@us.ibm.com>
Anthony Liguori wrote:
>
> Hrm, I was actually thinking that each of the VMI calls would be an
> export (vmi_init, vmi_set_pxe, etc.). I know that you want the
> hypervisor to drive the inlining but I that's sufficiently hairy (not
> to mention, there's not AFAIK performance data yet to justify it) that
> I think it ought to be left for VMI 2.0.
That seems quite ok to me. It is a little weird to have the VMI calls
be an export when some of them really can never be properly callable C
functions, and you have to overwrite the native code, so the linking
step is .. well this magic disassembly glue again. But it could be made
to work, and we have discussed it before.
> Multi-licensing is fine as long as one is GPL :-)
I agree. But it sort of defeats the point of the GPL if you can
optionally redistribute the code under the BSD license as well.
prev parent reply other threads:[~2006-03-23 1:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 18:02 [RFC, PATCH 5/24] i386 Vmi code patching Zachary Amsden
2006-03-15 10:02 ` Chris Wright
2006-03-15 16:01 ` Zachary Amsden
2006-03-15 22:05 ` Anthony Liguori
2006-03-15 23:00 ` Pavel Machek
2006-03-17 0:51 ` Zachary Amsden
2006-03-17 10:08 ` Joshua LeVasseur
2006-03-17 21:11 ` Chris Wright
2006-03-18 0:49 ` Joshua LeVasseur
2006-03-16 19:10 ` Jan Engelhardt
2006-03-16 19:45 ` Rik van Riel
2006-03-16 21:54 ` Zachary Amsden
2006-03-22 20:15 ` Andi Kleen
2006-03-22 21:40 ` Chris Wright
2006-03-22 22:16 ` Zachary Amsden
2006-03-22 22:33 ` Daniel Arai
2006-03-22 23:02 ` Chris Wright
2006-03-22 22:51 ` Chris Wright
2006-03-22 23:36 ` Zachary Amsden
2006-03-23 0:41 ` Chris Wright
2006-03-23 0:54 ` Zachary Amsden
2006-03-23 1:06 ` Chris Wright
2006-03-23 4:04 ` Zachary Amsden
2006-03-23 11:42 ` Joshua LeVasseur
2006-03-23 0:31 ` Anthony Liguori
2006-03-23 0:40 ` Chris Wright
2006-03-23 9:25 ` Keir Fraser
2006-03-23 18:50 ` [Xen-devel] " Zachary Amsden
2006-03-23 23:45 ` Eli Collins
2006-03-23 0:46 ` Zachary Amsden
2006-03-23 0:53 ` Anthony Liguori
2006-03-23 1:01 ` Zachary Amsden [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4421F34F.6030300@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=aliguori@us.ibm.com \
--cc=anne@vmware.com \
--cc=chrisl@vmware.com \
--cc=chrisw@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jbeulich@novell.com \
--cc=jreddy@vmware.com \
--cc=kmacy@fsmware.com \
--cc=ksrinivasan@novell.com \
--cc=leendert@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=wim.coekaerts@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox