From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH] MSI / MSIX injection for Xen HVM Date: Thu, 01 Mar 2012 15:03:26 +0100 Message-ID: <4F4F81AE.9080503@redhat.com> References: <1330536077.10387.57.camel@leeds.uk.xensource.com> <4F4E64B5.5080900@siemens.com> <1330597236.10387.70.camel@leeds.uk.xensource.com> <4F4F5BF5.6010206@siemens.com> <1330602678.10387.73.camel@leeds.uk.xensource.com> <4F4F71F0.4070109@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Stefano Stabellini Cc: Jan Kiszka , xen-devel , "Wei Liu (Intern)" , QEMU-devel List-Id: xen-devel@lists.xenproject.org Il 01/03/2012 15:06, Stefano Stabellini ha scritto: >> > This is not a NACK, but I can't help asking. Perhaps the fake Xen >> > interrupt controller is a bit too simplistic? You can add a memory >> > region corresponding to the APICs and trap writes in that region. >> > Writes coming from QEMU are MSIs and can be injected to the hypervisor, >> > writes coming from the VM will be trapped by Xen before going out to QEMU. > > That is a good point actually: we already have lapic emulation in Xen, > it makes sense to have apic-msi in Xen too. > We would still need the changes to msi_notify and msix_notify though. Why? The stores would just go to the Xen interrupt controller MMIO area which then does the xc_hvm_inject_msi. Paolo