From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 6/7] configs/qemu_armv7a_tz_virt: Armv7-A emulation with TrustZone services
Date: Tue, 5 Mar 2019 10:55:29 +0100 [thread overview]
Message-ID: <20190305105529.1fcccbc3@windsurf> (raw)
In-Reply-To: <CAN5uoS_1zj1=ywE3-Gu55UksPAsHdGGEgAgm+YAAV=Wuo2pBfA@mail.gmail.com>
Hello ?tienne,
On Tue, 5 Mar 2019 10:14:07 +0100
Etienne Carriere <etienne.carriere@linaro.org> wrote:
> I've prepared something to test the optee on qemu/arm through the
> runtime tests but few questions puzzle me.
>
> 1/ To use the board defconfig for the test, I created the file
> support/test/conf/qemu_xxx_defconfig as a symlink to
> configs/qemu_xxx_defconfig.
> I'm not sure it is that nice. But it allowed to set the test config in
> the test_opee.py using:
>
> class TestOpteeXtest(infra.basetest.BRTest):
> with open(infra.filepath('conf/qemu_armv7a_tz_virt_defconfig'),
> 'r') as config_file:
> config = "".join(line for line in config_file if line[:1]!='#')
infra.filepath() is as simple as:
def filepath(relpath):
return os.path.join(os.getcwd(), "support/testing", relpath)
so you can just do:
with open(os.path.join(os.getcwd(), "configs/qemu_armv7a_tz_virt_defconfig"))
however, I see one down-side with this: defconfigs are usually using an
internal toolchain, so they take a long time to build. We typically try
to use external toolchains for most runtime tests, to make them faster
and therefore more usable. But perhaps you can take the defconfig +
inject a few lines of configuration to use an external toolchain.
> 2/ To share this test I need few preliminary changes in arm-trusted-firmware.
> This will brings a series of dependent patches: tf-a updates + qemu
> board defconfig + optee runtime test script.
> The series depends on branch next, as dependent on OP-TEE packages.
> That will make several versatile changes in a single patches series
> over the next branch.
>
> I plan to submit the series to the ML, for the next.
> Tell me if you rather have this work be reviewed in 2 steps: first
> tf-a changes, then once merged, qemu board and the optee runtime test.
Note: next is going to be merged back in master very soon now, since
2019.02 has been released.
If you already have all the changes, then please send them in one
single series, it makes it clearer why the preparation patches are
needed.
Also, I have seen your series improving various things in optee related
packages, I intend to have a look very soon.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-05 9:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 10:47 [Buildroot] [PATCH v4 1/7] boot/optee-os: new package Etienne Carriere
2019-01-30 10:47 ` [Buildroot] [PATCH v4 2/7] optee-client: " Etienne Carriere
2019-02-17 20:52 ` Thomas Petazzoni
2019-01-30 10:47 ` [Buildroot] [PATCH v4 3/7] optee-examples: " Etienne Carriere
2019-02-17 21:28 ` Thomas Petazzoni
2019-02-19 7:25 ` Etienne Carriere
2019-01-30 10:47 ` [Buildroot] [PATCH v4 4/7] optee-test: " Etienne Carriere
2019-02-17 21:50 ` Thomas Petazzoni
2019-02-17 21:51 ` Thomas Petazzoni
2019-02-19 7:18 ` Etienne Carriere
2019-01-30 10:47 ` [Buildroot] [PATCH v4 5/7] optee-benchmark: " Etienne Carriere
2019-02-17 22:08 ` Thomas Petazzoni
2019-02-19 7:26 ` Etienne Carriere
2019-03-05 8:02 ` Etienne Carriere
2019-01-30 10:47 ` [Buildroot] [PATCH v4 6/7] configs/qemu_armv7a_tz_virt: Armv7-A emulation with TrustZone services Etienne Carriere
2019-02-17 22:12 ` Thomas Petazzoni
2019-02-18 18:14 ` Yann E. MORIN
2019-02-18 21:28 ` Etienne Carriere
2019-02-18 21:43 ` Thomas Petazzoni
2019-02-19 8:31 ` Arnout Vandecappelle
2019-03-05 9:14 ` Etienne Carriere
2019-03-05 9:55 ` Thomas Petazzoni [this message]
2019-03-05 10:58 ` Etienne Carriere
2019-01-30 10:47 ` [Buildroot] [PATCH v4 7/7] configs/qemu_aarch64_tz_virt: AArch64 " Etienne Carriere
2019-02-10 16:14 ` [Buildroot] [PATCH v4 1/7] boot/optee-os: new package Thomas Petazzoni
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=20190305105529.1fcccbc3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox