On Thu, Feb 06, 2014 at 01:45:07PM +0100, Giorgio Zoppi wrote:
i offer part of my free time as mentor.
From my original email:
In order to mentor you must be an established contributor (regularly
contribute patches).
I couldn't find any commits from you in QEMU, libvirt, or Linux. Did I
miss
On Thu, Feb 06, 2014 at 12:22:36PM +0530, Jobin Raju George wrote:
I am trying to establish a communication mechanism between the guest
and its host using virtio-serial. For this I am using the following to
boot the VM:
qemu-system-x86_64 -m 1024 \
-name ubuntu_vm \
-hda ubuntu \
-device
Hi Nicholas,
Adding Vadim Rozenfeld who wrote the virtio-scsi driver.
Best regards,
Yan.
On Feb 7, 2014, at 10:14 PM, Nicholas A. Bellinger n...@linux-iscsi.org wrote:
Hi Yan,
So recently I've been doing some KVM guest performance comparisons
between the scsi-mq prototype using
On Sun, 2014-02-09 at 11:24 +0200, Yan Vugenfirer wrote:
Hi Nicholas,
Adding Vadim Rozenfeld who wrote the virtio-scsi driver.
Best regards,
Yan.
On Feb 7, 2014, at 10:14 PM, Nicholas A. Bellinger n...@linux-iscsi.org
wrote:
Hi Yan,
So recently I've been doing some KVM guest
Hi All,
If the host system decides that it wants to push a given page out to
swap, the host will notify the host through registered mmu notifier to
inform the guest. I am wondering if there any other situations, other
than swapping, which will trigger the mmu notifier to inform host page
change to
-- Forwarded message --
From: Jobin Raju George jobin...@gmail.com
Date: Sun, Feb 9, 2014 at 11:39 PM
Subject: Re: Using block device instead of character device for virtio-serial
To: Stefan Hajnoczi stefa...@gmail.com
Cc: kvm@vger.kernel.org
On Sun, Feb 9, 2014 at 2:42 PM,
Am 31.01.2014 12:42, schrieb Paolo Bonzini:
Il 30/01/2014 20:48, Eduardo Habkost ha scritto:
There isn't any kind of registration involved in cpu_x86_register()
anymore: it is simply looking up a CPU model name and loading the model
definition data into the X86CPU object. Rename it to
Am 30.01.2014 20:48, schrieb Eduardo Habkost:
As we will initialize the X86CPU fields on instance_init eventually,
move the code that initializes the X86CPU data based on the CPU model
name closer to the object_new() call.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
Thanks, applied
Am 31.01.2014 12:42, schrieb Paolo Bonzini:
Il 30/01/2014 20:48, Eduardo Habkost ha scritto:
As the new X86CPU subclass code is going to change lots of the code
invoving x86_def_t, let's rename the struct to match coding style first.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
[...]
Am 31.01.2014 19:13, schrieb Eduardo Habkost:
Register separate QOM classes for each x86 CPU model.
This will allow management code to more easily probe what each CPU model
provides, by simply creating objects using the appropriate class name,
without having to restart QEMU.
This also
10 matches
Mail list logo
