From: Chris Friesen <chris.friesen@genband.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org
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 [thread overview]
Message-ID: <4F593792.1070909@genband.com> (raw)
In-Reply-To: <4F56E728.8020506@genband.com>
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
next prev parent reply other threads:[~2012-03-08 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 4:42 trying to figure out why VT-d isn't working on my kernel Chris Friesen
2012-03-08 22:49 ` Chris Friesen [this message]
[not found] ` <4F593792.1070909-b7o/lNNmKxtBDgjK7y7TUQ@public.gmane.org>
2012-03-14 17:48 ` trying to figure out why VT-d isn't working on my kernel -- solved Chris Wright
2012-03-14 17:48 ` Chris Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F593792.1070909@genband.com \
--to=chris.friesen@genband.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.