All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	intel-gfx@lists.freedesktop.org,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Intel-gfx] i915 dma faults on Xen
Date: Wed, 21 Oct 2020 12:33:05 +0200	[thread overview]
Message-ID: <a855e542-4e12-14e2-b663-75e2efceb937@suse.com> (raw)
In-Reply-To: <20201021095809.o53b6hpvjl2lbqsi@Air-de-Roger>

On 21.10.2020 11:58, Roger Pau Monné wrote:
> On Fri, Oct 16, 2020 at 12:23:22PM -0400, Jason Andryuk wrote:
>> The RMRRs are:
>> (XEN) [VT-D]Host address width 39
>> (XEN) [VT-D]found ACPI_DMAR_DRHD:
>> (XEN) [VT-D]  dmaru->address = fed90000
>> (XEN) [VT-D]drhd->address = fed90000 iommu->reg = ffff82c00021d000
>> (XEN) [VT-D]cap = 1c0000c40660462 ecap = 19e2ff0505e
>> (XEN) [VT-D] endpoint: 0000:00:02.0
>> (XEN) [VT-D]found ACPI_DMAR_DRHD:
>> (XEN) [VT-D]  dmaru->address = fed91000
>> (XEN) [VT-D]drhd->address = fed91000 iommu->reg = ffff82c00021f000
>> (XEN) [VT-D]cap = d2008c40660462 ecap = f050da
>> (XEN) [VT-D] IOAPIC: 0000:00:1e.7
>> (XEN) [VT-D] MSI HPET: 0000:00:1e.6
>> (XEN) [VT-D]  flags: INCLUDE_ALL
>> (XEN) [VT-D]found ACPI_DMAR_RMRR:
>> (XEN) [VT-D] endpoint: 0000:00:14.0
>> (XEN) [VT-D]dmar.c:615:   RMRR region: base_addr 78863000 end_addr 78882fff
>> (XEN) [VT-D]found ACPI_DMAR_RMRR:
>> (XEN) [VT-D] endpoint: 0000:00:02.0
>> (XEN) [VT-D]dmar.c:615:   RMRR region: base_addr 7d000000 end_addr 7f7fffff
>> (XEN) [VT-D]found ACPI_DMAR_RMRR:
>> (XEN) [VT-D] endpoint: 0000:00:16.7
>> (XEN) [VT-D]dmar.c:581:  Non-existent device (0000:00:16.7) is
>> reported in RMRR (78907000, 78986fff)'s scope!
>> (XEN) [VT-D]dmar.c:596:   Ignore the RMRR (78907000, 78986fff) due to
> 
> This is also part of a reserved region, so should be added to the
> iommu page tables anyway regardless of this message.

Could you clarify why you think so? RMRRs are tied to devices, so
if a device in reality doesn't exist (and no other one uses the
same range), I don't see why an IOMMU mapping would be needed
(unless to work around some related firmware bug). Plus aiui none
of the IOMMU faults actually report this range as having got
accessed.

Jan
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Jason Andryuk <jandryuk@gmail.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	intel-gfx@lists.freedesktop.org,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: i915 dma faults on Xen
Date: Wed, 21 Oct 2020 12:33:05 +0200	[thread overview]
Message-ID: <a855e542-4e12-14e2-b663-75e2efceb937@suse.com> (raw)
In-Reply-To: <20201021095809.o53b6hpvjl2lbqsi@Air-de-Roger>

