From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Collin Walling <walling@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
mst@redhat.com, qemu-devel@nongnu.org, pasic@linux.ibm.com,
qemu-s390x@nongnu.org, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4] s390: diagnose 318 info reset and migration support
Date: Tue, 14 May 2019 11:12:08 +0200 [thread overview]
Message-ID: <20190514111208.781e6358.cohuck@redhat.com> (raw)
In-Reply-To: <4ebcad9e-ce3c-bd86-3c96-e2909d360813@de.ibm.com>
On Tue, 14 May 2019 11:07:41 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 14.05.19 10:59, David Hildenbrand wrote:
> > We can
> >
> > 1. Fail to start with #cpus > 240 when diag318=on
> > 2. Remove the error once we support more than one SCLP response page
> >
> > Or
> >
> > 1. Allow to start with #cpus > 240 when diag318=on, but indicate only
> > 240 CPUs via SCLP
> > 2. Print a warning
> > 3. Remove the restriction and the warning once we support more than one
> > SCLP response page
We'd need compat handling for step 3., then?
> >
> > While I prefer the second approach (similar to defining zPCI devices
> > without zpci=on), I could also live with the first approach.
>
> Lets just continue with your other suggestion to simply limit the sclp
> response and do not do any failure or machine change. That seems like
> the easiest solution.
That's the second option, right? Should be reasonable.
next prev parent reply other threads:[~2019-05-14 9:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 22:31 [Qemu-devel] [PATCH v4] s390: diagnose 318 info reset and migration support Collin Walling
2019-05-09 9:58 ` Christian Borntraeger
2019-05-09 10:05 ` David Hildenbrand
2019-05-09 20:50 ` Collin Walling
2019-05-13 5:56 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-05-13 7:46 ` [Qemu-devel] " David Hildenbrand
2019-05-13 8:03 ` David Hildenbrand
2019-05-13 9:34 ` Christian Borntraeger
2019-05-13 9:40 ` David Hildenbrand
2019-05-13 9:51 ` Christian Borntraeger
2019-05-13 9:57 ` David Hildenbrand
2019-05-13 10:55 ` Christian Borntraeger
2019-05-13 11:34 ` David Hildenbrand
2019-05-13 11:46 ` Cornelia Huck
2019-05-14 7:09 ` Christian Borntraeger
2019-05-14 7:28 ` David Hildenbrand
2019-05-14 8:37 ` Christian Borntraeger
2019-05-14 8:49 ` Cornelia Huck
2019-05-14 8:53 ` Christian Borntraeger
2019-05-14 8:59 ` David Hildenbrand
2019-05-14 9:07 ` Christian Borntraeger
2019-05-14 9:12 ` Cornelia Huck [this message]
2019-05-14 9:10 ` Christian Borntraeger
2019-05-14 9:20 ` David Hildenbrand
2019-05-14 9:23 ` Christian Borntraeger
2019-05-14 9:25 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2019-05-14 9:27 ` David Hildenbrand
2019-05-14 9:30 ` Cornelia Huck
2019-05-16 13:35 ` Collin Walling
2019-05-16 14:10 ` Christian Borntraeger
2019-05-14 8:50 ` [Qemu-devel] " David Hildenbrand
2019-05-14 8:56 ` Christian Borntraeger
2019-05-14 9:00 ` Cornelia Huck
2019-05-14 9:03 ` David Hildenbrand
2019-05-14 9:05 ` David Hildenbrand
2019-05-14 9:00 ` David Hildenbrand
2019-05-14 9:04 ` Christian Borntraeger
2019-05-16 12:42 ` Collin Walling
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=20190514111208.781e6358.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=walling@linux.ibm.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.