From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Roman Shaposhnik" <roman@zededa.com>
Cc: Juergen Gross <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx
Date: Wed, 7 Aug 2019 12:03:30 +0200 [thread overview]
Message-ID: <4d8d0ef4-614e-7545-c388-4edb88e9cd2c@suse.com> (raw)
In-Reply-To: <20190807095701.exld4hnidz6hmgll@Air-de-Roger>
On 07.08.2019 11:57, Roger Pau Monné wrote:
> On Wed, Aug 07, 2019 at 09:08:58AM +0200, Jan Beulich wrote:
>> On 06.08.2019 23:48, Roman Shaposhnik wrote:
>>> On Tue, Aug 6, 2019 at 9:18 AM Roger Pau Monné <roger.pau@citrix.com> wrote:
>>>>
>>>> On Fri, Aug 02, 2019 at 10:05:40AM +0200, Roger Pau Monné wrote:
>>>>> On Thu, Aug 01, 2019 at 11:25:04AM -0700, Roman Shaposhnik wrote:
>>>>>> This patch completely fixes the problem for me!
>>>>>>
>>>>>> Thanks Roger! I'd love to see this in Xen 4.13
>>>>>
>>>>> Thanks for testing!
>>>>>
>>>>> It's still not clear to me why the previous approach didn't work, but
>>>>> I think this patch is better because it removes the usage of
>>>>> {set/clear}_identity_p2m_entry from PV domains. I will submit this
>>>>> formally now.
>>>>
>>>> Sorry to bother again, but since we still don't understand why the
>>>> previous fix didn't work for you, and I can't reproduce this with my
>>>> hardware, could you give the attached patch a try?
>>>
>>> No worries -- and thanks for helping to get it over the finish line --
>>> this is much appreciated!
>>>
>>> I'm happy to say that this latest patch is also working just fine. So
>>> I guess this is the one that's going to land in Xen 4.13?
>>
>> Not necessarily - the other patch is also a candidate, but its
>> description would need to explain what was actually wrong.
>>
>>>> AFAICT the only difference between the non-working version and the
>>>> working version is the flush, so I've added it here.
>>
>> Now I'm afraid I still can't draw a helpful conclusion from Roman's
>> successful test: intel_iommu_hwdom_init(), after having called
>> setup_hwdom_rmrr(), calls iommu_flush_all() (with one other,
>> seemingly innocent call in between). The only conclusion I _could_
>> draw is that iommu_flush_all() doesn't do what its name says. Which
>> would be quite bad. But
>>
>> [orig]
>> iommu_flush_all()
>> -> iommu_flush_iotlb_global(flush_non_present_entry=0)
>> -> flush->iotlb(DMA_TLB_GLOBAL_FLUSH, flush_non_present_entry=0)
>>
>> [patch]
>> iommu_flush_iotlb_all()
>> -> iommu_flush_iotlb(dma_old_pte_present=0, page_count=0)
>> -> iommu_flush_iotlb_dsi(flush_non_present_entry=0)
>> -> flush->iotlb(DMA_TLB_DSI_FLUSH, flush_non_present_entry=0)
>>
>> suggests to me that (as one would infer from the names) is the
>> more through flush. I must be overlooking something ...
>
> I went over the iotlb queued invalidation code and it seems fine to
> me, I haven't been able to spot any issues with it, and as you say
> above the only difference is the flush type (DSI vs GLOBAL).
>
> Again and just to make sure it's actually the flush type (and nothing
> in between) the factor that makes this work or break, can you try the
> above patch?
And I take it the "you" here was meant for Roman (only on Cc),
not me.
Jan
> Thanks, Roger.
> ---8<---
> diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c
> index fef97c82f6..3605614aaf 100644
> --- a/xen/arch/x86/mm/p2m.c
> +++ b/xen/arch/x86/mm/p2m.c
> @@ -1341,7 +1341,7 @@ int set_identity_p2m_entry(struct domain *d, unsigned long gfn_l,
>
> if ( !paging_mode_translate(p2m->domain) )
> {
> - if ( !need_iommu_pt_sync(d) )
> + if ( !has_iommu_pt(d) )
> return 0;
> return iommu_legacy_map(d, _dfn(gfn_l), _mfn(gfn_l), PAGE_ORDER_4K,
> IOMMUF_readable | IOMMUF_writable);
> @@ -1432,7 +1432,7 @@ int clear_identity_p2m_entry(struct domain *d, unsigned long gfn_l)
>
> if ( !paging_mode_translate(d) )
> {
> - if ( !need_iommu_pt_sync(d) )
> + if ( !has_iommu_pt(d) )
> return 0;
> return iommu_legacy_unmap(d, _dfn(gfn_l), PAGE_ORDER_4K);
> }
> diff --git a/xen/drivers/passthrough/vtd/iommu.c b/xen/drivers/passthrough/vtd/iommu.c
> index 5d72270c5b..885185ad09 100644
> --- a/xen/drivers/passthrough/vtd/iommu.c
> +++ b/xen/drivers/passthrough/vtd/iommu.c
> @@ -2026,7 +2026,7 @@ static int rmrr_identity_mapping(struct domain *d, bool_t map,
> mrmrr->count = 1;
> list_add_tail(&mrmrr->list, &hd->arch.mapped_rmrrs);
>
> - return 0;
> + return iommu_flush_all();
> }
>
> static int intel_iommu_add_device(u8 devfn, struct pci_dev *pdev)
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-07 10:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 19:31 [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx Roman Shaposhnik
2019-07-19 20:02 ` Roman Shaposhnik
2019-07-22 8:20 ` Paul Durrant
2019-07-22 11:48 ` Roger Pau Monné
2019-07-22 11:54 ` Paul Durrant
2019-07-22 13:48 ` Roger Pau Monné
2019-07-22 14:03 ` Paul Durrant
2019-07-22 14:39 ` Roger Pau Monné
2019-07-22 15:02 ` Paul Durrant
2019-07-22 15:21 ` Roger Pau Monné
2019-07-22 23:36 ` Roman Shaposhnik
2019-07-22 23:47 ` Andrew Cooper
2019-07-23 17:32 ` Roman Shaposhnik
2019-07-23 17:35 ` Andrew Cooper
2019-07-23 17:48 ` Roman Shaposhnik
2019-07-23 17:50 ` Andrew Cooper
2019-07-23 17:58 ` Roman Shaposhnik
2019-07-23 18:12 ` Andrew Cooper
2019-07-23 18:25 ` Roman Shaposhnik
2019-07-26 7:58 ` Jan Beulich
2019-07-30 17:56 ` Roman Shaposhnik
2019-07-31 8:34 ` Jan Beulich
2019-07-31 8:58 ` Andrew Cooper
2019-07-31 9:30 ` Jan Beulich
2019-07-31 19:37 ` Roman Shaposhnik
2019-07-24 12:00 ` Jan Beulich
2019-07-24 12:04 ` Jan Beulich
2019-07-24 11:23 ` Andrew Cooper
2019-07-24 11:40 ` Andrew Cooper
2019-07-24 14:11 ` Roger Pau Monné
2019-07-26 0:47 ` Roman Shaposhnik
2019-07-26 9:35 ` Roger Pau Monné
2019-07-30 9:21 ` Roger Pau Monné
2019-07-30 17:55 ` Roman Shaposhnik
2019-07-31 8:31 ` Jan Beulich
2019-07-31 8:36 ` Roger Pau Monné
2019-07-31 8:43 ` Roger Pau Monné
2019-07-31 19:35 ` Roman Shaposhnik
2019-07-31 19:46 ` Andrew Cooper
2019-07-31 21:03 ` Roman Shaposhnik
2019-08-01 8:15 ` Roger Pau Monné
2019-08-01 18:25 ` Roman Shaposhnik
2019-08-02 8:05 ` Roger Pau Monné
2019-08-06 16:17 ` Roger Pau Monné
2019-08-06 21:48 ` Roman Shaposhnik
2019-08-07 7:08 ` Jan Beulich
2019-08-07 9:57 ` Roger Pau Monné
2019-08-07 10:03 ` Jan Beulich [this message]
2019-08-07 7:35 ` Roger Pau Monné
2019-08-07 8:31 ` Jan Beulich
2019-08-07 10:17 ` Roger Pau Monné
2019-08-12 8:57 ` Roger Pau Monné
2019-08-13 19:24 ` Roman Shaposhnik
2019-08-14 8:06 ` Roger Pau Monné
2019-08-19 5:00 ` Roman Shaposhnik
2019-08-19 8:16 ` Roger Pau Monné
2019-08-20 2:03 ` Roman Shaposhnik
2019-08-01 7:35 ` Jan Beulich
2019-07-31 19:30 ` Roman Shaposhnik
2019-08-01 8:45 ` Roger Pau Monné
2019-08-01 18:19 ` Roman Shaposhnik
2019-07-20 16:39 ` Andrew Cooper
2019-07-22 8:03 ` Paul Durrant
2019-07-24 17:42 ` Rich Persaud
2019-07-26 1:13 ` Roman Shaposhnik
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=4d8d0ef4-614e-7545-c388-4edb88e9cd2c@suse.com \
--to=jbeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=roman@zededa.com \
--cc=xen-devel@lists.xenproject.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 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).