qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Filip Bozuta <Filip.Bozuta@rt-rk.com>
Cc: qemu-devel@nongnu.org, laurent@vivier.eu
Subject: Re: [PATCH v2 0/2] tests/tcg/multiarch: Add tests for implemented real
Date: Thu, 12 Mar 2020 09:58:33 +0000	[thread overview]
Message-ID: <87d09hgaie.fsf@linaro.org> (raw)
In-Reply-To: <1581603905-21565-1-git-send-email-Filip.Bozuta@rt-rk.com>


Filip Bozuta <Filip.Bozuta@rt-rk.com> writes:

> This series covers tests for implemented rtc and alsa timer ioctls. The names
> of ioctls that are covered by these tests can be found in patch descriptions.
> The functionalities of each ioctl that is tested can be found in patches that
> implement them.
>
> Some of the features that are accessible through these ioctls are not supported
> on all test host pc's. These tests were written so that the implemented ioctls
> can be properly tested on pc's that support all of their features.
>
> Both rtc and alsa timer test folders have separate files for manually written
> and remotely obtained tests. Tests that were obtained remotely run multiple ioctl
> tests at once, while the manually written tests can be used to run both individual 
> and multiple ioctl tests based on the command specified when running the test.
>
> Filip Bozuta (2):
>   tests/tcg/multiarch: Add tests for implemented rtc ioctls
>   tests/tcg/multiarch: Add tests for implemented alsa sound timer ioctls
>
>  .../manual-test/alsa-timer-ioctl-manual-test.c     | 294 +++++++++++++++++
>  .../alsa-timer-ioctl-tests/remote-test/timer.c     | 158 +++++++++
>  .../manual-test/rtc-ioctl-manual-test.c            | 352 +++++++++++++++++++++
>  .../rtc-ioctl-tests/remote-test/rtc-test.c         | 226
>  +++++++++++++

Because of the placement of the files these tests don't get built and
run when running check-tcg. Please integrate them properly into the
build system.

While we do have some manual only tests they are really only
placeholders until we can figure out how to plumb them in properly. You
can skip them by using a special run-% rule, eg. the semihosting tests:

  run-semiconsole: semiconsole
          $(call skip-test, $<, "MANUAL ONLY")

>  4 files changed, 1030 insertions(+)
>  create mode 100644 tests/tcg/multiarch/alsa-timer-ioctl-tests/manual-test/alsa-timer-ioctl-manual-test.c
>  create mode 100644 tests/tcg/multiarch/alsa-timer-ioctl-tests/remote-test/timer.c
>  create mode 100644 tests/tcg/multiarch/rtc-ioctl-tests/manual-test/rtc-ioctl-manual-test.c
>  create mode 100644 tests/tcg/multiarch/rtc-ioctl-tests/remote-test/rtc-test.c


-- 
Alex Bennée


      parent reply	other threads:[~2020-03-12  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 14:25 [PATCH v2 0/2] tests/tcg/multiarch: Add tests for implemented real Filip Bozuta
2020-02-13 14:25 ` [PATCH v2 1/2] tests/tcg/multiarch: Add tests for implemented rtc ioctls Filip Bozuta
2020-02-13 14:25 ` [PATCH v2 2/2] tests/tcg/multiarch: Add tests for implemented alsa sound timer ioctls Filip Bozuta
2020-02-13 22:47   ` Aleksandar Markovic
2020-03-12  9:58 ` Alex Bennée [this message]

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=87d09hgaie.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=Filip.Bozuta@rt-rk.com \
    --cc=laurent@vivier.eu \
    --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).