From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [RFC] create a single workqueue for each vm to update vm irq routing table Date: Tue, 26 Nov 2013 14:13:25 +0100 Message-ID: <52949E75.6050608@redhat.com> References: <52949847.6020908@redhat.com> <20131126125610.GM959@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Zhanghaoyu (A)" , KVM , "qemu-devel@nongnu.org" , "Michael S. Tsirkin" , Eric Blake , Luonengjun , "Huangweidong (C)" , "Jinxin (F)" , Zanghongyong To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:18108 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751083Ab3KZNNz (ORCPT ); Tue, 26 Nov 2013 08:13:55 -0500 In-Reply-To: <20131126125610.GM959@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Il 26/11/2013 13:56, Gleb Natapov ha scritto: > > I don't think a workqueue is even needed. You just need to use call_rcu > > to free "old" after releasing kvm->irq_lock. > > > > What do you think? > > It should be rate limited somehow. Since it guest triggarable guest may cause > host to allocate a lot of memory this way. True, though if I understand Zhanghaoyu's proposal a workqueue would be even worse. Paolo