Re: [tboot-devel] SINIT Exit Point

[Wang, S. <sha...@in...>]

OK.

So, it should not be the problem of entry point. Originally what I mean is the entry point in tboot header structure. (see init_txt_heap())
CONFIG_HIGHMEM4G should be kernel config. When you get "reset" in GETSEC[SENTER], kernel is not running. So, I don't think the problem is related to any of kernel configs.

Can you check your PMR setting for 4G? vtd_pmr_lo_base/size and vtd_pmr_hi_base/size.

This is what I can think related to memory.

PS: is it convenient for you to send me your serial log of your code?

Shane

Jonathan M. McCune wrote:
> Hi Shane, cc list,
> 
> Jonathan M. McCune wrote:
>>>> I'm experimenting with SENTER on an HP 8530p with the newest BIOS.
>>>> tboot works without issue.  However, when I run my own code, the
>>>> laptop reboots upon invoking SENTER, and LT.ERRORCODE is populated
>>>> with 0xc0000001, or "SINIT Exit Point".  I'm at a loss for what I
>>>> am doing wrong based solely on that error message.
> 
> This laptop contained 4GB of physical memory in two 2GB DIMMs.  I
> removed one of them, leaving the system with only 2GB of physical
> memory.  This enables my code to execute successfully.
> 
> I realized this when I noticed that despite having CONFIG_HIGHMEM4G=y
> in the kernel config, the system only sees 3GB of memory.  I then
> took a closer look at the value read from TXTCR_SINIT_BASE.  The
> value is 0x7be00000 with 2GB of RAM in the system, but it changes to
> 0xbfe00000 with 4GB in the system.  However, 0xbfe00000 is much closer
> to 3GB than 4GB.
> 
> tboot will execute successfully with either amount of memory in the
> system, and also sees 0xbfe00000 in TXTCR_SINIT_BASE with 4GB of RAM
> in the system.
> 
> Thus, I'm still not exactly sure what causes my code to fail.
> 
> However, I discovered that the chipset in this laptop has an issue
> with making all 4GB of RAM available despite CONFIG_HIGHMEM4G=y, and
> instead requires PAE support to see more than 3GB of RAM (I did
> verify that with CONFIG_HIGHMEM64G=y all 4GB are visible to Linux). 
> Here's a thread that discusses this unexpected need for PAE:
> 
> http://lkml.indiana.edu/hypermail/linux/kernel/0607.3/1787.html
> 
> I'm not sure if these issues are related yet.  Suggestions / comments
> / questions welcomed by all.
> 
> Thanks,
> -Jon