public inbox for iommu@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>,
	iommu@lists.linux-foundation.org,  Joerg Roedel <joro@8bytes.org>
Subject: Re: dmar pte read access not set error messages on hp dl388 gen8 systems
Date: Tue, 3 Dec 2019 09:59:33 +0800	[thread overview]
Message-ID: <14bbe41c-61e9-d2b6-31cb-67c0b1ad11da@linux.intel.com> (raw)
In-Reply-To: <20191202161332.ctc3y5cvdgqwnz7l@cantor>

Hi,

On 12/3/19 12:13 AM, Jerry Snitselaar wrote:
> On Mon Dec 02 19, Jerry Snitselaar wrote:
>> On Mon Dec 02 19, Lu Baolu wrote:
>>> Hi,
>>>
>>> On 12/2/19 2:34 PM, Jerry Snitselaar wrote:
>>>> We are seeing DMAR PTE read access not set errors when booting a
>>>> kernel with default passthrough, both with a test kernel and with
>>>> a 5.4.0 kernel. Previously we would see a number of identity mappings
>>>> being set related to the rmrrs, and now they aren't seen and we get
>>>> the dmar pte errors as devices touch those regions. From what I can 
>>>> tell
>>>> currently df4f3c603aeb ("iommu/vt-d: Remove static identity map code")
>>>> removed the bit of code in init_dmars that used to set up those
>>>> mappings:
>>>>
>>>> -       /*
>>>> -        * For each rmrr
>>>> -        *   for each dev attached to rmrr
>>>> -        *   do
>>>> -        *     locate drhd for dev, alloc domain for dev
>>>> -        *     allocate free domain
>>>> -        *     allocate page table entries for rmrr
>>>> -        *     if context not allocated for bus
>>>> -        *           allocate and init context
>>>> -        *           set present in root table for this bus
>>>> -        *     init context with domain, translation etc
>>>> -        *    endfor
>>>> -        * endfor
>>>> -        */
>>>> -       pr_info("Setting RMRR:\n");
>>>> -       for_each_rmrr_units(rmrr) {
>>>> -               /* some BIOS lists non-exist devices in DMAR table. */
>>>> -               for_each_active_dev_scope(rmrr->devices, 
>>>> rmrr->devices_cnt,
>>>> -                                         i, dev) {
>>>> -                       ret = iommu_prepare_rmrr_dev(rmrr, dev);
>>>> -                       if (ret)
>>>> -                               pr_err("Mapping reserved region 
>>>> failed\n");
>>>> -               }
>>>> -       }
>>>>
>>>> si_domain_init now has code that sets identity maps for devices in 
>>>> rmrrs, but
>>>> only for certain devices.
>>>
>>> On which device, are you seeing this error? Is it a rmrr locked device?
>>>
>>> Best regards,
>>> baolu
>>>
>>
>> Almost all of the messages are for the ilo, but there also is a 
>> message for
>> the smart array raid bus controller.
>>
> 
> Also seeing it with a dl380 gen9 system, where the raid bus controller
> is getting the error.

Does it help if you remove

                         if (device_is_rmrr_locked(dev))
                                 continue;

in si_domain_init()?

Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-12-03  2:00 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 [this message]
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
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=14bbe41c-61e9-d2b6-31cb-67c0b1ad11da@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.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