From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
frankja@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v1 4/4] s390x: add selftest for migration
Date: Wed, 13 Apr 2022 10:42:59 +0200 [thread overview]
Message-ID: <20220413104259.21553d56@p-imbrenda> (raw)
In-Reply-To: <627b95549636e5fb4bae5ba792298eee0a689b13.camel@linux.ibm.com>
On Tue, 12 Apr 2022 13:49:21 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:
> On Mon, 2022-04-11 at 14:49 +0200, Claudio Imbrenda wrote:
> [...]
> > > diff --git a/s390x/selftest-migration.c b/s390x/selftest-
> > > migration.c
> [...]
> > > +int main(void)
> > > +{
> > > + /* don't say migrate here otherwise we will migrate right
> > > away */
> > > + report_prefix_push("selftest migration");
> > > +
> > > + /* ask migrate_cmd to migrate (it listens for 'migrate') */
> > > + puts("Please migrate me\n");
> > > +
> > > + /* wait for migration to finish, we will read a newline */
> > > + (void)getchar();
> >
> > how hard would it be to actually check that you got the newline?
>
> It would be simple. I decided for ignoring what we actually read
> because that's what ARM and PPC do.
oh, then it's fine as it is
>
> But I am also OK checking we really read a newline. What would you
> suggest to do if we read something that's not a newline? Read again
> until we actually do get a newline?
I was more thinking that it's a failure, but see the comment above
next prev parent reply other threads:[~2022-04-13 8:43 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 [this message]
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
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=20220413104259.21553d56@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=frankja@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