From: Gregory Woodbury <redwolfe@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CONFIG_IOMMU_SUPPORT???
Date: Wed, 24 Aug 2011 01:09:27 -0400 [thread overview]
Message-ID: <CAJoOjx82X9wfu0MTsvFi8+_ozkv6QjQKr4=wDOTkhdRM1eQ0ng@mail.gmail.com> (raw)
In-Reply-To: <CAE1pOi3BOOWwoEe=oGC0Feyi9fcFS7j7Lz2m6zuXCKy7i=DZ6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
On Wed, Aug 24, 2011 at 12:18 AM, Hilco Wijbenga
<hilco.wijbenga@gmail.com>wrote:
> On 23 August 2011 20:38, Mark Knecht <markknecht@gmail.com> wrote:
> > Hi all,
> > Can someone point me toward somehow enabling CONFIG_IOMMU_SUPPORT?
> > It is apparently a kernel config option no required by
> > virtualbox-drivers but I'm not finding it in the 3.0.3 kernel. I
> > suspect there's something else I need to enable before this option
> > becomes available? Unfortunately I haven't been able to Google what I
> > need to do to find it.
>
IOMMU_SUPPORT is a derived value that becomes set when any of the various
IOMMU
devices are enabled. I enabled the IBM "CALGARY" IOMMU and the AMD IOMMU to
get the
VBox build to stop complaining.
I was also getting complaints about PCI_STUB support from VBox, but the
running VMs don't
need the vboxpcistub.ko driver to work.
--
G.Wolfe Woodbury
[-- Attachment #2: Type: text/html, Size: 1295 bytes --]
next prev parent reply other threads:[~2011-08-24 5:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 3:38 [gentoo-user] CONFIG_IOMMU_SUPPORT??? Mark Knecht
2011-08-24 4:10 ` Dale
2011-08-24 4:18 ` Hilco Wijbenga
2011-08-24 5:09 ` Gregory Woodbury [this message]
2011-08-24 17:55 ` Mark Knecht
2011-08-24 18:58 ` Hilco Wijbenga
2011-08-24 19:13 ` Mark Knecht
2011-08-24 19:55 ` Paul Hartman
2011-08-24 20:10 ` Mark Knecht
2011-08-25 6:56 ` Joost Roeleveld
2011-08-24 17:13 ` Michael Orlitzky
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='CAJoOjx82X9wfu0MTsvFi8+_ozkv6QjQKr4=wDOTkhdRM1eQ0ng@mail.gmail.com' \
--to=redwolfe@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox