Vikram Garhwal <vikram.garh...@amd.com> writes:
> Add CONFIG_XEN for aarch64 device to support build for ARM targets.
So to be clear a --enable-xen only build for any of these binaries
essentially ends up being the same thing just with a slightly less
discombobulating name?
Maybe given there is no real architecture specific stuff we should just
create a neutral binary for --enable-xen (e.g. qemu-xen-backend)?
Anyway:
Reviewed-by: Alex Bennée <alex.ben...@linaro.org>
>
> Signed-off-by: Vikram Garhwal <vikram.garh...@amd.com>
> Signed-off-by: Stefano Stabellini <stefano.stabell...@amd.com>
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index b686dfef75..0027d7d195 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -125,7 +125,7 @@ endif
> if cpu in ['x86', 'x86_64', 'arm', 'aarch64']
> # i386 emulator provides xenpv machine type for multiple architectures
> accelerator_targets += {
> - 'CONFIG_XEN': ['i386-softmmu', 'x86_64-softmmu'],
> + 'CONFIG_XEN': ['i386-softmmu', 'x86_64-softmmu', 'aarch64-softmmu'],
> }
> endif
> if cpu in ['x86', 'x86_64']
--
Alex Bennée
