On Fri, 2020-01-24 at 12:34 -0300, Martin Galvan wrote:
> The TXT.STS values make more sense now, though the PCH DID is still
> incorrect. Is there a way to check whether TXT is enabled other than
> looking at SINIT.BASE and HEAP.BASE?
Please look at txt_verify_platform() function in verify.c ther
I just ran the same tool on a Supermicro system which I'm positive has
TXT, and am now seeing the following (with TXT disabled):
Intel(r) TXT Configuration Registers:
STS: 0x0002
senter_done: FALSE
sexit_done: TRUE
mem_config_lock: FALSE
private_open: FALSE
El vie., 24 ene. 2020 a las 11:34, Lukasz Hawrylko
() escribió:
> I see that your SINIT.BASE and HEAP.BASE registers have all zeros, did
> you enable TXT in BIOS? I guess that txt-stat may not check if TXT is
> enabled before reading TXT related registers, that's why you can have
> strange, random
On Thu, 2020-01-23 at 14:41 -0300, Martin Galvan wrote:
> Hi all,
>
> I just ran txt-stat on a system which has an IceLake CPU and a 495
> Series PCH, and am seeing the following output:
>
> Intel(r) TXT Configuration Registers:
> STS: 0x0003
> senter_done: TRUE
> sexit_do
Hi all,
I just ran txt-stat on a system which has an IceLake CPU and a 495
Series PCH, and am seeing the following output:
Intel(r) TXT Configuration Registers:
STS: 0x0003
senter_done: TRUE
sexit_done: TRUE
mem_config_lock: FALSE
private_open: FALSE
