xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Tim Deegan <tim@xen.org>,
	Xiantao Zhang <xiantao.zhang@intel.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH 2/3] amd-iommu: disable iommu_hap_pt_share with AMD IOMMUs
Date: Tue, 8 Apr 2014 17:39:08 +0200	[thread overview]
Message-ID: <5344181C.3060103@citrix.com> (raw)
In-Reply-To: <5343D4FC0200007800006788@nat28.tlf.novell.com>

On 08/04/14 10:52, Jan Beulich wrote:
>>>> On 07.04.14 at 18:02, <roger.pau@citrix.com> wrote:
>> --- a/xen/drivers/passthrough/amd/iommu_init.c
>> +++ b/xen/drivers/passthrough/amd/iommu_init.c
>> @@ -1255,6 +1255,13 @@ int __init amd_iommu_init(void)
>>      if ( iterate_ivrs_mappings(amd_iommu_setup_device_table) != 0 )
>>          goto error_out;
>>  
>> +    /*
>> +     * Disable sharing HAP page tables with AMD IOMMU,
>> +     * since it only supports p2m_ram_rw, and this would
>> +     * prevent doing IO to/from mapped grant frames.
>> +     */
>> +    iommu_hap_pt_share = 0;
>> +
> 
> I guess at the very least when the option was specified on the
> command line you should issue a warning, or perhaps even stay
> away from enforcing this.

I think we should enforce it even if the user has specified
sharept=true, or else we need to gate the
XENFEAT_hvm_gntmap_supports_iommu feature. Printing a Warning in this
case (user trying to enforce sharept on AMD IOMMU) seems OK to me.

Roger.

  parent reply	other threads:[~2014-04-08 15:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 16:02 [PATCH 0/3] Fix grant map/unmap with auto-translated guests Roger Pau Monne
2014-04-07 16:02 ` [PATCH 1/3] iommu: set correct IOMMU entries when iommu_hap_pt_share == 0 Roger Pau Monne
2014-04-07 16:49   ` Konrad Rzeszutek Wilk
2014-04-08  8:30   ` Jan Beulich
2014-04-08  9:19     ` Roger Pau Monné
2014-04-08  9:55       ` Jan Beulich
2014-04-08 14:12     ` Tim Deegan
2014-04-08 15:15       ` Roger Pau Monné
2014-04-08 15:29         ` Jan Beulich
2014-04-13 20:27         ` Tim Deegan
2014-04-16 14:36     ` Roger Pau Monné
2014-04-16 14:41       ` Jan Beulich
2014-04-07 16:02 ` [PATCH 2/3] amd-iommu: disable iommu_hap_pt_share with AMD IOMMUs Roger Pau Monne
2014-04-07 16:51   ` Konrad Rzeszutek Wilk
2014-04-07 16:54     ` George Dunlap
2014-04-08  7:29       ` Roger Pau Monné
2014-04-08  8:52   ` Jan Beulich
2014-04-08 14:16     ` Tim Deegan
2014-04-08 14:36       ` Jan Beulich
2014-04-08 15:39     ` Roger Pau Monné [this message]
2014-04-07 16:02 ` [PATCH 3/3] xen: expose that grant table mappings update the IOMMU Roger Pau Monne
2014-04-08  8:34   ` Ian Campbell
2014-04-08  8:56     ` Jan Beulich
2014-04-08  8:58       ` Ian Campbell
2014-04-08  9:53         ` Jan Beulich
2014-04-08  9:57           ` Ian Campbell
2014-04-08 10:05             ` Jan Beulich
2014-04-08 10:26               ` Ian Campbell
2014-04-08 10:31                 ` Jan Beulich

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=5344181C.3060103@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xiantao.zhang@intel.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).