On Thu, Apr 01, 2010 at 11:22:37AM -0700, David Stevens wrote:
kvm-ow...@vger.kernel.org wrote on 04/01/2010 03:54:15 AM:
On Wed, Mar 31, 2010 at 03:04:43PM -0700, David Stevens wrote:
+ head.iov_base = (void
*)vhost_get_vq_desc(net-dev,
vq,
+
On Fri, Apr 02, 2010 at 10:31:20AM -0700, Sridhar Samudrala wrote:
Make vhost scalable by creating a separate vhost thread per vhost
device. This provides better scaling across multiple guests and with
multiple interfaces in a guest.
Thanks for looking into this. An alternative approach is
to
On Wed, Mar 24, 2010 at 02:38:57PM +0200, Avi Kivity wrote:
On 03/17/2010 03:04 PM, Michael S. Tsirkin wrote:
This is port of vhost v6 patch set I posted previously to qemu-kvm, for
those that want to get good performance out of it :) This patchset needs
to be applied when qemu.git one gets
Avi Kivity a...@redhat.com writes:
On 03/02/2010 11:34 AM, Jernej Simončič wrote:
On Tuesday, March 2, 2010, 9:21:18, Chris Webb wrote:
I remember about a year ago, someone asserting on the list that -usbdevice
tablet was very CPU intensive even when not in use, and should be avoided if
On Sun, Apr 4, 2010 at 5:47 PM, Dan Johansson k...@dmj.nu wrote:
Hi,
I am new to this list and to KVM (and qemu) so please be gentle with me.
Up until now I have been running my virtualizing using VMWare-Server. Now I
want to try KVM due to some issues with the VMWare-Server and I am having
Looks like the tablet is set to 100 Hz polling rate. We may be able
to get away with 30 Hz or even less (ep_bInterval, in ms, in
hw/usb-wacom.c).
Changing the USB tablet polling interval from 10ms to 100ms in both
hw/usb-wacom.c and hw/usb-hid.c made no difference except the an increase
Bugs item #2933400, was opened at 2010-01-16 15:35
Message generated for change (Comment added) made by masc82
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2933400group_id=180599
Please note that this message will contain a full copy of the comment
On 04/04/2010 02:46 PM, Michael S. Tsirkin wrote:
On Wed, Mar 24, 2010 at 02:38:57PM +0200, Avi Kivity wrote:
On 03/17/2010 03:04 PM, Michael S. Tsirkin wrote:
This is port of vhost v6 patch set I posted previously to qemu-kvm, for
those that want to get good performance out of it :)
On 04/04/2010 05:25 PM, Paul Brook wrote:
Looks like the tablet is set to 100 Hz polling rate. We may be able
to get away with 30 Hz or even less (ep_bInterval, in ms, in
hw/usb-wacom.c).
Changing the USB tablet polling interval from 10ms to 100ms in both
hw/usb-wacom.c and
(re-adding list)
On 04/02/2010 07:01 PM, Marek Olszewski wrote:
Thanks for the fast response.
I'm trying to find the code that on a write to a guest page table
entry, will iterate over all shadow page table entries that map that
guest entry to update them. Can you point me to that code? I
On Sunday 04 April 2010 15.00:26 sudhir kumar wrote:
On Sun, Apr 4, 2010 at 5:47 PM, Dan Johansson k...@dmj.nu wrote:
Hi,
I am new to this list and to KVM (and qemu) so please be gentle with me.
Up until now I have been running my virtualizing using VMWare-Server.
Now I want to try KVM
Am 04.04.2010 20:02, schrieb Dan Johansson:
On Sunday 04 April 2010 15.00:26 sudhir kumar wrote:
On Sun, Apr 4, 2010 at 5:47 PM, Dan Johansson k...@dmj.nu wrote:
Hi,
I am new to this list and to KVM (and qemu) so please be gentle with me.
Up until now I have been running my virtualizing
The USB HID devices implement the SET_IDLE command, so the polling
interval will have no real effect on performance.
On a Linux guest (F12), I see 125 USB interrupts per second with no
mouse movement, so something is broken (on the guest or host).
Turns out to be a a bug in the UHCI
My guess is that the overhead you're seeing is entirely from the USB host
adapter having to wake up and check the transport descriptor lists. This
will only result in the guest being woken if a device actually responds
(as mentioned above it should not).
A quick profile on the host side
Hi,
(Below is explenation about the bug to who does`nt familier)
In the beggining I tried to make this code run with
qemu_bh() but the result was performence catastrophic
The reason is that the migration code just doesn`t built
to run at such high granularity, for example sutff like:
static
15 matches
Mail list logo
