Does Eyrie Reveal Enclave's Physical Memory Addresses in Debug Mode?

[AlfiRam]

Does enabling rt_option(DEBUG "Enable debugging" ON) in runtime/CMakeLists.txt allow the Eyrie Runtime to print the enclave's physical memory addresses during loading?

For example, when running an enclave, the debug log shows:

# /usr/share/keystone/examples/hello-native.ke  
Verifying archive integrity... MD5 checksums are OK. All good.
Uncompressing Keystone Enclave Package
[debug] Creating new elf file struct
 (elf.c:16)
[debug] Check elf file
 (elf.c:26)
[debug] Check elf file 32
 (elf.c:75)
[debug] Check program header
 (elf.c:32)
[debug] Check section table
 (elf.c:40)
[debug] Finished validating elf
 (elf.c:48)
[debug] ROOT PAGE TABLE: 0xffffffff00007000 (boot.c:98)
[debug] UTM : 0x102400000-0x102500000 (1024 KB) (boot.c:99)
[debug] DRAM: 0x102200000-0x102400000 (2048 KB) (boot.c:100)
[debug] USER: 0x10222c000-0x10223e000 (72 KB) (boot.c:101)
[debug] FREE: 0x10223e000-0x102400000 (1800 KB), va 0xffffffff0003e000 (boot.c:108)
[debug] Creating new elf file struct
 (elf.c:16)
[debug] Check elf file
 (elf.c:26)
[debug] Check elf file 32
 (elf.c:75)
[debug] Check program header
 (elf.c:32)
[debug] Check section table
 (elf.c:40)
[debug] Finished validating elf
 (elf.c:48)
[debug] eyrie boot finished. drop to the user land ... (boot.c:140)
Enclave said: "Hello World"

Can I confirm that DRAM: 0x102200000-0x102400000 (2048 KB) represents the actual physical memory region allocated to the enclave in main memory?