mirror of https://github.com/xemu-project/xemu.git
docs: (further) remove non-reference uses of single backticks
The series rotted already. Here's the new changes. Signed-off-by: John Snow <jsnow@redhat.com> Reviewed-by: Damien Hedde <damien.hedde@greensocs.com> [ extra backticks fixes ] Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Message-Id: <20211004215238.1523082-3-jsnow@redhat.com>
This commit is contained in:
parent
450e0f28a4
commit
ca0a0d122c
|
@ -47,14 +47,14 @@ command line options for which a same-named Meson option exists;
|
||||||
dashes in the command line are replaced with underscores.
|
dashes in the command line are replaced with underscores.
|
||||||
|
|
||||||
Many checks on the compilation environment are still found in configure
|
Many checks on the compilation environment are still found in configure
|
||||||
rather than `meson.build`, but new checks should be added directly to
|
rather than ``meson.build``, but new checks should be added directly to
|
||||||
`meson.build`.
|
``meson.build``.
|
||||||
|
|
||||||
Patches are also welcome to move existing checks from the configure
|
Patches are also welcome to move existing checks from the configure
|
||||||
phase to `meson.build`. When doing so, ensure that `meson.build` does
|
phase to ``meson.build``. When doing so, ensure that ``meson.build`` does
|
||||||
not use anymore the keys that you have removed from `config-host.mak`.
|
not use anymore the keys that you have removed from ``config-host.mak``.
|
||||||
Typically these will be replaced in `meson.build` by boolean variables,
|
Typically these will be replaced in ``meson.build`` by boolean variables,
|
||||||
``get_option('optname')`` invocations, or `dep.found()` expressions.
|
``get_option('optname')`` invocations, or ``dep.found()`` expressions.
|
||||||
In general, the remaining checks have little or no interdependencies,
|
In general, the remaining checks have little or no interdependencies,
|
||||||
so they can be moved one by one.
|
so they can be moved one by one.
|
||||||
|
|
||||||
|
@ -298,7 +298,7 @@ comprises the following tasks:
|
||||||
|
|
||||||
- Add code to perform the actual feature check.
|
- Add code to perform the actual feature check.
|
||||||
|
|
||||||
- Add code to include the feature status in `config-host.h`
|
- Add code to include the feature status in ``config-host.h``
|
||||||
|
|
||||||
- Add code to print out the feature status in the configure summary
|
- Add code to print out the feature status in the configure summary
|
||||||
upon completion.
|
upon completion.
|
||||||
|
@ -334,7 +334,7 @@ The other supporting code is generally simple::
|
||||||
|
|
||||||
For the configure script to parse the new option, the
|
For the configure script to parse the new option, the
|
||||||
``scripts/meson-buildoptions.sh`` file must be up-to-date; ``make
|
``scripts/meson-buildoptions.sh`` file must be up-to-date; ``make
|
||||||
update-buildoptions`` (or just `make`) will take care of updating it.
|
update-buildoptions`` (or just ``make``) will take care of updating it.
|
||||||
|
|
||||||
|
|
||||||
Support scripts
|
Support scripts
|
||||||
|
|
|
@ -77,9 +77,9 @@ CPUID
|
||||||
|
|
||||||
Due to its myriad dependencies, SGX is currently not listed as supported
|
Due to its myriad dependencies, SGX is currently not listed as supported
|
||||||
in any of Qemu's built-in CPU configuration. To expose SGX (and SGX Launch
|
in any of Qemu's built-in CPU configuration. To expose SGX (and SGX Launch
|
||||||
Control) to a guest, you must either use `-cpu host` to pass-through the
|
Control) to a guest, you must either use ``-cpu host`` to pass-through the
|
||||||
host CPU model, or explicitly enable SGX when using a built-in CPU model,
|
host CPU model, or explicitly enable SGX when using a built-in CPU model,
|
||||||
e.g. via `-cpu <model>,+sgx` or `-cpu <model>,+sgx,+sgxlc`.
|
e.g. via ``-cpu <model>,+sgx`` or ``-cpu <model>,+sgx,+sgxlc``.
|
||||||
|
|
||||||
All SGX sub-features enumerated through CPUID, e.g. SGX2, MISCSELECT,
|
All SGX sub-features enumerated through CPUID, e.g. SGX2, MISCSELECT,
|
||||||
ATTRIBUTES, etc... can be restricted via CPUID flags. Be aware that enforcing
|
ATTRIBUTES, etc... can be restricted via CPUID flags. Be aware that enforcing
|
||||||
|
@ -126,7 +126,7 @@ creating VM with SGX.
|
||||||
Feature Control
|
Feature Control
|
||||||
~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
Qemu SGX updates the `etc/msr_feature_control` fw_cfg entry to set the SGX
|
Qemu SGX updates the ``etc/msr_feature_control`` fw_cfg entry to set the SGX
|
||||||
(bit 18) and SGX LC (bit 17) flags based on their respective CPUID support,
|
(bit 18) and SGX LC (bit 17) flags based on their respective CPUID support,
|
||||||
i.e. existing guest firmware will automatically set SGX and SGX LC accordingly,
|
i.e. existing guest firmware will automatically set SGX and SGX LC accordingly,
|
||||||
assuming said firmware supports fw_cfg.msr_feature_control.
|
assuming said firmware supports fw_cfg.msr_feature_control.
|
||||||
|
|
Loading…
Reference in New Issue