From: Hack <mistermyster@outlook.com>
To: xen-devel@lists.xensource.com
Subject: Re: AMD Ryzen Support
Date: Sat, 10 Jun 2017 17:47:23 +0200 [thread overview]
Message-ID: <ohh4a5$tbe$1@blaine.gmane.org> (raw)
In-Reply-To: <592EF08B020000780015E53E@prv-mh.provo.novell.com>
On 05/31/2017 04:34 PM, Jan Beulich wrote:
>>>> On 31.05.17 at 16:08, <mistermyster@outlook.com> wrote:
>> On 05/31/2017 10:59 AM, Jan Beulich wrote:
>>>>>> On 30.05.17 at 13:27, <mistermyster@outlook.com> wrote:
>>>> What about AMD Ryzen iommu Support? Is there any roadmap?
>>>
>>> Mind being a little more specific? What features are you looking for?
>>>
>>> It would, btw, also help if you Cc-ed the maintainer(s) of the code
>>> you inquire about.
>>>
>> PCI passthrough.
>
> Excuse me? The question really is what AMD IOMMU support you
> are _missing_. I'm sure you're aware there is support for it there
> in general, so when posting on xen-devel I think we can expect
> you to be a little more precise (in technical terms) with your
> question.
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
>
Well I am wondering if there is any support of :
1. IOMMU isolation between Groups;
2. IOMMU isolation device into Groups;
3. IOMMU for PCI passthru to PV Linux guests;
4. PCIe ACS support;
5. Vfio-Pci support.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-06-10 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 11:27 AMD Ryzen Support Hack
2017-05-31 8:59 ` Jan Beulich
2017-05-31 14:08 ` Hack
2017-05-31 14:34 ` Jan Beulich
2017-06-10 15:47 ` Hack [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='ohh4a5$tbe$1@blaine.gmane.org' \
--to=mistermyster@outlook.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.