From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Cc: Roberto Luongo <rluongo@ready.it>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] AMD/guest_iommu: Disable guest iommu support
Date: Mon, 6 Oct 2014 10:11:06 +0100 [thread overview]
Message-ID: <54325CAA.80909@citrix.com> (raw)
In-Reply-To: <5432681F020000780003C541@mail.emea.novell.com>
On 06/10/14 08:59, Jan Beulich wrote:
>>>> On 06.10.14 at 08:46, <Suravee.Suthikulpanit@amd.com> wrote:
>> The function guest_iommu_set_base() was added by Wei before my time. I
>> checked the log and didn't see the evidence that this code has ever been
>> used. Do you remember why he added this code to begin with, and how this
>> was planned to be used?
> The plan here clearly was to allow guests to see a virtual IOMMU,
> and the setting of the respective base address would then be
> a requirement for tool stack and/or virtual firmware to set up the
> environment for the guest.
>
> Jan
>
The commit which introduces the virtual IOMMU (c/s 4547137c3) indicates
that a virtual IOMMU is necessary for correct functioning of ATS-capable
guest device drivers using PASID or PRI, in passthrough.
~Andrew
prev parent reply other threads:[~2014-10-06 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 14:02 [PATCH] AMD/guest_iommu: Disable guest iommu support Andrew Cooper
2014-10-02 14:08 ` Andrew Cooper
2014-10-02 14:50 ` Jan Beulich
2014-10-02 15:16 ` Konrad Rzeszutek Wilk
2014-10-06 6:46 ` Suravee Suthikulpanit
2014-10-06 7:59 ` Jan Beulich
2014-10-06 9:11 ` Andrew Cooper [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=54325CAA.80909@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=rluongo@ready.it \
--cc=xen-devel@lists.xen.org \
/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.