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:00:07 +0200 [thread overview]
Message-ID: <20190514110007.24d8ac33.cohuck@redhat.com> (raw)
In-Reply-To: <9a9e9c58-d991-369f-a577-b70581efc75b@de.ibm.com>
On Tue, 14 May 2019 10:56:43 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 14.05.19 10:50, David Hildenbrand wrote:
> > Another idea for temporary handling: Simply only indicate 240 CPUs to
> > the guest if the response does not fit into a page. Once we have that
> > SCLP thingy, this will be fixed. Guest migration back and forth should
> > work, as the VCPUs are fully functional (and initially always stopped),
> > the guest will simply not be able to detect them via SCLP when booting
> > up, and therefore not use them.
>
> Yes, that looks like a good temporary solution. In fact if the guest relies
> on simply probing it could even make use of the additional CPUs. Its just
> the sclp response that is limited to 240 (or make it 247?)
Where did the 240 come from - extra spare room? If so, 247 would
probably be all right?
next prev parent reply other threads:[~2019-05-14 9:01 UTC|newest]
Thread overview: 39+ 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-01 22:31 ` 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
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 [this message]
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=20190514110007.24d8ac33.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 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).