From: Pavel Machek <pavel@suse.cz>
To: Zachary Amsden <zach@vmware.com>
Cc: Rik van Riel <riel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
greg@kroah.com, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
Rusty Russell <rusty@rustcorp.com.au>, Jack Lo <jlo@vmware.com>,
Sahil Rihan <srihan@vmware.com>
Subject: Re: A proposal - binary
Date: Wed, 9 Aug 2006 09:43:52 +0200 [thread overview]
Message-ID: <20060809074352.GL4886@elf.ucw.cz> (raw)
In-Reply-To: <44D7DDEF.6070907@vmware.com>
Hi!
> >Well, I guess we'd like VMI to be buildable in normal kernel build
> >tools ... and at that point, open sourcing it should be _really_ easy.
> >
> >And we'd prefer legal decisions not to influence technical ones. Maybe
> >we will decide to use binary interface after all, but seeing GPLed,
> >easily-buildable interface, first, means we can look at both solutions
> >and decide which one is better.
>
> I don't think you're actually arguing for the VMI ROM to be built into
> the kernel. But since this could be a valid interpretation of what you
> said, let me address that point so other readers of this thread don't
> misinterpret.
I actually was arguing for VMI ROM to be built into kernel. You have
pretty strong arguments why it will not work, but Xen is doing that,
and it would be at least very interesting to see how it works for
vmware. (And perhaps to decide that it does not work :-).
> On a purely technical level, the VMI layer must not be part of the
> normal kernel build. It must be distributed by the hypervisor to
> which
Oh yes, it can be part of kernel build. #ifdef vmware_version_3_0_4 is
ugly, but at least it would force you not to change the interfaces too
often, which might be good thing.
> We do use standard tools for building it, for the most part - although
> some perl scripting and elf munging magic is part of the build.
> Finally, since it is a ROM, we have to use a post-build tool to convert
> the extracted object to a ROM image and fix up the checksum. We don't
> have a problem including any of those tools in an open source
> distribution of the VMI ESX ROM once we finish sorting through the
> license issues. We've already fixed most of the problems we had with
> entangled header files so that we can create a buildable tarball that
> requires only standard GNU compilers, elf tools, and perl to run. I
> believe the only technical issue left is fixing the makefiles so that
> building it doesn't require our rather complicated make system.
Good, nice, so you are close. Now get us GPLed release ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-08-09 7:44 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 10:14 A proposal - binary Zachary Amsden
2006-08-03 11:16 ` Arjan van de Ven
2006-08-03 12:16 ` Antonio Vargas
2006-08-03 15:17 ` Rik van Riel
2006-08-03 16:05 ` Chris Wright
2006-08-03 17:57 ` Zachary Amsden
2006-08-03 18:29 ` Antonio Vargas
2006-08-03 18:47 ` Zachary Amsden
2006-08-03 18:08 ` Zachary Amsden
2006-08-03 19:03 ` Greg KH
2006-08-03 19:14 ` Zachary Amsden
2006-08-03 19:36 ` Greg KH
2006-08-03 19:56 ` Dave Jones
2006-08-03 19:59 ` Greg KH
2006-08-03 20:25 ` Options depending on STANDALONE Adrian Bunk
2006-08-03 20:28 ` Greg KH
2006-08-03 20:41 ` Dave Jones
2006-08-03 23:40 ` [v4l-dvb-maintainer] " Trent Piepho
2006-08-05 10:51 ` Adrian Bunk
2006-08-06 11:18 ` Oliver Endriss
2006-08-13 16:36 ` Adrian Bunk
2006-08-14 21:15 ` Trent Piepho
2006-08-27 21:45 ` Adrian Bunk
2006-08-03 19:48 ` A proposal - binary linux-os (Dick Johnson)
2006-08-04 6:13 ` Jan Engelhardt
2006-08-03 21:03 ` Alan Cox
2006-08-03 13:21 ` Alan Cox
2006-08-03 20:29 ` Willy Tarreau
2006-08-03 21:12 ` Alan Cox
2006-08-03 21:27 ` Zachary Amsden
2006-08-03 15:35 ` Rik van Riel
2006-08-03 18:36 ` Zachary Amsden
2006-08-05 10:45 ` Pavel Machek
2006-08-06 22:45 ` Zachary Amsden
2006-08-06 22:59 ` Greg KH
2006-08-08 0:12 ` Pavel Machek
2006-08-08 0:42 ` Zachary Amsden
2006-08-09 7:43 ` Pavel Machek [this message]
2006-08-03 19:06 ` Greg KH
2006-08-03 19:26 ` Zachary Amsden
2006-08-03 20:01 ` Greg KH
2006-08-03 21:41 ` Zachary Amsden
2006-08-03 22:33 ` Alan Cox
2006-08-03 22:30 ` Greg KH
2006-08-03 22:49 ` Zachary Amsden
2006-08-03 22:31 ` Zachary Amsden
2006-08-03 23:30 ` Alan Cox
2006-08-03 23:40 ` Zachary Amsden
2006-08-04 10:21 ` Alan Cox
2006-08-04 14:34 ` Theodore Tso
2006-08-05 0:06 ` Paul Mackerras
2006-08-04 8:56 ` Christoph Hellwig
2006-08-04 2:52 ` Jeremy Fitzhardinge
2006-08-04 4:18 ` Andrew Morton
2006-08-04 5:04 ` Rusty Russell
2006-08-04 5:53 ` Andrew Morton
2006-08-04 7:04 ` Rusty Russell
2006-08-04 7:21 ` Andrew Morton
2006-08-04 8:29 ` Rusty Russell
2006-08-04 16:57 ` David Lang
2006-08-04 18:38 ` Jeremy Fitzhardinge
2006-08-04 18:46 ` Antonio Vargas
2006-08-04 19:06 ` David Lang
2006-08-04 19:26 ` Arjan van de Ven
2006-08-04 19:45 ` David Lang
2006-08-04 20:11 ` Jeremy Fitzhardinge
2006-08-04 20:31 ` David Lang
2006-08-04 21:26 ` Jeremy Fitzhardinge
2006-08-04 21:40 ` Bill Rugolsky Jr.
2006-08-04 22:00 ` Arjan van de Ven
2006-08-04 22:45 ` David Lang
2006-08-04 19:45 ` Jeff Dike
2006-08-04 19:49 ` David Lang
2006-08-04 21:46 ` Jeff Dike
2006-08-04 22:40 ` David Lang
2006-08-04 5:40 ` Chris Wright
2006-08-04 6:28 ` Antonio Vargas
2006-08-04 7:01 ` Chris Wright
2006-08-04 7:19 ` Antonio Vargas
2006-08-04 7:37 ` Chris Wright
2006-08-04 18:34 ` Chris Wright
2006-08-04 20:41 ` Zachary Amsden
2006-08-04 20:52 ` Chris Wright
2006-08-04 21:26 ` Alan Cox
2006-08-05 1:14 ` James Bottomley
2006-08-05 5:37 ` Zachary Amsden
2006-08-05 10:42 ` Adrian Bunk
2006-08-05 11:50 ` Alan Cox
2006-08-04 22:01 ` Andi Kleen
2006-08-04 22:39 ` Zachary Amsden
2006-08-04 22:52 ` Andi Kleen
2006-08-04 22:43 ` David Lang
2006-08-05 10:47 ` Adrian Bunk
2006-08-05 11:57 ` Andi Kleen
2006-08-05 1:30 ` James Bottomley
2006-08-05 4:33 ` Zachary Amsden
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=20060809074352.GL4886@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jlo@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=srihan@vmware.com \
--cc=torvalds@osdl.org \
--cc=zach@vmware.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