From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Friesen Subject: 2.6.27, kvm-kmod, and PCI device assignment Date: Mon, 12 Sep 2011 11:56:46 -0600 Message-ID: <4E6E47DE.6080602@genband.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org, Avi Kivity , mtosatti@redhat.com, David Ahern Return-path: Received: from exprod7og119.obsmtp.com ([64.18.2.16]:40487 "EHLO exprod7og119.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751618Ab1ILR5Q (ORCPT ); Mon, 12 Sep 2011 13:57:16 -0400 Sender: kvm-owner@vger.kernel.org List-ID: Hi, I've been away a bit but I'm now coming back to this issue. Is it expected that the kvm-kmod modules will allow PCI device assignment (aka VT-d) with older kernels? If so, then is there an expectation for how far back it will be supported? I haven't seen a clear statement of this anywhere, and I think David was interested in this as well. Looking at the instructions at "http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM", step 4 is to unbind the device from the host using the "pci_stub" functionality. That code was only added to mainline for 2.6.29-rc1, so it seems like extra work will be needed for 2.6.28 and earlier. Thanks, Chris -- Chris Friesen Software Developer GENBAND chris.friesen@genband.com www.genband.com