From: Nico Boehr <nrb@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v1 4/4] s390x: add selftest for migration
Date: Wed, 13 Apr 2022 16:32:07 +0200 [thread overview]
Message-ID: <dd6fc8061a0c0740e4d9160575e4c3a934df474c.camel@linux.ibm.com> (raw)
In-Reply-To: <9e87f40c-3270-ebc3-7afe-13a3489940d1@redhat.com>
On Tue, 2022-04-12 at 09:49 +0200, Thomas Huth wrote:
> I think a simple test that checks some register values should not be
> too
> hard to implement, so I'd prefer that instead of this simple selftest
> ...
> but if you're too short in time right now, I also won't insist.
It makes sense. I will add it.
prev parent reply other threads:[~2022-04-13 14:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 10:07 [kvm-unit-tests PATCH v1 0/4] s390x: add migration test suport Nico Boehr
2022-04-11 10:07 ` [kvm-unit-tests PATCH v1 1/4] lib: s390x: add support for SCLP console read Nico Boehr
2022-04-12 8:02 ` Thomas Huth
2022-04-13 14:41 ` Nico Boehr
2022-04-12 15:32 ` Janosch Frank
2022-04-13 15:00 ` Nico Boehr
2022-04-11 10:07 ` [kvm-unit-tests PATCH v1 2/4] s390x: add support for migration tests Nico Boehr
2022-04-11 12:58 ` Claudio Imbrenda
2022-04-12 8:05 ` Thomas Huth
2022-04-11 10:07 ` [kvm-unit-tests PATCH v1 3/4] s390x: don't run migration tests under PV Nico Boehr
2022-04-11 12:58 ` Claudio Imbrenda
2022-04-12 8:06 ` Thomas Huth
2022-04-11 10:07 ` [kvm-unit-tests PATCH v1 4/4] s390x: add selftest for migration Nico Boehr
2022-04-11 12:49 ` Claudio Imbrenda
2022-04-12 11:49 ` Nico Boehr
2022-04-13 8:42 ` Claudio Imbrenda
2022-04-11 15:30 ` Thomas Huth
2022-04-12 7:41 ` Nico Boehr
2022-04-12 7:49 ` Thomas Huth
2022-04-13 14:32 ` Nico Boehr [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=dd6fc8061a0c0740e4d9160575e4c3a934df474c.camel@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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