From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [RFC][PATCH 11/45] msi: Factor out delivery hook Date: Mon, 17 Oct 2011 15:41:36 +0200 Message-ID: <20111017134135.GC6406@redhat.com> References: <4E9C09E7.2010106@redhat.com> <4E9C0E6C.2070809@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , Marcelo Tosatti , "kvm@vger.kernel.org" , Alex Williamson , "qemu-devel@nongnu.org" To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4424 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753253Ab1JQNke (ORCPT ); Mon, 17 Oct 2011 09:40:34 -0400 Content-Disposition: inline In-Reply-To: <4E9C0E6C.2070809@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Oct 17, 2011 at 01:15:56PM +0200, Jan Kiszka wrote: > On 2011-10-17 12:56, Avi Kivity wrote: > > On 10/17/2011 11:27 AM, Jan Kiszka wrote: > >> So far we deliver MSI messages by writing them into the target MMIO > >> area. This reflects what happens on hardware, but imposes some > >> limitations on the emulation when introducing KVM in-kernel irqchip > >> models. For those we will need to track the message origin. > > > > Why do we need to track the message origin? Emulated interrupt remapping? > > The origin holds the routing cache which we need to track if the message > already has a route (and that without searching long lists) and to > update that route instead of add another one. Hmm, yes, but if the device does stl_phys or something like this, it won't work with irqchip, will it? And it should, ideally. -- MST