From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/4] KVM: support VT-d device hotplug Date: Mon, 17 Nov 2008 12:28:43 +0200 Message-ID: <4921475B.5010403@redhat.com> References: <715D42877B251141A38726ABF5CABF2C018BE64962@pdsmsx503.ccr.corp.intel.com> <491FD45A.9070309@redhat.com> <715D42877B251141A38726ABF5CABF2C018BE64D26@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "'kvm@vger.kernel.org'" , "Kay, Allen M" , "Yang, Sheng" To: "Han, Weidong" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:52364 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754792AbYKQK2u (ORCPT ); Mon, 17 Nov 2008 05:28:50 -0500 In-Reply-To: <715D42877B251141A38726ABF5CABF2C018BE64D26@pdsmsx503.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: Han, Weidong wrote: >> Need a KVM_CAP_ to indicate this is available. >> >> > > KVM_ASSIGN_PCI_DEVICE and KVM_ASSIGN_IRQ don't need a KVM_CAP_xxx. Why do you need it for KVM_DEASSIGN_PCI_DEVICE? > > #define KVM_CAP_DEVICE_ASSIGNMENT 17 -- error compiling committee.c: too many arguments to function