[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69304d110608030516y16f7d1fdiaccfbe4ecca3084a@mail.gmail.com>
Date: Thu, 3 Aug 2006 14:16:46 +0200
From: "Antonio Vargas" <windenntw@...il.com>
To: "Arjan van de Ven" <arjan@...radead.org>,
"Zachary Amsden" <zach@...are.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Linus Torvalds" <torvalds@...l.org>, greg@...ah.com,
"Andrew Morton" <akpm@...l.org>,
"Christoph Hellwig" <hch@...radead.org>,
"Rusty Russell" <rusty@...tcorp.com.au>, "Jack Lo" <jlo@...are.com>
Subject: Re: A proposal - binary
On 8/3/06, Arjan van de Ven <arjan@...radead.org> wrote:
> On Thu, 2006-08-03 at 03:14 -0700, Zachary Amsden wrote:
> > I would like to propose an interface for linking a GPL kernel,
> > specifically,
> > Linux, against binary blobs. Stop. Before you condemn this as evil,
> > let me
> > explain in precise detail what a binary blob is.
>
>
> Hi,
>
> you use a lot of words for saying something self contradictory. It's
> very simple; based on your mail, there's no reason the VMI gateway page
> can't be (also) GPL licensed (you're more than free obviously to dual,
> tripple or quadruple license it). Once your gateway thing is gpl
> licensed, your entire proposal is moot in the sense that there is no
> issue on the license front. See: it can be very easy. Much easier than
> trying to get a license exception (which is very unlikely you'll get)...
>
>
> Now you can argue for hours about if such an interface is desirable or
> not, but I didn't think your email was about that.
>
> Greetings,
> Arjan van de Ven
>
> --
> if you want to mail me at work (you don't), use arjan (at) linux.intel.com
If the essence of using virtual machines is precisely that the machine
acts just as if it was a real hardware one, then we should not need
any modifications to the kernel. So, it would be much better if the
hypervirsor was completely transparent and just emulated a native cpu
and a common native set of hardware, which would then work 100% with
the native code in the kernel. This keeps the smarts of virtual
machine management on the hypervisor.
For example, TBL and pagetable handling can be done with 2 interfaces,
one standard via intercepting normal cpu instructions, and a batched
one via a hardware driver with a FIFO on shared memory just like many
graphics card do to send commands and data to the GPU. I recall this
design was the one used in the mac-on-linux hypervisor for ppc
architecture. Why not for x86 with vt/pacifica extensions? What about
using the same design than on the Sparc T1 port?
--
Greetz, Antonio Vargas aka winden of network
http://network.amigascne.org/
windNOenSPAMntw@...il.com
thesameasabove@...gascne.org
Every day, every year
you have to work
you have to study
you have to scene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists