From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board/qemu/aarch64: add a aarch64 virt machine using an ARM cortex-a72 core
Date: Tue, 7 May 2019 14:11:42 +0200 [thread overview]
Message-ID: <20190507141142.27657a08@windsurf> (raw)
In-Reply-To: <20190507112521.12165-1-romain.naour@smile.fr>
Hello Romain,
On Tue, 7 May 2019 13:25:21 +0200
Romain Naour <romain.naour@smile.fr> wrote:
> ARM cortex-a72 core has been added to Qemu since version 3.1.0 [1] [2].
Do we really want a different defconfig for each possible ARM core that
Qemu emulates ?
> Qemu also support ARM cortex-a57 cpu core.
> Should we support and test all cpu emulation available in Qemu ?
> This can be useful for toolchain-builder project to provide a prebuilt ARM aarch64
> toolchain optimized for cortex-a57.
I'm not sure the toolchain builder project requires exactly a Qemu
emulating the specific optimization for which gcc was built. I.e, a
Cortex-A53 qemu defconfig can be used to boot test a Cortex-A57 or A72
optimized toolchain.
We're already doing that for example with ARMv5/v6/v7:
armv5-* | armv6-* | armv7-*)
test_defconfig="qemu_arm_vexpress_defconfig"
test_board_dir="arm-vexpress"
Or for x86:
x86-core2)
test_defconfig="qemu_x86_defconfig"
x86-i686)
test_defconfig="qemu_x86_defconfig"
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-07 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 11:25 [Buildroot] [PATCH] board/qemu/aarch64: add a aarch64 virt machine using an ARM cortex-a72 core Romain Naour
2019-05-07 12:11 ` Thomas Petazzoni [this message]
2019-05-07 12:56 ` Romain Naour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190507141142.27657a08@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.