[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1477b1dd-ac48-b49d-77f9-107bb4555b91@linux.intel.com>
Date: Thu, 6 Aug 2020 10:36:01 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: FelixCui-oc <FelixCui-oc@...oxin.com>,
Joerg Roedel <joro@...tes.org>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Woodhouse <dwmw2@...radead.org>
Cc: baolu.lu@...ux.intel.com,
RaymondPang-oc <RaymondPang-oc@...oxin.com>,
CobeChen-oc <CobeChen-oc@...oxin.com>
Subject: Re: 答复: 答复: 答复: 答复: 答复: [PATCH] iommu/vt-d:Add support for ACPI device in RMRR
Hi Felix,
On 8/5/20 3:37 PM, FelixCui-oc wrote:
> Hi baolu,
> Let me talk about why acpi_device_create_direct_mappings() is needed and please tell me if there is an error.
Sure. Before that, let me sync my understanding with you. You have an
acpi namespace device in ANDD table, it also shows up in the device
scope of a RMRR. Current code doesn't enumerate that device for the
RMRR, hence iommu_create_device_direct_mappings() doesn't work for this
device.
At the same time, probe_acpi_namespace_devices() doesn't work for this
device, hence you want to add a home-made
acpi_device_create_direct_mappings() helper.
Did I get it right?
> In the probe_acpi_namespace_devices() function, only the device in the addev->physical_node_list is probed,
> but we need to establish identity mapping for the namespace device in RMRR. These are two different devices.
The namespace device has been probed and put in one drhd's device list.
Hence, it should be processed by probe_acpi_namespace_devices(). So the
question is why there are no devices in addev->physical_node_list?
> Therefore, the namespace device in RMRR is not mapped in probe_acpi_namespace_devices().
> acpi_device_create_direct_mappings() is to create direct mappings for namespace devices in RMRR.
Best regards,
baolu
Powered by blists - more mailing lists