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, 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
On 20/08/2018 09:30, Jan Beulich wrote:
On 20.08.18 at 05:32, 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
>>> On 20.08.18 at 10:40, wrote:
> On 2018/8/20 16:30, Jan Beulich wrote:
> On 20.08.18 at 05:32, 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
On 2018/8/20 16:30, Jan Beulich wrote:
On 20.08.18 at 05:32, 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
>>> On 20.08.18 at 05:32, 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
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().
As said above, acpi_parse_dmar() doesn't zaps APCI DMAR signature in
real TXT
