-
Hi All, Although I know the static CPU template will be depracated from v1.5.0, however I have some puzzles want to clarify, and If someone can help, I will appreciate very much.
These are the similar CPUID which are filtered: Any comment or help is highly appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @up2wing, thanks for starting a discussion! The reason we decided against including RDSEED, ADX, CLWB and CLFLUSHOPT bits in the T2CL/T2A CPUs templates was that they did not have different values between Cascade Lake and Milan. The reason we did not include UMIP, PKU and XSAVEC was regular userspace applications (that Firecracker is mainly targeted at) were not supposed to observe the effects that settings those bits would make. We limited those CPU templates to feature bits that are likely to be taken into account by applications or frameworks that choose different (optimised) implementations based on them. Also, as a note, we have deprecated static CPU templates in Firecracker 1.5. Users are encouraged to use custom CPU templates instead where they have much more control over the guest CPUID configuration. Hope it answers your question. |
Beta Was this translation helpful? Give feedback.
Hi @up2wing, thanks for starting a discussion!
The reason we decided against including RDSEED, ADX, CLWB and CLFLUSHOPT bits in the T2CL/T2A CPUs templates was that they did not have different values between Cascade Lake and Milan.
The reason we did not include UMIP, PKU and XSAVEC was regular userspace applications (that Firecracker is mainly targeted at) were not supposed to observe the effects that settings those bits would make. We limited those CPU templates to feature bits that are likely to be taken into account by applications or frameworks that choose different (optimised) implementations based on them.
Also, as a note, we have deprecated static CPU templates in Firecracker 1.5. …