we have seen a number of SBI changes proposed (debug console, ap tee, ...).

will there be one big rev ala priv 1.12, small fast tracks , something else?

I also suggest that this either needs to be run out of the priv sw HC or convene a new TG. Can we conduct this conversation there (and create the appropriate group or committee mail aliases).

Thanks
Mark

--------
sent from a mobile device. please forgive any typos.

On Thu, Jun 2, 2022 at 7:36 PM mark <markhimelstein@...> wrote:

we have seen a number of SBI changes proposed (debug console, ap tee, ...).

will there be one big rev ala priv 1.12, small fast tracks , something else?

I also suggest that this either needs to be run out of the priv sw HC or convene a new TG. Can we conduct this conversation there (and create the appropriate group or committee mail aliases).

My understanding is that different TGs or SIGs will propose their own
SBI extensions. Once a set of changes for next SBI spec release are
finalized, the SBI TG can collect all new SBI extensions and prepare a
draft of the next SBI spec. It will be the responsibility of SBI TG to
complete the ratification process.

Is this understanding correct ?

Regards,
Anup

Thanks
Mark

--------
sent from a mobile device. please forgive any typos.

On Thu, Jun 2, 2022 at 7:41 AM Aaron Durbin <adurbin@...> wrote:

On Thu, Jun 2, 2022 at 8:38 AM Anup Patel <apatel@...> wrote:

On Thu, Jun 2, 2022 at 7:36 PM mark <markhimelstein@...> wrote:

we have seen a number of SBI changes proposed (debug console, ap tee, ...).

will there be one big rev ala priv 1.12, small fast tracks , something else?

I also suggest that this either needs to be run out of the priv sw HC or convene a new TG. Can we conduct this conversation there (and create the appropriate group or committee mail aliases).

My understanding is that different TGs or SIGs will propose their own
SBI extensions. Once a set of changes for next SBI spec release are
finalized, the SBI TG can collect all new SBI extensions and prepare a
draft of the next SBI spec. It will be the responsibility of SBI TG to
complete the ratification process.

As per my discussions with Philip, there will be a Firmware & Platform
Services SIG
which will cover all the platform services specs (SBI, UEFI, ACPI).

It can spin off separate TGs for SBI/ACPI which will be actually
responsible to deliver
the next version of the SBI specification.

Is this understanding correct ?

That aligns w/ my recollection on how we'll handle updates to SBI.

Yup. That's what I was thinking as well. Fortunately, a number of new
extensions have started to take shape.
Instead of releasing a version of each new extension, it would be good
to have a release that combines all of them.

Regards,
Anup

Thanks
Mark

--------
sent from a mobile device. please forgive any typos.

Mark,

In case you missed it from the agenda-email: we have the formation of
a Firmware & Platforms Services SIG on the agenda for the (joint)
Software HCs meeting today. Atish has kindly volunteered to be the
acting chair and we'll announce as soon as the draft charter is done.
The scope of the new SIG will be (at least) SBI, ACPI, UEFI and
bootloaders.

Philipp.

More than this, the specification cannot go to Freeze (public review)
until any SBI changes are in place.

One thing we might want to consider is having an "SBI approval"
process. That would allow SBI changes to be "upstreamed but not
released", and allow specifications to go to Freeze & Ratification
while they wait for the SBI changes to be released in the next version
of SBI.

This is no different than the upstreaming of things like GCC today. We
could make these changes to the process without changing the policy.
(no vote needed)

Cheers,
Stephano

On Mon, Jun 6, 2022 at 8:42 AM Stephano Cetola <stephano@...> wrote:

More than this, the specification cannot go to Freeze (public review)
until any SBI changes are in place.

One thing we might want to consider is having an "SBI approval"
process. That would allow SBI changes to be "upstreamed but not
released", and allow specifications to go to Freeze & Ratification

Do you mean SBI spec changes are merged in the spec but the SBI spec
is not frozen
by itself ?

while they wait for the SBI changes to be released in the next version
of SBI.

Release of the SBI specification - ratified version or frozen is fine ?
As long as dependent specs can go into public review once SBI spec is
frozen, that should be fine too.
As SBI spec is a software spec, a PoC implementation is the most
critical step here.

This is no different than the upstreaming of things like GCC today. We
could make these changes to the process without changing the policy.
(no vote needed)

Cheers,
Stephano

On Thu, Jun 2, 2022 at 8:06 AM mark <markhimelstein@...> wrote:

Just remember that something that depends on an SBI change can't get ratified until the SBI change is ratified.

If there is a roll up, there still needs to a TG governing it or it needs to be a fast track with the committee governing it and there needs to be a rat plan.

Mark

On Thu, Jun 2, 2022 at 7:38 AM Anup Patel <apatel@...> wrote:

On Thu, Jun 2, 2022 at 7:36 PM mark <markhimelstein@...> wrote:

we have seen a number of SBI changes proposed (debug console, ap tee, ...).

will there be one big rev ala priv 1.12, small fast tracks , something else?

I also suggest that this either needs to be run out of the priv sw HC or convene a new TG. Can we conduct this conversation there (and create the appropriate group or committee mail aliases).

My understanding is that different TGs or SIGs will propose their own
SBI extensions. Once a set of changes for next SBI spec release are
finalized, the SBI TG can collect all new SBI extensions and prepare a
draft of the next SBI spec. It will be the responsibility of SBI TG to
complete the ratification process.

Is this understanding correct ?

Regards,
Anup

Thanks
Mark

--------
sent from a mobile device. please forgive any typos.