On 2018/8/20 16:44, Andrew Cooper wrote:
On 20/08/2018 09:30, Jan Beulich wrote:
On 20.08.18 at 05:32, <zhenzhong.d...@oracle.com> wrote:
When TBOOT enabled, acpi_parse_dmar() zap a copy of DMAR table rather
than the real table, so make it controled by config option based on the
fact that we already have done the real zapping in tboot_parse_dmar_table().
Is this just a cosmetic change, or is there any harm done by the extra
zapping?
Before 123c7793797502b222300eb710cd3873dcca41ee, calling it multiple
times would require an equivalent number of reinstate calls for it to work.
That change went into Xen 4.6, whereas I guess this is a patch being
upstreamed from Oracles 4.4 patchqueue?
Not for that reason. Patch is for upstream.
tboot_parse_dmar_table() called acpi_dmar_zap() the first time,
acpi_parse_dmar called it the second time, I thought it's a dup.
Thanks
Zhenzhong
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
