zeInit and L0 offline mode

[jandres742]

there could be situations where L0 APIs need to be accessed in offline mode, meaning, on systems where Compute workloads cannot be run because for instance, there are no devices is available. Some examples:

• Maybe an application wants to generate an AOT (Ahead-Of-Time) binary which would be used for execution at another time.
• Maybe user wants to analyze the data from a core dump provided in a previous run by an L0 application. No need to run the application again, just extract the information available in the core dump using also L0 APIs.
• Maybe user wants to analyze some timestamp or performance data obtained during a previous run.

for instance, in the last scenario, user could run first an application on a GPU device and collect some data:

// On the machine containing a GPU
zeInit
...
zeExecuteCommandLists
...
// Gather timestamps

then, in another system, not necessarily containing the same GPU, user might want to do:

zeInit // Initialize in offline mode
zeDriverAnalyzeTimestamps // this is a made-up  API, just to show an example

so questions here:

1. Is this something useful and that belongs to the L0 specification?
2. if desired, then, how could user tell zeInit to initialize in offline mode? maybe a new env var, something like ZE_INIT_OFFLINE=1?
3. are there any other uses, pros/cons for this mode?