[PATCH v12 03/19] x86: Secure Launch Resource Table header file

[ross.philipson at oracle.com]

On 3/7/25 11:30 AM, Jarkko Sakkinen wrote:
> On Fri, Mar 07, 2025 at 11:22:02AM -0800, ross.philipson at oracle.com wrote:
>> On 3/6/25 9:32 PM, Jarkko Sakkinen wrote:
>>> On Thu, Dec 19, 2024 at 11:42:00AM -0800, Ross Philipson wrote:
>>>> Introduce the Secure Launch Resource Table which forms the formal
>>>> interface between the pre and post launch code.
>>>>
>>>> Signed-off-by: Ross Philipson <ross.philipson at oracle.com>
>>>
>>> Is this interface kernel specific or uarch specific? I'd just
>>> explicitly state the context of the formal interface, that's
>>> all.
>>
>> It is specific to our DRTM solution (i.e. Secure Launch). It is meant to be
>> extensible to accommodate future architectures that have DRTM support
>> available. Not sure if I am getting at your specific question.
> 
> OK so:
> 
> 1. It's software defined set of data structures with no ties to
>     the hardware architecture.
> 2. It's essentially an API maintining backwards compatibility.
> 
> I have nothing against that definition. It is just that speaking about
> formal interface between pre and post launch code does not provide
> explanation on what are the constraints of the interface.
> 
> So what I was not getting was the specific definition (i.e. *the*
> specific formalism under discussion).

Ok I get what you are saying/asking now. We can make this clearer.

Ross

> 
> BR, Jarkko
>