qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Willian Rampazzo <wrampazz@redhat.com>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Cleber Rosa Junior" <crosa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Philippe Mathieu Daude" <philmd@redhat.com>
Subject: Re: [PATCH v2 2/6] tests/acceptance: add replay kernel test for ppc64
Date: Mon, 5 Jul 2021 14:46:52 -0300	[thread overview]
Message-ID: <CAKJDGDb+fDxJw2ZnLPGSZ0_VLPrJdfq2wbVw=zbsvb8_tU1kOA@mail.gmail.com> (raw)
In-Reply-To: <162459954921.387455.17000468377504697052.stgit@pasha-ThinkPad-X280>

Already upstream :)

On Fri, Jun 25, 2021 at 2:39 AM Pavel Dovgalyuk
<pavel.dovgalyuk@ispras.ru> wrote:
>
> This patch adds record/replay test which boots Linux
> kernel on ppc64 platform. The test uses kernel binaries
> taken from boot_linux_console test.
>
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgalyuk@ispras.ru>
> ---
>  tests/acceptance/replay_kernel.py |   13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/tests/acceptance/replay_kernel.py b/tests/acceptance/replay_kernel.py
> index cdc22cb6d3..7e7f4c8ccc 100644
> --- a/tests/acceptance/replay_kernel.py
> +++ b/tests/acceptance/replay_kernel.py
> @@ -367,6 +367,19 @@ def test_xtensa_lx60(self):
>          self.do_test_advcal_2018(file_path, 'santas-sleigh-ride.elf',
>                                   args=('-cpu', 'dc233c'))
>
> +    def test_ppc64_e500(self):
> +        """
> +        :avocado: tags=arch:ppc64
> +        :avocado: tags=machine:ppce500
> +        :avocado: tags=cpu:e5500
> +        """
> +        tar_hash = '6951d86d644b302898da2fd701739c9406527fe1'
> +        tar_url = ('https://www.qemu-advent-calendar.org'
> +                   '/2018/download/day19.tar.xz')
> +        file_path = self.fetch_asset(tar_url, asset_hash=tar_hash)
> +        self.do_test_advcal_2018(file_path, 'uImage', ('-cpu', 'e5500'))
> +
> +
>  @skipUnless(os.getenv('AVOCADO_TIMEOUT_EXPECTED'), 'Test might timeout')
>  class ReplayKernelSlow(ReplayKernelBase):
>      # Override the timeout, because this kernel includes an inner
>



  reply	other threads:[~2021-07-05 17:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  5:38 [PATCH v2 0/6] More record/replay acceptance tests Pavel Dovgalyuk
2021-06-25  5:39 ` [PATCH v2 1/6] tests/acceptance: add replay kernel test for s390 Pavel Dovgalyuk
2021-06-25  7:20   ` Thomas Huth
2021-06-25  5:39 ` [PATCH v2 2/6] tests/acceptance: add replay kernel test for ppc64 Pavel Dovgalyuk
2021-07-05 17:46   ` Willian Rampazzo [this message]
2021-07-06  4:27     ` Pavel Dovgalyuk
2021-06-25  5:39 ` [PATCH v2 3/6] tests/acceptance: add replay kernel test for openrisc Pavel Dovgalyuk
2021-06-25  5:39 ` [PATCH v2 4/6] tests/acceptance: add replay kernel test for nios2 Pavel Dovgalyuk
2021-06-25  5:39 ` [PATCH v2 5/6] tests/acceptance: add replay kernel test for alpha Pavel Dovgalyuk
2021-06-25  5:39 ` [PATCH v2 6/6] tests/acceptance: Linux boot test for record/replay Pavel Dovgalyuk

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='CAKJDGDb+fDxJw2ZnLPGSZ0_VLPrJdfq2wbVw=zbsvb8_tU1kOA@mail.gmail.com' \
    --to=wrampazz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=pavel.dovgalyuk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --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).