From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Question on skip_emulated_instructions() Date: Thu, 08 Apr 2010 16:47:46 +0300 Message-ID: <4BBDDE82.4020009@redhat.com> References: <4BBAB46B.9010405@lab.ntt.co.jp> <4BBCC2C9.1040301@redhat.com> <4BBD6959.6080003@lab.ntt.co.jp> <4BBD82ED.9010105@redhat.com> <20100408071953.GI303@redhat.com> <4BBD8F74.8070401@lab.ntt.co.jp> <4BBD966D.7060801@redhat.com> <4BBD9E84.6040307@lab.ntt.co.jp> <4BBDC2B4.20203@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , kvm@vger.kernel.org, Marcelo Tosatti To: Yoshiaki Tamura Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49537 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756753Ab0DHNrv (ORCPT ); Thu, 8 Apr 2010 09:47:51 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 04/08/2010 04:42 PM, Yoshiaki Tamura wrote: > >> Yes, you can release the I/O from the iothread instead of the vcpu thread. >> You can make virtio_net_handle_tx() disable virtio notifications and >> initiate state sync and return, when state sync continues you can call the >> original virtio_net_handle_tx(). If the secondary takes over, it needs to >> call the original virtio_net_handle_tx() as well. >> > Agreed. Let me try it. > Meanwhile, I'll post what I have done including the hack preventing > rip to proceed. > I would appreciate if you could comment on that too, to keep things in > a good direction. > Certainly. -- error compiling committee.c: too many arguments to function