From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: devel@edk2.groups.io, sean.brogan@microsoft.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [edk2-devel] [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg
Date: Tue, 31 Mar 2020 18:32:13 +0200 [thread overview]
Message-ID: <15bdbf11-56c8-54fc-9607-0b6cf7283825@arm.com> (raw)
In-Reply-To: <10604.1585671987556224046@groups.io>
On 3/31/20 6:26 PM, Sean via Groups.Io wrote:
> On Mon, Mar 30, 2020 at 11:41 PM, Ard Biesheuvel wrote:
>
> Not sure I follow. Which command line are we talking about?
>
> @Ard - In this Platform CI, ArmVirt is building and running AARCH64 but
> not ARM 32bit. Would it be valuable to build for ARM too?
>
Yes, absolutely.
> I prototyped it but want to make sure I am calling QEMU with the
> parameters you would expect to work with ArmVirtPkg
>
> qemu-system-arm -M virt -cpu cortex-a15 -pflash
> /home/vsts/work/1/s/Build/ArmVirtQemu-ARM/DEBUG_GCC5/FV/QEMU_EFI.fd -m
> 1024 -net none -serial stdio -drive
> file=fat:rw:/home/vsts/work/1/s/Build/ArmVirtQemu-ARM/DEBUG_GCC5/VirtualDrive,format=raw,media=disk
> -display none
>
The parameters look fine. Note that you can use the qemu-system-aarch64
binary as well, so no need to install both.
>
> PR build results can be seen here:
> https://dev.azure.com/tianocore/edk2-ci-play/_build/results?buildId=5074&view=results
> PR code change: https://github.com/spbrogan/edk2/pull/14
Yep, looking good. The main focus is obviously on X64 and AARCH64, but
that only increases the risk that we might regress on IA32 or ARM
without anyone noticing. So having both IA32 and ARM is a good thing.
next prev parent reply other threads:[~2020-03-31 16:32 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 7:04 [PATCH] .azurepipelines: Enable CI for OvmfPkg and EmulatorPkg Zhang, Shenglei
2020-03-26 7:11 ` [edk2-devel] " Rebecca Cran
2020-03-26 7:50 ` [EXTERNAL] " Bret Barkelew
2020-03-26 8:43 ` Ard Biesheuvel
2020-03-26 8:45 ` Zhang, Shenglei
2020-03-27 14:36 ` Laszlo Ersek
2020-03-27 14:39 ` Laszlo Ersek
2020-03-26 23:26 ` [EXTERNAL] " Bret Barkelew
2020-03-27 0:00 ` Michael D Kinney
2020-03-27 0:14 ` Bret Barkelew
2020-03-27 1:59 ` Michael D Kinney
2020-03-27 2:04 ` Liming Gao
2020-03-27 2:50 ` Sean
2020-03-28 2:29 ` [edk2-devel] " Sean
2020-03-28 2:38 ` Rebecca Cran
2020-03-28 2:48 ` Sean
2020-03-28 19:29 ` Sean
2020-03-28 20:28 ` Ard Biesheuvel
2020-03-28 21:47 ` Sean
2020-03-29 8:51 ` Ard Biesheuvel
2020-03-29 23:16 ` Sean
2020-03-30 1:44 ` Andrew Fish
2020-03-30 6:07 ` Ard Biesheuvel
2020-03-30 9:31 ` Sean
2020-03-30 9:35 ` Ard Biesheuvel
2020-03-30 17:00 ` Sean
2020-03-30 17:04 ` Ard Biesheuvel
2020-03-30 17:11 ` Sean
2020-03-30 17:44 ` Ard Biesheuvel
2020-03-30 19:07 ` Sean
2020-03-30 19:51 ` Ard Biesheuvel
2020-03-30 20:56 ` Laszlo Ersek
2020-03-30 21:03 ` Sean
2020-03-30 21:13 ` Rebecca Cran
2020-04-05 6:39 ` Sean
2020-04-06 10:11 ` Ard Biesheuvel
2020-04-07 13:21 ` Laszlo Ersek
2020-03-30 21:22 ` Ard Biesheuvel
2020-03-31 12:13 ` Laszlo Ersek
2020-03-30 21:11 ` Laszlo Ersek
2020-03-30 21:29 ` Michael D Kinney
2020-03-30 21:42 ` Sean
2020-03-30 21:46 ` Ard Biesheuvel
2020-03-31 6:31 ` Sean
2020-03-31 6:40 ` Ard Biesheuvel
2020-03-31 16:26 ` Sean
2020-03-31 16:32 ` Ard Biesheuvel [this message]
2020-03-30 22:45 ` Rebecca Cran
2020-03-30 22:58 ` Michael D Kinney
2020-03-31 12:27 ` Laszlo Ersek
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-list 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=15bdbf11-56c8-54fc-9607-0b6cf7283825@arm.com \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox