From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Fabiano Rosas <farosas@linux.ibm.com>,
mopsfelder@gmail.com
Subject: Re: [PATCH 0/2] tests/migration: add support for ppc64le in guestperf.py
Date: Sat, 21 Jan 2023 08:39:05 -0300 [thread overview]
Message-ID: <835c0cce-ea5e-c9c7-fd6a-f0e6ebd7ed20@gmail.com> (raw)
In-Reply-To: <20220809002451.91541-1-muriloo@linux.ibm.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 8/8/22 21:24, Murilo Opsfelder Araujo wrote:
> The first patch adds sysprof-capture-4 dependency when building stress binary in
> order to fix a build error.
>
> The second patch adds support for ppc64le in guestperf.py.
>
> Murilo Opsfelder Araujo (2):
> tests/migration: add sysprof-capture-4 as dependency for stress binary
> tests/migration: add support for ppc64le for guestperf.py
>
> tests/migration/guestperf/engine.py | 28 +++++++++++++++++++++++++---
> tests/migration/meson.build | 4 +++-
> 2 files changed, 28 insertions(+), 4 deletions(-)
>
> --
> 2.37.1
next prev parent reply other threads:[~2023-01-21 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 0:24 [PATCH 0/2] tests/migration: add support for ppc64le in guestperf.py Murilo Opsfelder Araujo
2022-08-09 0:24 ` [PATCH 1/2] tests/migration: add sysprof-capture-4 as dependency for stress binary Murilo Opsfelder Araujo
2022-12-23 16:19 ` Daniel Henrique Barboza
2023-02-02 16:54 ` Juan Quintela
2022-08-09 0:24 ` [PATCH 2/2] tests/migration: add support for ppc64le for guestperf.py Murilo Opsfelder Araujo
2022-12-23 16:19 ` Daniel Henrique Barboza
2023-02-02 16:57 ` Juan Quintela
2023-01-21 11:39 ` Daniel Henrique Barboza [this message]
2023-01-21 11:57 ` [PATCH 0/2] tests/migration: add support for ppc64le in guestperf.py BALATON Zoltan
2023-01-21 12:20 ` Daniel Henrique Barboza
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=835c0cce-ea5e-c9c7-fd6a-f0e6ebd7ed20@gmail.com \
--to=danielhb413@gmail.com \
--cc=dgilbert@redhat.com \
--cc=farosas@linux.ibm.com \
--cc=mopsfelder@gmail.com \
--cc=muriloo@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.com \
/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.