qemu-s390x
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qemu-s390x] [PATCH v4] s390: diagnose 318 info reset and migration


From: Cornelia Huck
Subject: Re: [qemu-s390x] [PATCH v4] s390: diagnose 318 info reset and migration support
Date: Tue, 14 May 2019 11:00:07 +0200

On Tue, 14 May 2019 10:56:43 +0200
Christian Borntraeger <address@hidden> 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?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]