From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH v2 0/9] qemu-kvm: Clean up and enhance MSI irqchip support Date: Wed, 27 Apr 2011 16:21:55 +0200 Message-ID: <4DB82683.3030300@siemens.com> References: <4DB7DC11.1010308@redhat.com> <4DB7DC8B.1030402@siemens.com> <4DB7DE7A.4000608@redhat.com> <4DB7FC21.8000203@siemens.com> <4DB80826.5010706@redhat.com> <4DB81AA4.9060904@siemens.com> <4DB81C8F.1070205@redhat.com> <4DB8201C.1000607@siemens.com> <20110427140230.GL15788@redhat.com> <4DB823BC.7050604@siemens.com> <20110427141412.GN15788@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Marcelo Tosatti , "kvm@vger.kernel.org" To: "Michael S. Tsirkin" Return-path: Received: from thoth.sbs.de ([192.35.17.2]:18034 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750727Ab1D0OWC (ORCPT ); Wed, 27 Apr 2011 10:22:02 -0400 In-Reply-To: <20110427141412.GN15788@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2011-04-27 16:14, Michael S. Tsirkin wrote: > On Wed, Apr 27, 2011 at 04:10:04PM +0200, Jan Kiszka wrote: >>> Another issue is the reverse: regular memory address can be put >>> in the MSIX/MSI field and the result should be a regular memory >>> write. >> >> Yes, that's a separate issue: Requests issued by the CPUs have to be >> told apart from those issued by devices. > > Seems to be the reverse: in qemu msi writes are implemented as regular > writes so you can stick a non msi address there and it works. > in kvm they are handled differently and that's broken ... Right, that's _also_ an issue. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux