From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: iommu external module Date: Thu, 02 Oct 2008 15:45:33 +0300 Message-ID: <48E4C26D.6030608@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: KVM list Return-path: Received: from mx2.redhat.com ([66.187.237.31]:43182 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752209AbYJBMph (ORCPT ); Thu, 2 Oct 2008 08:45:37 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id m92CjbhZ014723 for ; Thu, 2 Oct 2008 08:45:37 -0400 Sender: kvm-owner@vger.kernel.org List-ID: When userspace support for device assignment is merged, we will finally have full support for device assignment. Unfortunately, many users won't be able to test or use device assignment, since very few actually run development kernels. The first stable kernel with enough iommu support for kvm will be 2.6.28, released in about three months, and distros are even further away. We can fix this fairly simply by having an external module for the iommus, much like kvm itself. I don't think it should be too difficult, and it will provide a lot of testing to us, and important functionality for our users. Anyone willing to pick this up? -- error compiling committee.c: too many arguments to function