On 21.10.2020 11:58, Roger Pau Monné wrote:
> On Fri, Oct 16, 2020 at 12:23:22PM -0400, Jason Andryuk wrote:
>> The RMRRs are:
>> (XEN) [VT-D]Host address width 39
>> (XEN) [VT-D]found ACPI_DMAR_DRHD:
>> (XEN) [VT-D]  dmaru->address = fed90000
>> (XEN) [VT-D]drhd->address = fed90000 iommu->reg = ffff82c00021d000
>> (XEN) [VT-D]cap = 1c0000c40660462 ecap = 19e2ff0505e
>> (XEN) [VT-D] endpoint: 0000:00:02.0
>> (XEN) [VT-D]found ACPI_DMAR_DRHD:
>> (XEN) [VT-D]  dmaru->address = fed91000
>> (XEN) [VT-D]drhd->address = fed91000 iommu->reg = ffff82c00021f000
>> (XEN) [VT-D]cap = d2008c40660462 ecap = f050da
>> (XEN) [VT-D] IOAPIC: 0000:00:1e.7
>> (XEN) [VT-D] MSI HPET: 0000:00:1e.6
>> (XEN) [VT-D]  flags: INCLUDE_ALL
>> (XEN) [VT-D]found ACPI_DMAR_RMRR:
>> (XEN) [VT-D] endpoint: 0000:00:14.0
>> (XEN) [VT-D]dmar.c:615:   RMRR region: base_addr 78863000 end_addr 78882fff
>> (XEN) [VT-D]found ACPI_DMAR_RMRR:
>> (XEN) [VT-D] endpoint: 0000:00:02.0
>> (XEN) [VT-D]dmar.c:615:   RMRR region: base_addr 7d000000 end_addr 7f7fffff
>> (XEN) [VT-D]found ACPI_DMAR_RMRR:
>> (XEN) [VT-D] endpoint: 0000:00:16.7
>> (XEN) [VT-D]dmar.c:581:  Non-existent device (0000:00:16.7) is
>> reported in RMRR (78907000, 78986fff)'s scope!
>> (XEN) [VT-D]dmar.c:596:   Ignore the RMRR (78907000, 78986fff) due to
> 
> This is also part of a reserved region, so should be added to the
> iommu page tables anyway regardless of this message.

Could you clarify why you think so? RMRRs are tied to devices, so
if a device in reality doesn't exist (and no other one uses the
same range), I don't see why an IOMMU mapping would be needed
(unless to work around some related firmware bug). Plus aiui none
of the IOMMU faults actually report this range as having got
accessed.

Jan


  reply	other threads:[~2020-10-21 11:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 19:28 [Intel-gfx] i915 dma faults on Xen Jason Andryuk
2020-10-14 19:28 ` Jason Andryuk
2020-10-14 19:37 ` [Intel-gfx] " Andrew Cooper
2020-10-14 19:37   ` Andrew Cooper
2020-10-15 11:31   ` [Intel-gfx] " Roger Pau Monné
2020-10-15 11:31     ` Roger Pau Monné
2020-10-15 15:16     ` [Intel-gfx] " Jason Andryuk
2020-10-15 15:16       ` Jason Andryuk
2020-10-15 16:38       ` Tamas K Lengyel
2020-10-15 17:13         ` Jason Andryuk
2021-02-19 17:33           ` tboot UEFI and Xen (was Re: i915 dma faults on Xen) Jason Andryuk
2020-10-16 16:23       ` [Intel-gfx] i915 dma faults on Xen Jason Andryuk
2020-10-16 16:23         ` Jason Andryuk
2020-10-21  9:58         ` [Intel-gfx] " Roger Pau Monné
2020-10-21  9:58           ` Roger Pau Monné
2020-10-21 10:33           ` Jan Beulich [this message]
2020-10-21 10:33             ` Jan Beulich
2020-10-21 10:51             ` [Intel-gfx] " Roger Pau Monné
2020-10-21 10:51               ` Roger Pau Monné
2020-10-21 12:45           ` [Intel-gfx] " Jason Andryuk
2020-10-21 12:45             ` Jason Andryuk
2020-10-21 12:52             ` [Intel-gfx] " Jan Beulich
2020-10-21 12:52               ` Jan Beulich
2020-10-21 13:36               ` [Intel-gfx] " Jason Andryuk
2020-10-21 13:36                 ` Jason Andryuk
2020-10-21 13:59                 ` [Intel-gfx] " Jan Beulich
2020-10-21 13:59                   ` Jan Beulich
2021-02-19 17:30                   ` [Intel-gfx] " Jason Andryuk
2021-02-19 17:30                     ` Jason Andryuk
2021-02-22 10:18                     ` [Intel-gfx] " Roger Pau Monné
2021-02-22 10:18                       ` Roger Pau Monné
2021-02-22 12:49                       ` [Intel-gfx] " Jason Andryuk
2021-02-22 12:49                         ` Jason Andryuk

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=a855e542-4e12-14e2-b663-75e2efceb937@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=roger.pau@citrix.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 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.