BroadwellDEFspBinPkg MR2 locks IA32_FEATURE_CONTROL in FSP-M about fsp HOT 11 OPEN

that should never be locked by anything but the kernel. Anything else is a mistake. We went through this seven years ago on chromebooks, I can't believe we're back here.

from fsp.

@nate-desimone Any update on this issue ?

from fsp.

The issue will be investigated, you may contact your Intel rep or file an IPS (Intel Premier Support) ticket if it’s urgent for you. Thanks!

from fsp.

It's been a month without a reply. Any update on this issue ?

from fsp.

It's been a month without a reply. Any update on this issue ?

from fsp.

At this point it's been a months. I'm +1-ning for update on that.

from fsp.

It's been a month without a reply. Any update on this issue ?

from fsp.

It's been a month without a reply. Any update on this issue ?

from fsp.

Almost a year! You must be typing very slow as it's only one line of source code to change...

from fsp.

Root cause : after memory initialization the FSP programs "IA32_FEATURE_CONTROL" MSR with Vmx features and lock the register by setting 0th bit; once the lock bit set the register become read only.

Proposed solution : do not lock the register after memory init instead lock the register during FSP ready to boot stage .

This will be resolved in the next official release however the timeline of next release is still tbc.
For NDA customers and technology partners of Intel, you may contact your Intel Rep or file an IPS# ticket for source request or method consultation for temporary workaround on your own.

from fsp.

@swong23 any update on this (next month this will be 3 years old)

from fsp.