On (Fri) Sep 18 2009 [12:55:20], Anthony Liguori wrote:
So you need a tiny kernel side driver to unpack it into a meaningful
fs, or just a user-user channel with a daemon each end and a protocol
over it - nothing kernel in that.
I think there's some confusion over what this driver
On (Fri) Sep 18 2009 [10:57:59], H. Peter Anvin wrote:
On 09/18/2009 10:55 AM, Anthony Liguori wrote:
I fail to see how this is at all relevant. This is a virtual machine,
we're presenting virtual hardware that behaves like a serial device.
Where web servers fit in is completely beyond
On 09/18/2009 03:17 AM, Alok Kataria wrote:
Hi,
We ran a few experiments to compare performance of VMware's
paravirtualization technique (VMI) and hardware MMU technologies (HWMMU)
on VMware's hypervisor.
To give some background, VMI is VMware's paravirtualization
specification which tries
On Thu, Sep 17, 2009 at 05:17:08PM -0700, Alok Kataria wrote:
Given this new development, I wanted to discuss how should we go about
retiring the VMI code from mainline Linux, i.e. the vmi_32.c and
vmiclock_32.c bits.
One of the options that I am contemplating is to drop the code from the
On 09/19/09 15:44, Greg KH wrote:
That sounds good to me, how intrusive are the patches to do this? Is it
going to be tricky to get everything merged properly in -tip for it?
They should be very local - just a matter of removing a couple of files
and dropping some config options.
J
On Sat, 2009-09-19 at 15:44 -0700, Greg KH wrote:
On Thu, Sep 17, 2009 at 05:17:08PM -0700, Alok Kataria wrote:
Given this new development, I wanted to discuss how should we go about
retiring the VMI code from mainline Linux, i.e. the vmi_32.c and
vmiclock_32.c bits.
One of the
Here is the patch which actually removes the vmi code.
Signed-off-by: Alok N Kataria akata...@vmware.com
---
Documentation/kernel-parameters.txt |2
arch/x86/Kconfig| 10
arch/x86/include/asm/vmi.h | 269 --
arch/x86/include/asm/vmi_time.h |
