From: David Gibson <david@gibson.dropbear.id.au>
To: "Matheus K. Ferst" <matheus.ferst@eldorado.org.br>
Cc: thuth@redhat.com, gustavo.romero@protonmail.com,
qemu-devel@nongnu.org, wainersm@redhat.com, f4bug@amsat.org,
luis.pires@eldorado.org.br, qemu-ppc@nongnu.org,
alex.bennee@linaro.org
Subject: Re: [RFC PATCH 0/3] tests/tcg/ppc64le: paddi tests
Date: Mon, 19 Apr 2021 11:14:30 +1000 [thread overview]
Message-ID: <YHzZdqK4zeeaz2fh@yekko.fritz.box> (raw)
In-Reply-To: <338d679e-6619-4f60-5620-24de3ed3bf6d@eldorado.org.br>
[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]
On Fri, Apr 16, 2021 at 11:13:48AM -0300, Matheus K. Ferst wrote:
> On 16/04/2021 00:52, David Gibson wrote:
> > On Thu, Apr 15, 2021 at 06:41:35PM -0300, matheus.ferst@eldorado.org.br wrote:
> > > From: Matheus Ferst <matheus.ferst@eldorado.org.br>
> > >
> > > Based-on: <20210413211129.457272-1-luis.pires@eldorado.org.br>
> >
> > First things first: it's unclear to me if this is testing stuff that's
> > already merged, or it's speculative tests for the in-progress prefixed
> > instruction stuff. i.e. If these tests are applied right now, will
> > they pass?
>
> GCC-10 images can be used to test already merged Power10 instructions, such
> as brh/brw/brd, but I haven't writen tests for them (yet?). Both tests are
> targeting paddi, whose implementation is in-progress, so applying them now
> will fail. Maybe I should split the series? Patch 1 for now, and Patch 2 and
> 3 when paddi are merged?
That sounds reasonable, as long as patch 1 does *something* visible
now (e.g. running existing tests with the new compiler).
>
> > > This series adds gcc-10 based images to enable the build of tests with Power10
> > > instructions. Then two tests for paddi are added:
> > > - The first one checks a weird behavior observed on POWER10 Functional Simulator
> > > 1.1.0, where the 34-bit immediate is treated as a 32-bits one;
> > > - The second one exercises the R=1 path of paddi, where CIA is used instead of RA.
> > > The test is failing with the current implementation because we use cpu_nip,
> > > which is not updated all the time. Luis already has the fix, it should be
> > > applied on the next version of his patch series.
> > >
> > > The main reason to submit this patch as an RFC first is the docker part. I would
> > > lie if I tell you that I understand half of what is going on there.
> > > - 'make docker-test-tcg' fails, but apparently on unrelated things;
> > > - 'make docker-run-test-tcg@debian-ppc64el-cross' passes, but it looks
> > > like the test is skipped?
> > > - 'make check-tcg' runs the test and passes (with the fix in place for the
> > > second).
> >
> > What sort of host was that on? Unfortunately 'make check-tcg' has
> > been broken on a POWER host for some time, and I've never had time to
> > look into it.
> >
>
> I'm testing on amd64, but I can also try on ppc64le.
>
> > >
> > > Finally, get_maintainer.pl found no maintainers for
> > > tests/tcg/ppc64{,le}/Makefile.target. Would it be Mr. Gibson?
> >
> > Uh... sorta? I also don't know much about what's going on here, but
> > I'm probably maintainer by default.
> >
>
> So, should I update MAINTAINERS in this series?
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-04-19 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 21:41 [RFC PATCH 0/3] tests/tcg/ppc64le: paddi tests matheus.ferst
2021-04-15 21:41 ` [RFC PATCH 1/3] tests/docker: gcc-10 based images for ppc64{, le} tests matheus.ferst
2021-04-16 3:58 ` David Gibson
2021-04-16 14:07 ` [RFC PATCH 1/3] tests/docker: gcc-10 based images for ppc64{,le} tests Alex Bennée
2021-04-15 21:41 ` [RFC PATCH 2/3] tests/tcg/ppc64le: load 33-bits constant with paddi matheus.ferst
2021-04-15 21:41 ` [RFC PATCH 3/3] tests/tcg/ppc64le: R=1 test for paddi matheus.ferst
2021-04-16 3:52 ` [RFC PATCH 0/3] tests/tcg/ppc64le: paddi tests David Gibson
2021-04-16 14:13 ` Matheus K. Ferst
2021-04-19 1:14 ` David Gibson [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=YHzZdqK4zeeaz2fh@yekko.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=gustavo.romero@protonmail.com \
--cc=luis.pires@eldorado.org.br \
--cc=matheus.ferst@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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 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).