From: Wei Huang <wei.huang2@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Andrew Oakley <andrew@ado.is-a-geek.net>
Subject: Re: AMD IOMMU status
Date: Fri, 8 Jan 2010 11:17:53 -0600 [thread overview]
Message-ID: <4B4768C1.3060607@amd.com> (raw)
In-Reply-To: <C76CBCF4.5A7B%keir.fraser@eu.citrix.com>
Xen's support for AMD IOMMU is up-to-date. You need 800 chipset and a
working BIOS to use IOMMU. There will be an option in BIOS to turn it
on/off. IOMMU feature doesn't require special support from CPUs.
Best,
-Wei
Keir Fraser wrote:
> AMD are actively working on it. Most recent committed patch specifically for
> AMD IOMMU support was mid December.
>
> -- Keir
>
> On 08/01/2010 00:10, "Andrew Oakley" <andrew@ado.is-a-geek.net> wrote:
>
>
>> There seem to be a lot of commits and discussion about VT-d support,
>> however there seems to be very little activity regarding device
>> passthrough using the AMD IOMMU. Is it "done", lacking a mantainer,
>> or never going to work?
>>
>> A quick google showed that 8 series chipsets for desktop are likely to
>> be released very soon (looks like it is only the 8 series that have the
>> relevant IOMMU). I'm not sure if any other hardware is required for
>> passthrough, does anyone know if there is anything special about the
>> CPU?
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
prev parent reply other threads:[~2010-01-08 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 0:10 AMD IOMMU status Andrew Oakley
2010-01-08 10:44 ` Keir Fraser
2010-01-08 17:17 ` Wei Huang [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=4B4768C1.3060607@amd.com \
--to=wei.huang2@amd.com \
--cc=andrew@ado.is-a-geek.net \
--cc=keir.fraser@eu.citrix.com \
--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.