From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 2/2] KVM: Device assignemnt with VT-d Date: Sun, 24 Aug 2008 13:00:34 +0300 Message-ID: <48B13142.3010306@qumranet.com> References: <1218118487-7657-1-git-send-email-benami@il.ibm.com> <200808231427.42578.amit.shah@qumranet.com> <48AFD852.8040604@qumranet.com> <200808231513.19684.amit.shah@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Ben-Ami Yassour , kvm@vger.kernel.org, Muli Ben-Yehuda , weidong.han@intel.com, "Kay, Allen M" To: Amit Shah Return-path: Received: from il.qumranet.com ([212.179.150.194]:28787 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751041AbYHXKAg (ORCPT ); Sun, 24 Aug 2008 06:00:36 -0400 In-Reply-To: <200808231513.19684.amit.shah@qumranet.com> Sender: kvm-owner@vger.kernel.org List-ID: Amit Shah wrote: >> That only detects if the headers have the flag, not if the kernel >> actually supports it (and whether there is an iommu in the host). We >> need run-time detection. >> > > Which means we expose KVM_CAP_IOMMU only if one was detected? Yes. > How to do this > correctly? > I don't know. Can't the VT-d api tell you if an iommu exists? -- error compiling committee.c: too many arguments to function