From: Joerg Roedel <joro@8bytes.org>
To: "Jens Krehbiel-Gräther" <xen@jkg-it-services.de>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Joop Boonen <joop_boonen@web.de>,
"Huang2, Wei" <wei.huang2@amd.com>,
xen-devel@lists.xensource.com,
Leonardo Prosperi <leo.prosperi@gmail.com>
Subject: Re: IOMMU and AMD 890fx
Date: Thu, 3 Jun 2010 13:26:49 +0200 [thread overview]
Message-ID: <20100603112649.GG11162@8bytes.org> (raw)
In-Reply-To: <ee4a6ab6f04c6a03ad99464f01b6dabc@imap.hosting.jkg-it-services.net>
Hello Jens,
On Thu, Jun 03, 2010 at 12:51:23PM +0200, Jens Krehbiel-Gräther wrote:
>
> I got this answer from asrock support:
>
> <answer>
> So, I get more/final answer from Taiwan department:
>
> For H/W part:
> >From chipset spec, RD890(890FX) did support IOMMU.
> But IOMMU also need CPU to support.
Thats wrong. The IOMMU is a feature of the chipset northbridge and does
not need additional cpu support.
> Till now, AMD has no plan to support
> IOMMU on desktop CPU (AM3 socket).
There are AM3 boards out there with server a chipset that have it
enabled. Its no question of a socket.
> It only support with server CPU.
Also wrong. I have seen systems with desktop cpus that have IOMMU
enabled (Phenom X4 and Phenom X6).
> For BIOS part:
> AMD has removed IOMMU related registers.
Hard to believe. I have found people in the net who say that the ASUS
Crosshair IV mobo has IOMMU support in the BIOS. So if they can enable
it, asrock can do that too. Its just the BIOS which has to enable it
> So they say it is AMD's fault. :-(
I doubt that.
Joerg
next prev parent reply other threads:[~2010-06-03 11:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <z2n56ae3d9b1005081631sf3c31fafsb24b018c70b11b1a@mail.gmail.com>
2010-05-09 18:01 ` IOMMU and AMD 890fx Leonardo Prosperi
2010-05-10 4:43 ` Huang2, Wei
2010-05-10 6:16 ` Pasi Kärkkäinen
2010-05-10 6:38 ` Sander Eikelenboom
2010-06-03 4:07 ` Leonardo Prosperi
2010-06-03 8:19 ` Sander Eikelenboom
2010-06-03 8:53 ` Joop Boonen
2010-06-03 9:23 ` Sander Eikelenboom
2010-06-03 10:51 ` Jens Krehbiel-Gräther
2010-06-03 11:11 ` Sander Eikelenboom
2010-06-04 6:14 ` Huang2, Wei
2010-06-06 9:08 ` Jens Krehbiel-Gräther
[not found] ` <4C0FF901.6090708@amd.com>
2010-06-10 7:12 ` Jens Krehbiel-Gräther
2010-06-10 7:23 ` Sander Eikelenboom
2010-06-10 10:21 ` Jens Krehbiel-Gräther
2010-06-10 18:01 ` Jens Krehbiel-Gräther
2010-06-03 11:26 ` Joerg Roedel [this message]
2010-06-03 11:50 ` Sander Eikelenboom
2010-06-03 11:51 ` Andre Przywara
2010-06-03 13:41 ` Jens Krehbiel-Gräther
2010-06-03 15:05 ` Joerg Roedel
2010-06-10 18:49 ` Andrew Oakley
2010-06-10 19:12 ` Wei Huang
2010-06-10 19:15 ` Andrew Oakley
2010-06-14 11:08 ` Jens Krehbiel-Gräther
2010-06-14 11:30 ` Joerg Roedel
2010-06-14 13:49 ` Andre Przywara
2010-06-15 21:37 ` Joop Boonen
2010-06-15 22:40 ` Huang2, Wei
2010-06-16 22:09 ` Jens Krehbiel-Gräther
2010-06-17 13:14 ` Konrad Rzeszutek Wilk
2010-06-17 17:16 ` Wei Huang
2010-06-17 23:35 ` Jens Krehbiel-Gräther
2010-06-18 14:24 ` Sander Eikelenboom
2010-06-19 7:48 ` Jens Krehbiel-Gräther
2010-06-21 15:00 ` Jens Krehbiel-Gräther
2010-06-21 15:39 ` Joerg Roedel
2010-06-18 17:36 ` Huang2, Wei
2010-06-19 7:46 ` Jens Krehbiel-Gräther
[not found] ` <4C1A5882 <4C20E51D.1000406@jkg-it-services.de>
[not found] ` <EE335F95F28A664DB4A21289D2AA053B42F7C382@SAUSEXMBP01.amd.com>
2010-06-23 12:45 ` Jens Krehbiel-Gräther
2010-06-17 8:20 ` Jens Krehbiel-Gräther
2010-06-26 20:49 ` Joop Boonen
2010-07-06 14:54 ` Andrew Oakley
2010-07-06 15:03 ` Sander Eikelenboom
2010-07-07 7:47 ` Sander Eikelenboom
2010-07-07 10:37 ` Jens Krehbiel-Gräther
2010-07-07 13:53 ` Sander Eikelenboom
2010-07-07 18:28 ` Sander Eikelenboom
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=20100603112649.GG11162@8bytes.org \
--to=joro@8bytes.org \
--cc=joop_boonen@web.de \
--cc=leo.prosperi@gmail.com \
--cc=linux@eikelenboom.it \
--cc=wei.huang2@amd.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen@jkg-it-services.de \
/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;
as well as URLs for NNTP newsgroup(s).