iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: iommu@lists.linux-foundation.org
Subject: Re: dmar pte read access not set error messages on hp dl388 gen8 systems
Date: Tue, 10 Dec 2019 13:03:34 +0800	[thread overview]
Message-ID: <860d1f65-1fa6-577b-3dcd-f4d575a9db36@linux.intel.com> (raw)
In-Reply-To: <20191210034753.wlmbqdvqpcnzfxyl@cantor>

Hi,

On 12/10/19 11:47 AM, Jerry Snitselaar wrote:
>>>
>>> So the domain type is dma after 01:00.0 gets added, and when
>>> intel_iommu_add_device is called for 01:00.2 it will go into the if
>>> section. Since the device default domain type for 01:00.2 is dma
>>> nothing happens in there, and it goes on to 01:00.4. Is the "private
>>> identity domain" message really accurate since everyone will use
>>> si_domain? Adding some more debugging.
>>
>> The facts that we have seen:
>>
>> 1) 01.00.2 uses the default domain in group 25. The domain type of this
>>   default domain is DMA.
>>
>> 2) iommu_group_create_direct_mappings() *should* be called when adding
>>   01.00.2 into group 25. As the result, RMRR for this device *should*
>>   be identity mapped.
>>
>> 3) By checking DMAR table, RMRR (0x000000bdf6f000 ~ 0x000000bdf7efff) is
>>   reported for device 01.00.2.
>>
>> The problem is that RMRR (0x000000bdf6f000 ~ 0x000000bdf7efff) hasn't
>> actually been mapped, as the result IOMMU faults generated when device
>> try to access this range.
>>
>> So I guess you could add more debug message to check why
>> iommu_group_create_direct_mappings() doesn't do the right thing?
>>
>> Best regards,
>> baolu
>>
> 
> A call to iommu_map is failing.
> 
> [   36.686881] pci 0000:01:00.2: iommu_group_add_device: calling 
> iommu_group_create_direct_mappings
> [   36.689843] pci 0000:01:00.2: iommu_group_create_direct_mappings: 
> iterating through mappings
> [   36.692757] pci 0000:01:00.2: iommu_group_create_direct_mappings: 
> calling apply_resv_region
> [   36.695526] pci 0000:01:00.2: e_direct_mappings: entry type is direct
> [   37.198053] iommu: iommu_map: ops->map failed iova 0xbddde000 pa 
> 0x00000000bddde000 pgsize 0x1000

So can you further check why intel_iomm_map() fails here?

Best regards,
baolu

> [   37.201357] pci 0000:01:00.2: iommu_group_create_direct_mappings: 
> iommu_map failed
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-12-10  5:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  6:34 dmar pte read access not set error messages on hp dl388 gen8 systems Jerry Snitselaar
2019-12-02  6:41 ` Lu Baolu
2019-12-02  7:14   ` Jerry Snitselaar
2019-12-02 16:13     ` Jerry Snitselaar
2019-12-03  1:59       ` Lu Baolu
2019-12-03  9:56         ` Jerry Snitselaar
2019-12-04  0:17           ` Lu Baolu
2019-12-04 20:53             ` Jerry Snitselaar
2019-12-05  1:39               ` Lu Baolu
2019-12-05  2:25                 ` Jerry Snitselaar
2019-12-05  2:44                   ` Lu Baolu
2019-12-05  2:53                     ` Jerry Snitselaar
2019-12-06  1:52                       ` Lu Baolu
2019-12-06  7:24                         ` Jerry Snitselaar
2019-12-07  1:53                           ` Lu Baolu
2019-12-07  2:29                             ` Jerry Snitselaar
2019-12-07  2:41                               ` Jerry Snitselaar
2019-12-08  6:26                                 ` Lu Baolu
2019-12-10  0:52                                   ` Jerry Snitselaar
2019-12-10  1:29                                     ` Lu Baolu
2019-12-10  3:47                                       ` Jerry Snitselaar
2019-12-10  5:03                                         ` Lu Baolu [this message]
2019-12-10  5:18                                         ` Jerry Snitselaar
2019-12-10  5:43                                           ` Lu Baolu
2019-12-10 22:12                                             ` Jerry Snitselaar
2019-12-10  5:43                                           ` Jerry Snitselaar
2019-12-10  6:16                                             ` Jerry Snitselaar
2019-12-10  6:26                                               ` Lu Baolu
2019-12-10  7:44                                                 ` Jerry Snitselaar
2019-12-08  6:04                           ` Lu Baolu

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=860d1f65-1fa6-577b-3dcd-f4d575a9db36@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jsnitsel@redhat.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).