xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jens Krehbiel-Gräther" <xen@jkg-it-services.de>
To: "Huang2, Wei" <Wei.Huang2@amd.com>
Cc: "Przywara, Andre" <Andre.Przywara@amd.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Leonardo Prosperi <leo.prosperi@gmail.com>,
	Joerg Roedel <joro@8bytes.org>,
	Eikelenboom <linux@eikelenboom.it>,
	Andrew Oakley <andrew@ado.is-a-geek.net>,
	Joop Boonen <joop_boonen@web.de>
Subject: Re: IOMMU and AMD 890fx
Date: Thu, 17 Jun 2010 10:20:46 +0200	[thread overview]
Message-ID: <4C19DADE.7030009@jkg-it-services.de> (raw)
In-Reply-To: <3399D2269986104B959D31B7E919313C3D10B465@SAUSEXMBP01.amd.com>

Am 16.06.2010 00:40, schrieb Huang2, Wei:
> IOMMU doesn't require CPU support. It is a feature of chipset. I think Biostart means SVM feature of CPU, which is supported by Phenom II.
>
>
> -Wei

Perhaps you should tell this asrock. Today I got an answer from asrock 
support:

<asrock-support>
Sorry for lat reply. Taiwan was still checking this issue. And they told us:

Again IOMMU also need CPU to support.
Till now, AMD has no plan to support IOMMU on desktop CPU (AM3 socket).
Also "IOMMU" not list on our 890FX Deluxe3 specification
Please 890FX Deluxe3 link:
http://www.asrock.com/mb/overview.asp?Model=890FX%20Deluxe3

In feature, AMD release that CPU, we will borrow it, and test it.
Any news will update to you.
Thanks your mail.

Best regards,


ASRock Support
</asrock-support>


Jens

  parent reply	other threads:[~2010-06-17  8:20 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
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 [this message]
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=4C19DADE.7030009@jkg-it-services.de \
    --to=xen@jkg-it-services.de \
    --cc=Andre.Przywara@amd.com \
    --cc=Wei.Huang2@amd.com \
    --cc=andrew@ado.is-a-geek.net \
    --cc=joop_boonen@web.de \
    --cc=joro@8bytes.org \
    --cc=leo.prosperi@gmail.com \
    --cc=linux@eikelenboom.it \
    --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 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).