From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:41885) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S3464-0003bp-7m for qemu-devel@nongnu.org; Thu, 01 Mar 2012 06:23:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S345z-0006Ao-HI for qemu-devel@nongnu.org; Thu, 01 Mar 2012 06:22:55 -0500 Received: from thoth.sbs.de ([192.35.17.2]:31776) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S345z-0006AU-7R for qemu-devel@nongnu.org; Thu, 01 Mar 2012 06:22:51 -0500 Message-ID: <4F4F5BF5.6010206@siemens.com> Date: Thu, 01 Mar 2012 12:22:29 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <1330536077.10387.57.camel@leeds.uk.xensource.com> <4F4E64B5.5080900@siemens.com> <1330597236.10387.70.camel@leeds.uk.xensource.com> In-Reply-To: <1330597236.10387.70.camel@leeds.uk.xensource.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] MSI / MSIX injection for Xen HVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wei Liu Cc: xen-devel , QEMU-devel , Stefano Stabellini On 2012-03-01 11:20, Wei Liu wrote: >> However, you know that you miss those (uncommon) messages that are >> injected via DMA? They end up directly in apic_deliver_msi (where KVM >> will once pick them up as well). >> > > Thanks for pointing this out. However I cannot find apic_deliver_msi in > qemu-kvm or upstream qemu tree. I can only find apic_send_msi and > apic_deliver_irq, none of which seems to be KVM-specific. Can you please > give me some pointer on this? Yes, apic_send_msi. I was accidentally looking at my msi refactoring tree. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH] MSI / MSIX injection for Xen HVM Date: Thu, 01 Mar 2012 12:22:29 +0100 Message-ID: <4F4F5BF5.6010206@siemens.com> References: <1330536077.10387.57.camel@leeds.uk.xensource.com> <4F4E64B5.5080900@siemens.com> <1330597236.10387.70.camel@leeds.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1330597236.10387.70.camel@leeds.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: xen-devel , QEMU-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 2012-03-01 11:20, Wei Liu wrote: >> However, you know that you miss those (uncommon) messages that are >> injected via DMA? They end up directly in apic_deliver_msi (where KVM >> will once pick them up as well). >> > > Thanks for pointing this out. However I cannot find apic_deliver_msi in > qemu-kvm or upstream qemu tree. I can only find apic_send_msi and > apic_deliver_irq, none of which seems to be KVM-specific. Can you please > give me some pointer on this? Yes, apic_send_msi. I was accidentally looking at my msi refactoring tree. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux