Skip to content

Commit 33b361a

Browse files
committed
doc: update design page for cpu templates
Signed-off-by: Nikita Kalyazin <[email protected]>
1 parent d3a8906 commit 33b361a

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

docs/design.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -115,12 +115,10 @@ KVM supports.
115115

116116
#### Exposing the CPU to the guest
117117

118-
Firecracker allows the exposure of either the host processor information or any
119-
other family/model/stepping as a way to keep compatibility for services that
120-
were not running on top of it. In addition, Firecracker supports feature
121-
masking via CPUID. To simplify customer operation, CPU feature templates can be
122-
set via the Firecracker API. Currently, the available feature templates to
123-
choose from are EC2 C3 and EC2 T2 instance types.
118+
Firecracker allows control of what processor information is exposed
119+
to the guest by using [CPU templates](cpu_templates/cpu-templates.md).
120+
CPU templates can be set via the Firecracker API. Users can choose from
121+
existing static CPU templates and/or creating their own custom CPU templates.
124122

125123
#### Clocksources available to guests
126124

0 commit comments

Comments
 (0)