hi baolu,

               We run this on zhaoxin X86 paltform.

               There are some MCUS on our platforms that read and write data to the system memory.

During this process, the MCU is invisible to the host kernel. And the MCU needs to report through ACPI_NAMESPACE_DEVICE in RMRR.


Best regards

Felixcui-oc

发件人: Lu Baolu <baolu.lu@linux.intel.com>
发送时间: 2020年9月3日 15:22:14
收件人: FelixCui-oc; Joerg Roedel; iommu@lists.linux-foundation.org; linux-kernel@vger.kernel.org; David Woodhouse; Dan Carpenter; kbuild@lists.01.org
抄送: baolu.lu@linux.intel.com; CobeChen-oc; RaymondPang-oc; Tony W Wang-oc; Ashok Raj
主题: Re: 答复: 答复: [PATCH v3 2/2] iommu/vt-d:Add support for probing ACPI device in RMRR
 
Hi Felix,

On 9/2/20 11:24 AM, FelixCui-oc wrote:
> hi baolu,
>
>> So you have a hidden device (invisible to host kernel). But you need to
>
>>setup some identity mappings for this device, so that the firmware
>>could keep working, right?
>
>>The platform designs this by putting that range in the RMRR table and
>>expecting the OS kernel to setup identity mappings during boot.
>
>>Do I understand it right?
>
>
> Yes. What you understand is correct.

This appears to be a new usage model of RMRR. I need to discuss this
with the VT-d spec maintainer. Do you mind telling which platform are
you going to run this on? What is the motivation of creating such hidden
device?

Basically, RMRRs were added as work around for certain legacy device and
we have been working hard to fix those legacy devices so that RMRR are
no longer needed.

Best regards,
baolu