All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/4] support/testing: test can use the locally generated qemu host tool
Date: Tue, 2 Apr 2019 09:06:50 +0200	[thread overview]
Message-ID: <20190402090650.645aeef7@windsurf> (raw)
In-Reply-To: <5c9ee2b9d0ea5_29f73fa56c112b2c43513@ultri5.mail>

Hello Ricardo and Etienne,

On Sat, 30 Mar 2019 00:30:01 -0300
Ricardo Martincoski <ricardo.martincoski@gmail.com> wrote:

> I am not strongly against it.
> But let me ask:
> Are you or someone else having trouble with any other test case when using
> "old" qemu versions from host?
> 
> If the answer is no, maybe we should keep things simple and use a patch very
> similar to v2 of this one, just adding the host-qemu to the test case config
> fragment and the 'local' argument to Emulator.run.
> I say similar to v2 because I think your implementation in v3 with the
> 'qemu_bin' variable is better than v2.

I totally agree here. Having this option --local-emulator doesn't make
much sense. We would have to use it for some tests, but not for some
other tests.

Instead, we want each test to know whether it needs a recent enough
version of Qemu, or whether the system-provided Qemu version is good
enough.

> Another approach "to have an generic option to script run-tests to build the
> emulator within the test config" (quoting your reply to v2) would be:
> Instead of adding a command line argument to run-tests, create a new flag in
> the test case class, perhaps named "build_emulator". If that flag is True, the
> host-qemu is automatically added to the config fragment by the test infra. The
> same flag could be propagated to the Emulator.init so we don't need to pass
> 'local' to Emulator.run.

Yes, something like that sounds good.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-04-02  7:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  9:58 [Buildroot] [PATCH v3 1/4] boot/arm-trusted-firmware: support alternate image files Etienne Carriere
2019-03-22  9:58 ` [Buildroot] [PATCH v3 2/4] configs/qemu_arm_vexpress_tz: Armv7-A emulation with TrustZone services Etienne Carriere
2019-10-27 14:55   ` Arnout Vandecappelle
2019-10-29  8:08     ` Etienne Carriere
2019-10-29  8:11       ` Etienne Carriere
2019-10-29  9:08         ` Arnout Vandecappelle
2019-12-28 11:35   ` Thomas Petazzoni
2020-01-07  7:56     ` Etienne Carriere
2020-02-09 17:55       ` Romain Naour
2020-02-10 21:13         ` Romain Naour
2019-03-22  9:58 ` [Buildroot] [PATCH v3 3/4] support/testing: test can use the locally generated qemu host tool Etienne Carriere
2019-03-30  3:30   ` Ricardo Martincoski
2019-04-02  7:06     ` Thomas Petazzoni [this message]
2019-04-03  9:53       ` Etienne Carriere
2019-03-22  9:58 ` [Buildroot] [PATCH v3 4/4] support/testing: test_optee.py: test optee boot and testsuite Etienne Carriere
2019-03-30  3:33   ` Ricardo Martincoski
2019-04-03 10:19     ` Etienne Carriere
2019-04-04  3:30       ` Ricardo Martincoski
2019-04-04  7:29         ` Etienne Carriere
2019-10-27 14:59 ` [Buildroot] [PATCH v3 1/4] boot/arm-trusted-firmware: support alternate image files Arnout Vandecappelle
2019-10-29  8:19   ` Etienne Carriere

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=20190402090650.645aeef7@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.