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,
	Xiantao Zhang <xiantao.zhang@intel.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH v2 3/4] amd-iommu: disable iommu_hap_pt_share with AMD IOMMUs
Date: Wed, 23 Apr 2014 16:31:14 +0200	[thread overview]
Message-ID: <5357CEB2.9070103@citrix.com> (raw)
In-Reply-To: <5357B767020000780000B5FB@nat28.tlf.novell.com>

On 23/04/14 12:51, Jan Beulich wrote:
>>>> On 23.04.14 at 12:04, <roger.pau@citrix.com> wrote:
>> On 23/04/14 11:57, Jan Beulich wrote:
>>>>>> On 23.04.14 at 10:16, <roger.pau@citrix.com> wrote:
>>>> According to the comment in p2m.h, AMD IOMMUs don't work correctly
>>>> with page types different than p2m_ram_rw when the p2m is shared
>>>> between HAP and IOMMU, so disable this sharing when using AMD IOMMUs.
>>>
>>> Doesn't this need to go before patch 2?
>>
>> It could certainly go before patch 2, but I don't see such a hard
>> requirement in the ordering (either way AMD hardware needs both patches
>> to work correctly, and applying one before the other is not going to
>> break bisection AFAICT).
> 
> Patch 2 allows the high bits in present IOMMU entries to be non-zero,
> thus allowing for IOMMU faults without this patch already in effect.

Since on AMD hardware iommu_hap_pt_share is always true (unless the user
forces it to false), the previous patch has no effect without this one
(because the previous patch only deals with iommu_hap_pt_share ==
false). I don't mind moving it anyway, and will do it in the next version.

Roger.

  reply	other threads:[~2014-04-23 14:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  8:16 [PATCH v2 0/4] Fix grant map/unmap with auto-translated guests Roger Pau Monne
2014-04-23  8:16 ` [PATCH v2 1/4] xen: make logdirty and iommu mutually exclusive Roger Pau Monne
2014-04-23  9:54   ` Jan Beulich
2014-04-24  7:36     ` Roger Pau Monné
2014-04-24 11:57       ` Roger Pau Monné
2014-04-24 11:50   ` Tim Deegan
2014-04-23  8:16 ` [PATCH v2 2/4] iommu: set correct IOMMU entries when iommu_hap_pt_share == 0 Roger Pau Monne
2014-04-23  9:56   ` Jan Beulich
2014-04-24 11:52   ` Tim Deegan
2014-05-08 18:38   ` Konrad Rzeszutek Wilk
2014-04-23  8:16 ` [PATCH v2 3/4] amd-iommu: disable iommu_hap_pt_share with AMD IOMMUs Roger Pau Monne
2014-04-23  9:57   ` Jan Beulich
2014-04-23 10:04     ` Roger Pau Monné
2014-04-23 10:51       ` Jan Beulich
2014-04-23 14:31         ` Roger Pau Monné [this message]
2014-04-23 14:35           ` Jan Beulich
2014-04-23  8:16 ` [PATCH v2 4/4] xen: expose that grant table mappings update the IOMMU Roger Pau Monne
2014-04-23 10:00   ` Jan Beulich
2014-04-24  7:43     ` Roger Pau Monné
2014-04-24  8:23       ` Jan Beulich
2014-05-08 18:39         ` Konrad Rzeszutek Wilk
2014-05-09  6:32           ` 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=5357CEB2.9070103@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=suravee.suthikulpanit@amd.com \
    --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).