From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Friesen Subject: Re: trying to figure out why VT-d isn't working on my kernel -- solved Date: Thu, 08 Mar 2012 16:49:54 -0600 Message-ID: <4F593792.1070909@genband.com> References: <4F56E728.8020506@genband.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F56E728.8020506@genband.com> Sender: linux-kernel-owner@vger.kernel.org To: Linux Kernel Mailing List , David Woodhouse , iommu@lists.linux-foundation.org List-Id: iommu@lists.linux-foundation.org On 03/06/2012 10:42 PM, Chris Friesen wrote: > Hi, > > I've got a current (pulled today) kernel running on a Xeon E5-2648L CPU > on an Intel motherboard, and I'm trying to get VT-d working without much success. > > lspci -vv (version 3.1.4) doesn't show anything related to IOV. > (Full output below.) Since I know the I350 devices are capable of virtual > functions, am I correct in assuming it's something similar to the situation > described at https://bugzilla.redhat.com/show_bug.cgi?id=652210 and there is > a problem with my BIOS? Based on comment 15 there, the fact that all > the DevCtl2 lines show "ARIFwd-" seems interesting. > > > Among other things, I've enabled the following in the kernel config: > > CONFIG_DMAR_TABLE=y > CONFIG_INTEL_IOMMU=y > CONFIG_INTEL_IOMMU_DEFAULT_ON=y > CONFIG_PCI_MSI=y > CONFIG_PCI_STUB=y > CONFIG_PCI_IOV=y Just in case anyone else runs into this, it turns out that enabling CONFIG_PCI_MMCONFIG allowed the virtual functions to be detected and configured. Chris -- Chris Friesen Software Developer GENBAND chris.friesen@genband.com www.genband.com