From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v1] s390x: Add tests for execute-type instructions
Date: Thu, 23 Feb 2023 10:50:55 +0100 [thread overview]
Message-ID: <e8d21eb5afde7fd9114e225692222fa8902c4e7a.camel@linux.ibm.com> (raw)
In-Reply-To: <167713875438.6442.2406479682969262260@t14-nrb.local>
On Thu, 2023-02-23 at 08:52 +0100, Nico Boehr wrote:
> Quoting Nina Schoetterl-Glausch (2023-02-22 12:47:42)
> > Test the instruction address used by targets of an execute instruction.
> > When the target instruction calculates a relative address, the result is
> > relative to the target instruction, not the execute instruction.
> >
> > Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> [...]
> > diff --git a/s390x/Makefile b/s390x/Makefile
> > index 97a61611..6cf8018b 100644
> > --- a/s390x/Makefile
> > +++ b/s390x/Makefile
> > @@ -39,6 +39,7 @@ tests += $(TEST_DIR)/panic-loop-extint.elf
> > tests += $(TEST_DIR)/panic-loop-pgm.elf
> > tests += $(TEST_DIR)/migration-sck.elf
> > tests += $(TEST_DIR)/exittime.elf
> > +tests += $(TEST_DIR)/ex.elf
>
> You didn't add your new test to unittests.cfg, is this intentional?
Nope, I just forgot.
@Thomas, I guess I should also add it to s390x-kvm in .gitlab-ci.yml,
since the test passes on KVM?
>
> Otherwise:
>
> Reviewed-by: Nico Boehr <nrb@linux.ibm.com>
Thanks!
next prev parent reply other threads:[~2023-02-23 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 11:47 [kvm-unit-tests PATCH v1] s390x: Add tests for execute-type instructions Nina Schoetterl-Glausch
2023-02-23 7:52 ` Nico Boehr
2023-02-23 9:50 ` Nina Schoetterl-Glausch [this message]
2023-02-23 19:16 ` Thomas Huth
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=e8d21eb5afde7fd9114e225692222fa8902c4e7a.camel@linux.ibm.com \
--to=nsg@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=thuth@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