From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org, kieran.bingham@ideasonboard.com
Subject: Re: [PATCH 1/2] tests: Add basic stress testing
Date: Mon, 13 Feb 2017 01:25:29 +0200 [thread overview]
Message-ID: <82610485.A1jWxPdiEH@avalon> (raw)
In-Reply-To: <1486824186-26450-2-git-send-email-kieran.bingham+renesas@ideasonboard.com>
Hi Kieran,
Thank you for the patch.
On Saturday 11 Feb 2017 14:43:05 Kieran Bingham wrote:
> From: Kieran Bingham <kieran.bingham@ideasonboard.com>
>
> Duplicate the functionality of vsp-unit-test-0001, to provide a set of
> work for the hardware to run, whilst we load the system using the
> 'stress' utility.
>
> Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> ---
> tests/vsp-unit-test-0022.sh | 55 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
> create mode 100755 tests/vsp-unit-test-0022.sh
>
> diff --git a/tests/vsp-unit-test-0022.sh b/tests/vsp-unit-test-0022.sh
> new file mode 100755
> index 000000000000..10230dffcc42
> --- /dev/null
> +++ b/tests/vsp-unit-test-0022.sh
> @@ -0,0 +1,55 @@
> +#!/bin/sh
> +
> +#
> +# Test active pipeline, with high load on CPU/Memory/IO using 'stress'
> +#
> +# Test WPF packing in RGB mode. Use a RPF -> WPF pipeline with a fixed
> ARGB32 +# format on the input and capture output frames in all RGB formats
> supported +# by the WPF.
> +#
> +
> +source vsp-lib.sh
> +
> +features="rpf.0 wpf.0"
> +formats="RGB332 ARGB555 XRGB555 RGB565 BGR24 RGB24 ABGR32 ARGB32 XBGR32
> XRGB32"
> +
> +test_wpf_packing() {
> + test_start "WPF packing in $format during stress testing"
> +
> + pipe_configure rpf-wpf 0 0
> + format_configure rpf-wpf 0 0 ARGB32 1024x768 $format
> +
> + vsp_runner rpf.0 &
> + vsp_runner wpf.0
> +
> + local result=$(compare_frames)
> +
> + test_complete $result
> +}
> +
> +exists() { type -t "$1" > /dev/null 2>&1; }
Let's keep formatting consistent and not inline functions on a single line.
Same comment for patch 2/2.
> +test_main() {
> + local format
> +
> + if exists stress ; then
> + STRESS=`which stress`
I don't think this is needed, you can just execute stress below, it will be
found from the $PATH. Same comment for patch 2/2.
No need to resend, I'll fix this while applying.
> + else
> + echo "$0: Stress test requires utility 'stress'"
> + test_complete skip
> + return
> + fi
> +
> + # Start stressing the system, as a background task
> + $STRESS --cpu 8 --io 4 --vm 2 --vm-bytes 128M &
> +
> + for format in $formats ; do
> + test_wpf_packing $format
> + done
> +
> + # Recover the system. Stress launches multiple PIDs, so it's best to:
> + killall -9 stress
> +}
> +
> +test_init $0 "$features"
> +test_run
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-02-12 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 14:43 [PATCH 0/2] vsp-tests: Provide stress testing Kieran Bingham
2017-02-11 14:43 ` [PATCH 1/2] tests: Add basic " Kieran Bingham
2017-02-12 23:25 ` Laurent Pinchart [this message]
2017-02-12 23:40 ` Laurent Pinchart
2017-02-11 14:43 ` [PATCH 2/2] tests: Add extended " Kieran Bingham
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=82610485.A1jWxPdiEH@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.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 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.