From: Chris Wright <chrisw@sous-sol.org>
To: Prasad Joshi <P.G.Joshi@student.reading.ac.uk>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Query on IOMMU
Date: Tue, 21 Dec 2010 08:15:02 -0800 [thread overview]
Message-ID: <20101221161502.GE15023@sequoia.sous-sol.org> (raw)
In-Reply-To: <000DF292CEBFBB41A633359D615F1514022A5F7C@DB2PRD0103MB011.eurprd01.prod.exchangelabs.com>
* Prasad Joshi (P.G.Joshi@student.reading.ac.uk) wrote:
> I am facing a problem with enabling the IOMMU.
>
> Dec 21 15:50:57 prasad-kvm kernel: [ 0.000000] Aperture pointing to e820 RAM. Ignoring.
> Dec 21 15:50:57 prasad-kvm kernel: [ 0.000000] Your BIOS doesn't leave a aperture memory hole
> Dec 21 15:50:57 prasad-kvm kernel: [ 0.000000] Please enable the IOMMU option in the BIOS setup
>
> Dec 21 15:50:57 prasad-kvm kernel: [ 2.790913] pci 0000:01:05.0: Firmware left e100 interrupts enabled; disabling
> Dec 21 15:50:57 prasad-kvm kernel: [ 2.791941] pci 0000:00:00.2: PCI INT A -> GSI 55 (level, low) -> IRQ 55
> Dec 21 15:50:57 prasad-kvm kernel: [ 2.792775] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40
> Dec 21 15:50:57 prasad-kvm kernel: [ 2.800989] AMD-Vi: Lazy IO/TLB flushing enabled
>
>
> I have enabled IOMMU in the BIOS, but I am not sure why it is still asking to enabled IOMMU in BIOS. Do I need to worry about this?
It's unfortunate wording. It's telling you that the GART is missing,
which is fine because you have an IOMMU.
> Besides I don't see the DMAR message similar to the one mentioned on the link
> http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
That wiki page is specific to Intel VT-d. You have an AMD box with IOMMU,
so all looks fine.
Are you interested in using the IOMMU to do direct PCI device assignment
to a guest?
thanks,
-chris
next prev parent reply other threads:[~2010-12-21 16:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 16:00 Query on IOMMU Prasad Joshi
2010-12-21 16:15 ` Chris Wright [this message]
2010-12-21 16:54 ` Prasad Joshi
2010-12-21 17:12 ` Chris Wright
2010-12-21 17:39 ` Prasad Joshi
2010-12-21 18:33 ` Chris Wright
[not found] ` <000DF292CEBFBB41A633359D615F1514022A5FF4@DB2PRD0103MB011.eurprd01.prod.exchangelabs.com>
2010-12-21 19:22 ` Prasad Joshi
2010-12-21 19:29 ` Chris Wright
2010-12-21 19:56 ` Prasad Joshi
2010-12-21 20:01 ` Chris Wright
2010-12-21 20:06 ` Prasad Joshi
2010-12-22 9:06 ` [PATCH] pci-stub: ignore zero-length id parameters Tejun Heo
2010-12-23 20:54 ` Jesse Barnes
2010-12-21 20:34 ` Query on IOMMU Chris Wright
2010-12-22 13:16 ` Prasad Joshi
2010-12-22 13:35 ` Prasad Joshi
2010-12-22 14:56 ` Chris Wright
2010-12-22 14:54 ` Chris Wright
2010-12-22 15:02 ` Prasad Joshi
2010-12-22 15:22 ` Chris Wright
2010-12-22 15:46 ` Prasad Joshi
2010-12-22 16:34 ` Prasad Joshi
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=20101221161502.GE15023@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=P.G.Joshi@student.reading.ac.uk \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox