From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, Christian Tramnitz <chris.ace@gmx.net>
Subject: Re: Re: VT-d on Asus P7P55D-Evo: IOMMU not supported
Date: Fri, 9 Apr 2010 09:48:18 -0400 [thread overview]
Message-ID: <20100409134818.GA26880@phenom.dumpdata.com> (raw)
In-Reply-To: <20100401055024.GC1878@reaktio.net>
On Thu, Apr 01, 2010 at 08:50:24AM +0300, Pasi Kärkkäinen wrote:
> On Thu, Apr 01, 2010 at 12:29:03AM +0200, Christian Tramnitz wrote:
> > 31.03.2010 22:51, Mark Hurenkamp wrote:
> > > Asus doesn't seem to pay much attention to VT-d issues with their P55
> > > boards, i couldn't find any indication that they are working on it.
> > > I tried to submit a tech support question, but it requires a serial number,
> > > which i seem to be unable to locate on the board.
> >
> > Even if you find the serial and open the support case there will be no
> > meaningful answer just "Linux is not supported". Been there, done that....
> >
>
> Please see here:
> http://wiki.xensource.com/xenwiki/XenPCIpassthrough
>
> Especially this:
> "Intel developers also want to know about broken IOMMU/VT-d BIOS implementations, see this email: http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00841.html, so let them know all the details about your hardware and software if you have broken BIOS. "
This just got posted on LKML that might shed the light on why certain
motherboards have VT-d working i7 but not with i5 CPUs:
(https://lists.linux-foundation.org/pipermail/iommu/2010-April/002268.html):
"
When using iommu_domain_alloc with the Intel iommu, the domain address width
is always initialized to 48 bits (agaw 2). This domain->agaw value is then
used by pfn_to_dma_pte to (always) build a 4 level page table. However, not
all systems support iommu width of 48 or 4 level page tables. In particular,
the Core i5-660 and i5-670 support an address width of 36 bits (not 39!), an
agaw of only 1, and only 3 level page tables.
My patch delays the domain initialization until the first iommu_attach_device,
...
prev parent reply other threads:[~2010-04-09 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 20:57 VT-d on Asus P7P55D-Evo: IOMMU not supported Mark Hurenkamp
2010-03-31 5:26 ` Cui, Dexuan
2010-03-31 20:51 ` Mark Hurenkamp
2010-03-31 21:34 ` Pasi Kärkkäinen
2010-03-31 22:29 ` Christian Tramnitz
2010-04-01 5:50 ` Pasi Kärkkäinen
2010-04-09 13:48 ` Konrad Rzeszutek Wilk [this message]
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=20100409134818.GA26880@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=chris.ace@gmx.net \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/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.