From: Cornelia Huck <cohuck@redhat.com>
To: Collin Walling <walling@linux.ibm.com>
Cc: borntraeger@de.ibm.com, cotte@de.ibm.com, david@redhat.com,
mimu@linux.ibm.com, qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1] s390: guest support for diagnose 318 and limit max VCPUs to 247
Date: Wed, 5 Dec 2018 12:07:17 +0100 [thread overview]
Message-ID: <20181205120717.1713d8fe.cohuck@redhat.com> (raw)
In-Reply-To: <16daec26-f72a-326c-a808-729b9f1af129@linux.ibm.com>
On Tue, 4 Dec 2018 17:26:36 -0500
Collin Walling <walling@linux.ibm.com> wrote:
> I screen-scraped the @ibm address again (Conny was the victim this time)
>
> Reply to this thread to avoid any delivery failures.
>
> On 12/4/18 5:18 PM, Collin Walling wrote:
> > Add migration and reset support for diagnose 318. This is a new z14 GA2
> > hardware feature, but we can provide guest support starting with the
> > zEC12-full CPU model.
> >
> > Because new hardware introduces a new facility-availability byte in
> > the Read SCP Info block, we lose one byte in the CPU entries list
> > and must limit the maximum VCPUs to 247 (down from 248).
> >
> > Signed-off-by: Collin Walling <walling@linux.ibm.com>
> > ---
> >
> > Changelog
> >
> > RFC -> v1
> > - introduced kvm stubs for set/get cpc
> > - s/fac134/byte_134
> > - moved diag318 vmstate description to diag.c
> > - reduced S390_VCPU_MAX to 247
> >
> > hw/s390x/ipl.c | 3 +++
> > hw/s390x/s390-virtio-ccw.c | 3 +++
> > hw/s390x/sclp.c | 2 ++
> > include/hw/s390x/sclp.h | 2 ++
> > linux-headers/asm-s390/kvm.h | 5 ++++
> > target/s390x/cpu.h | 2 +-
> > target/s390x/cpu_features.c | 3 +++
> > target/s390x/cpu_features.h | 1 +
> > target/s390x/cpu_features_def.h | 3 +++
> > target/s390x/diag.c | 53 +++++++++++++++++++++++++++++++++++++++++
> > target/s390x/gen-features.c | 1 +
> > target/s390x/internal.h | 4 +++-
> > target/s390x/kvm-stub.c | 10 ++++++++
> > target/s390x/kvm.c | 23 ++++++++++++++++++
> > target/s390x/kvm_s390x.h | 3 +++
> > 15 files changed, 116 insertions(+), 2 deletions(-)
> > diff --git a/linux-headers/asm-s390/kvm.h b/linux-headers/asm-s390/kvm.h
> > index 0265482..8c206d2 100644
> > --- a/linux-headers/asm-s390/kvm.h
> > +++ b/linux-headers/asm-s390/kvm.h
Please split this out into a dummy headers update patch, which will be
replaced with a real headers update when applied.
next prev parent reply other threads:[~2018-12-05 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 22:18 [Qemu-devel] [PATCH v1] s390: guest support for diagnose 318 and limit max VCPUs to 247 Collin Walling
2018-12-04 22:26 ` Collin Walling
2018-12-05 11:07 ` Cornelia Huck [this message]
2018-12-05 14:52 ` [Qemu-devel] [qemu-s390x] " Collin Walling
2018-12-04 23:50 ` [Qemu-devel] " no-reply
2018-12-05 8:26 ` David Hildenbrand
2018-12-05 8:27 ` Christian Borntraeger
2018-12-05 11:54 ` [Qemu-devel] [qemu-s390x] " Cornelia Huck
2018-12-05 11:57 ` David Hildenbrand
2018-12-05 14:58 ` Collin Walling
2018-12-05 8:29 ` [Qemu-devel] " Christian Borntraeger
2018-12-05 14:59 ` Collin Walling
2018-12-05 15:22 ` Cornelia Huck
2018-12-05 15:27 ` [Qemu-devel] [qemu-s390x] " 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=20181205120717.1713d8fe.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=david@redhat.com \
--cc=mimu@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--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).