From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC][PATCH 11/45] msi: Factor out delivery hook Date: Mon, 17 Oct 2011 14:14:00 +0200 Message-ID: <4E9C1C08.9040907@redhat.com> References: <4E9C09E7.2010106@redhat.com> <4E9C0E6C.2070809@siemens.com> <4E9C100A.2070705@redhat.com> <4E9C1184.4040908@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]:32163 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752723Ab1JQMOG (ORCPT ); Mon, 17 Oct 2011 08:14:06 -0400 In-Reply-To: <4E9C1184.4040908@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/17/2011 01:29 PM, Jan Kiszka wrote: > >> > >> APIC is x86-specific, MSI is not. I think Xen will also want to make use > >> of this hook. I originally though of using it for the KVM in-kernel > >> models as well, but I will now establish a callback at APIC-level > >> (upstream will look differently from qemu-kvm in this regard). > >> > > > > But you still have to handle it the the platform interrupt controller > > (or whatever processes msi messages) since you can still DMA there. So > > you don't get away from doing it there anyway. > > Right, but that's the slow path (which is still handled - on x86 via the > MMIO region the APIC still maintains). > It's handled by caching and immediately uncaching the MSIMessage/kvm route relationship? Can you post a git tree? It will be easier for me to understand the whole thing this way. -- error compiling committee.c: too many arguments to function