On Mon, 13 Sept 2021 at 14:10, <marcandre.lur...@redhat.com> wrote:
>
> From: Marc-André Lureau <marcandre.lur...@redhat.com>
>
> I was looking for such documentation, but couldn't find it. Add it to
> the build-platform.rst document.
>
> Signed-off-by: Marc-André Lureau <marcandre.lur...@redhat.com>
> ---
> docs/about/build-platforms.rst | 28 ++++++++++++++++++++++++++++
> meson.build | 2 +-
> 2 files changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/docs/about/build-platforms.rst b/docs/about/build-platforms.rst
> index 692323609e..518a19aff7 100644
> --- a/docs/about/build-platforms.rst
> +++ b/docs/about/build-platforms.rst
> @@ -29,6 +29,34 @@ The `Repology`_ site is a useful resource to identify
> currently shipped versions of software in various operating systems,
> though it does not cover all distros listed below.
>
> +Supported host architectures
> +----------------------------
> +
> +Those hosts have a native TCG backend and are regularly tested:
> +
> + .. list-table::
> + :header-rows: 1
> +
> + * - CPU Architecture
> + - Accelerators
> + * - Arm
> + - kvm (64 bit only), xen
> + * - MIPS
> + - kvm
> + * - PPC
> + - kvm
> + * - RISC-V
> + -
> + * - s390x
> + - kvm
> + * - SPARC
> + -
> + * - x86
> + - kvm, xen, hax, hvf (64 bit only), nvmm, whpx (64 bit only)
I still wonder if this would be clearer if we listed 'tcg' as
an accelerator like all the others, rather than describing it as
a kind of special case in the text above the table. After all, you
can select it with '-accel tcg' the same as any other.
I think the information in the table is correct now.
Sort the list of accelerators alphabetically ?
> +
> +Other architectures are not actively maintained. They may be removed in
> future
> +releases.
> +
> Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
> -----------------------------------------
>
> diff --git a/meson.build b/meson.build
> index 9a64d16943..27593c9b90 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -78,7 +78,7 @@ endif
>
> accelerator_targets = { 'CONFIG_KVM': kvm_targets }
> if cpu in ['x86', 'x86_64', 'arm', 'aarch64']
> - # i368 emulator provides xenpv machine type for multiple architectures
> + # i386 emulator provides xenpv machine type for multiple architectures
> accelerator_targets += {
> 'CONFIG_XEN': ['i386-softmmu', 'x86_64-softmmu'],
> }
This change appears to be unrelated ?
thanks
-- PMM
