From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC][PATCH 00/45] qemu-kvm: MSI layer rework for in-kernel irqchip support Date: Mon, 17 Oct 2011 14:18:33 +0200 Message-ID: <4E9C1D19.1060008@redhat.com> References: 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, Alexander Graf , Gerd Hoffmann , Isaku Yamahata To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32815 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750760Ab1JQMSn (ORCPT ); Mon, 17 Oct 2011 08:18:43 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 10/17/2011 11:27 AM, Jan Kiszka wrote: > As previously indicated, I was working for quite a while on a major > refactoring of the MSI "additions" we have in qemu-kvm to support > in-kernel irqchip, vhost and device assignment. This is now the outcome. > > I'm quite happy with it, things are still working (apparently), and the > invasiveness of KVM hooks into the MSI layer is significantly reduced. > Moreover, I was able to port the device assignment code over generic MSI > support, reducing the size of that file a bit further. > > Some further highlights: > - fix for HPET MSI support with in-kernel irqchip > - fully configurable MSI-X (allows 1:1 mapping for assigned devices) > - refactored KVM core API for device assignment and IRQ routing > > I'm sending the whole series in one chunk so that you can see what the > result will be. It's RFC as I bet that there are regressions included > and maybe still room left for improvements. Once all is fine (can be > broken up into multiple chunks for the merge), I would suggest patching > qemu-kvm first and then start with porting things over to upstream. Impressive patchset, let's merge this as quickly as possible. -- error compiling committee.c: too many arguments to function