All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 for-next 00/11] gitlab Qemu runtime testing
Date: Wed, 18 Dec 2019 23:50:53 +0100	[thread overview]
Message-ID: <99a9e061-7fca-c7c0-683b-49845067ba8f@mind.be> (raw)
In-Reply-To: <4ae261dd-e9f5-0212-eafd-c642c21d27bf@smile.fr>



On 14/12/2019 21:48, Romain Naour wrote:
> Hi,
> 
> Le 17/11/2019 ? 21:18, Romain Naour a ?crit?:
>> This new iteration take into account the previous review with
>> some additional rework.
>>
>> This series start by removing useless host-qemu build for
>> m68k_q800, enable serial console for x86/x86_64 and some
>> refactoring for csky and arm-versatile.
>>
>> Replace the readme.txt file by a bash script that ease starting
>> Qemu. Then a new comment is added to each Qemu defconfig files in
>> order to provide the path to this new script.
>> This path help to link each Qemu defconfig with it's own script.
>>
>> Add new python script to be used by gitlab to start Qemu when
>> a Qemu defconfig is built.
>>
>> Finally add this new python script to .gitlab-ci.yml.
>>
>> http://lists.busybox.net/pipermail/buildroot/2019-May/249432.html
>>
> 
> I discussed about this series with Jeremy and he suggest to add the Qemu command
> line into the Qemu's defconfig file (add a new Kconfig option).
> With that, we can even add a new Makefile target "make run-qemu" to start Qemu
> when the Qemu command line is set in the defconfig (this would avoid adding
> several launch.sh script).

So something like

config BR2_PACKAGE_HOST_QEMU_LAUNCH_ARGS
	string "qemu launch command"
	help
	  Command to launch qemu. If this is defined, 'make run-qemu' can be
	  used to build everything and launch qemu.


HOST_QEMU_LAUNCH_ARGS = $(call qstrip,$(BR2_PACKAGE_HOST_QEMU_LAUNCH_ARGS))
ifneq ($(HOST_QEMU_LAUNCH_ARGS),)
run-qemu: world
	$(Q)$(HOST_QEMU) <kernel args> <rootfs args> $(HOST_QEMU_LAUNCH_ARGS)
endif



Looks like a good idea indeed!

 Regards,
 Arnout

  reply	other threads:[~2019-12-18 22:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 20:18 [Buildroot] [PATCH v3 for-next 00/11] gitlab Qemu runtime testing Romain Naour
2019-11-17 20:18 ` [Buildroot] [PATCH v3 for-next 01/11] configs/qemu_m68k_q800: remove host-qemu Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 02/11] configs/qemu{x86, x86_64}: add a serial console Romain Naour
2019-11-22 11:27   ` Carlos Santos
2019-11-22 12:42     ` Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 03/11] board/qemu/arm-versatile: move arm-versatile nommu stuff to board/qemu/arm-versatile-nommu Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 04/11] board/qemu/csky: move csky610 stuff to board/qemu/csky610-virt Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 05/11] board/qemu/csky: move csky807 stuff to board/qemu/csky807-virt Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 06/11] board/qemu/csky: move csky810 stuff to board/qemu/csky810-virt Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 07/11] board/qemu/csky: move csky860 stuff to board/qemu/csky860-virt Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 08/11] board/qemu/*/launch.sh: add qemu launch script Romain Naour
2019-11-21 21:42   ` Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 09/11] configs/qemu-*: add a comment to provide the path launch.sh script for each Qemu defconfig Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 10/11] support/scripts/boot-qemu-image.py: boot Qemu images with Qemu-system Romain Naour
2019-11-17 20:19 ` [Buildroot] [PATCH v3 for-next 11/11] gitlab.yml.in*: enable Qemu gitlab testing Romain Naour
2019-12-14 20:48 ` [Buildroot] [PATCH v3 for-next 00/11] gitlab Qemu runtime testing Romain Naour
2019-12-18 22:50   ` Arnout Vandecappelle [this message]
2019-12-19 11:11     ` Peter Korsgaard
2020-02-04 13:59       ` Romain Naour
2020-02-04 14:31         ` Arnout Vandecappelle
2020-02-04 17:20           ` 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=99a9e061-7fca-c7c0-683b-49845067ba8f@mind.be \
    --to=arnout@mind.be \
    --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.