From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC][PATCH 17/45] qemu-kvm: Track MSIRoutingCache in KVM routing table Date: Mon, 17 Oct 2011 13:13:57 +0200 Message-ID: <4E9C0DF5.8050209@redhat.com> References: <76a09d29c3ff24930642b36302ce41dd96824ca1.1318843693.git.jan.kiszka@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm@vger.kernel.org, Alex Williamson , "Michael S. Tsirkin" , qemu-devel@nongnu.org To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35764 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751414Ab1JQLOD (ORCPT ); Mon, 17 Oct 2011 07:14:03 -0400 In-Reply-To: <76a09d29c3ff24930642b36302ce41dd96824ca1.1318843693.git.jan.kiszka@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/17/2011 11:27 AM, Jan Kiszka wrote: > Keep a link from the internal KVM routing table to potential MSI routing > cache entries. The link is used so far whenever the entry is dropped to > invalidate the cache content. It will allow us to build MSI routing > entries on demand and flush existing ones on table overflow. > Does this not require a destructor for MSIRoutingCache? -- error compiling committee.c: too many arguments to function