Re: [kvm-devel] [patch 00/13] RFC: split the global mutex

2008-04-20 Thread Avi Kivity
Marcelo Tosatti wrote: > On Sun, Apr 20, 2008 at 02:16:52PM +0300, Avi Kivity wrote: > >>> The iperf numbers are pretty good. Performance of UP guests increase >>> slightly but SMP >>> is quite significant. >>> >> I expect you're seeing contention induced by memcpy()s and inefficient >>

Re: [kvm-devel] [patch 00/13] RFC: split the global mutex

2008-04-20 Thread Marcelo Tosatti
On Sun, Apr 20, 2008 at 02:16:52PM +0300, Avi Kivity wrote: > >The iperf numbers are pretty good. Performance of UP guests increase > >slightly but SMP > >is quite significant. > > I expect you're seeing contention induced by memcpy()s and inefficient > emulation. With the dma api, I expect the

Re: [kvm-devel] [patch 00/13] RFC: split the global mutex

2008-04-20 Thread Avi Kivity
Marcelo Tosatti wrote: > Introduce QEMUDevice, making the ioport/iomem->device relationship visible. > > At the moment it only contains a lock, but could be extended. > > With it the following is possible: > - vcpu's to read/write via ioports/iomem while the iothread is working on > som

[kvm-devel] [patch 00/13] RFC: split the global mutex

2008-04-17 Thread Marcelo Tosatti
Introduce QEMUDevice, making the ioport/iomem->device relationship visible. At the moment it only contains a lock, but could be extended. With it the following is possible: - vcpu's to read/write via ioports/iomem while the iothread is working on some unrelated device, or just copying