On Mon, 28 Aug 2017 11:11:15 +0200 Christian Borntraeger <borntraeger@xxxxxxxxxx> wrote: > On 08/28/2017 11:07 AM, Cornelia Huck wrote: > > On Mon, 28 Aug 2017 10:07:28 +0200 > > Christian Borntraeger <borntraeger@xxxxxxxxxx> wrote: > > > >> From: "Jason J. Herne" <jjherne@xxxxxxxxxxxxxxxxxx> > >> > >> kvm has always supported the concept of starting in z/Arch mode so let's > >> reflect the feature bit to the guest. > >> > >> Also, we change sigp set architecture to reject any request to change > >> architecture modes. > > > > What are the implications of this for guests? IIRC, czam is a z14 > > feature (the updated PoP is not yet out, is it?). We now reject any set > > arch sigp, even if we profess to be an older machine. Linux can > > probably deal with this, but is it correct? > > Linux can deal with it. Since KVM does not support IPL in ESA mode, we basically > always provided the czam functionality. We now do it like it was architected. > z/VM does it the same way when enabling czam on an older system like z13. OK, this implies any z operating system needs to be able to deal with czam on older machines. > In other words the old code was not compliant (and never was), the new code > is compliant. Since czam is kind of a "negative" facility, we can implement > it also on older systems. Looking at this, we should mirror this in qemu in tcg mode, as the corresponding qemu patch only handles the kvm path (I obviously did not look at the patch in enough detail...) Added to my list. -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
