qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 0/5] tests/vm: various minor improvements
Date: Fri, 3 Aug 2018 17:29:39 +0800	[thread overview]
Message-ID: <20180803092939.GF16395@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180803085230.30574-1-peter.maydell@linaro.org>

On Fri, 08/03 09:52, Peter Maydell wrote:
> The setup I had for my BSD VMs broke today, so I thought I'd
> have a look at using the tests/vm/ support for building QEMU
> inside BSD VMs rather than re-rolling my own. This patchset
> fixes some rough edges I ran into along the way:
>  * fixes support for non-KVM accelerators
>  * propagates J=n setting into 'make check' in the VM
>  * propagates V=1 setting into 'make' and 'make check' in the VM
>  * uses --output-sync so that J=n settings don't mangle output
>  * bumps the RAM settings so J=n doesn't cause the guest to
>    run out of memory and kill the compiler
> 
> Ideally I'd like to be able to separately invoke commands
> for "build in VM" and "run make check in VM for that build"; for
> instance I only want V=1 on the make-check, not the make, and in
> some cases might want to do a build but not check, and so on.
> But that seemed too complicated for the moment.

If we can limit the abstraction to "build" and "check" (or "test"), it shouldn't
be hard to add a --build-only option to the Python main() and VM_BUILD_ONLY=1 to
Makefile.

> 
> Is it possible for the VMs to be persistent? Currently it
> looks like they throw away their contents and start afresh
> for every invocation. Doing build tests as incremental is
> faster than doing every one as a from-clean...

Yes, we'll do that in 3.1.

> 
> Also, I notice that the OpenBSD VM setup is using SDL 1.2,
> which means that configure complains and suggests switching
> to SDL 2.0. How do we update the base image?

I prepared the image by hand and uploaded it because I couldn't find a better
way. So the easist way to update is probably booting the image by hand, do the
modifications, then upload it again.

> 
> thanks
> -- PMM
> 
> Peter Maydell (5):
>   tests/vm: Use -cpu max rather than -cpu host
>   tests/vm: Pass the jobs parallelism setting to 'make check'
>   tests/vm: Propagate V=1 down into the make inside the VM
>   tests/vm: Bump guest RAM up from 2G to 4G
>   tests/vm: Use make's --output-sync option
> 
>  tests/vm/Makefile.include | 1 +
>  docs/devel/testing.rst    | 1 +
>  tests/vm/basevm.py        | 9 ++++++---
>  tests/vm/freebsd          | 4 ++--
>  tests/vm/netbsd           | 4 ++--
>  tests/vm/openbsd          | 4 ++--
>  tests/vm/ubuntu.i386      | 4 ++--
>  7 files changed, 16 insertions(+), 11 deletions(-)
> 
> -- 
> 2.17.1
> 
> 

  parent reply	other threads:[~2018-08-03  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03  8:52 [Qemu-devel] [PATCH 0/5] tests/vm: various minor improvements Peter Maydell
2018-08-03  8:52 ` [Qemu-devel] [PATCH 1/5] tests/vm: Use -cpu max rather than -cpu host Peter Maydell
2018-08-03  8:52 ` [Qemu-devel] [PATCH 2/5] tests/vm: Pass the jobs parallelism setting to 'make check' Peter Maydell
2018-08-03  8:52 ` [Qemu-devel] [PATCH 3/5] tests/vm: Propagate V=1 down into the make inside the VM Peter Maydell
2018-08-03  8:52 ` [Qemu-devel] [PATCH 4/5] tests/vm: Bump guest RAM up from 2G to 4G Peter Maydell
2018-08-03  8:52 ` [Qemu-devel] [PATCH 5/5] tests/vm: Use make's --output-sync option Peter Maydell
2018-08-03  9:29 ` Fam Zheng [this message]
2018-08-03 10:45 ` [Qemu-devel] [PATCH 0/5] tests/vm: various minor improvements Fam Zheng

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=20180803092939.GF16395@lemon.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).